Skip to main content
Rerun is an app of AI coworkers. You tell it what you need done, its guide (the Foreman) sets up a team of coworkers, and each one works with your tools, on a schedule or when you message it, and checks with you before anything that matters. The open source build is the same product Rerun Cloud runs, licensed under AGPL-3.0, for you to host. No plan, no credit, no limit on coworkers or seats.

Install it

One docker compose command, about ten minutes.

Open source or Cloud

What the open source build leaves out, and how to get the equivalent.

​
The three pieces

The app is the website people open: the board, the chats, the settings. It is a Next.js server (apps/ui) listening on port 3000. It also holds the API the engines call back. Supabase is the database behind the app: Postgres for the data, its auth for sign-in, its storage for uploaded files, its realtime for live updates. You use a project on supabase.com or run it on your own machine. The engine is where the coworkers actually work (apps/engine). Each workspace has exactly one. It runs every coworker of that workspace with its tools, memory, files and schedules, plus a Chromium browser and a desktop screen (Xvfb and x11vnc) people can watch. It listens on port 3000 inside its container.

​
How they talk

  • The browser talks to the app, and directly to Supabase for sign-in and live updates. That is why the Supabase address must work from the browser too.
  • The app calls the engine with the engine’s key. The engine calls the app back at RERUN_HUB_BASE_URL with the same key: to report what happened in a run, to reach the Rerun models, to compute embeddings.
  • The desktop screen is the one exception: the browser opens it directly on the engine’s address, over ws:// or wss://.
  • The app reaches OpenRouter with your key for the Foreman and the Rerun models.

​
What runs where

docker compose up starts two containers on one machine: the app, and the engine of your first workspace. That is enough for a person or a small team. Every other workspace needs a server of its own. You start the engine image on any machine with Docker, and it attaches itself to the workspace from the app. See Servers.

​
What is stored where

The data-dir is a plain folder of files and SQLite databases. Credentials stay there and never go to Supabase. Back up both places: see Backups.

​
What you need

  • A machine with Docker and Docker Compose. Building the images needs about 6 GB of memory available to Docker.
  • A Supabase project, free on supabase.com, or Supabase running on the same machine.
  • An OpenRouter key, for the Foreman and the default models.
  • Node.js 22, for two small setup commands.

​
Next steps

Install

Configuration

Add a server