Rerun: what it is, and how to start
Updated on
Rerun is an open-source app of AI coworkers you can self-host. You tell it what you need done; its guide, the Foreman, plans a team; each coworker gets a job, memory, skills and a computer, and asks before it sends, pays or deletes anything. This page follows the project's own README and self-hosting docs. It is not about the robotics data visualization tool at rerun.io (GitHub: rerun-io/rerun).
Status: Not tested yet. We have not installed Rerun for this page, so nothing here comes from our own use. Sources were checked on 2026-11-04. The latest GitHub release that day was v0.5.0, published on 2026-11-03.
Not the robotics tool
Two different projects share the name Rerun:
| This page | Different product | |
|---|---|---|
| What it is | An app of AI coworkers you self-host or use on Rerun Cloud | Multimodal robotics / spatial data visualization and streaming |
| Website | rerun.build | rerun.io |
| GitHub | rerun-build/rerun | rerun-io/rerun |
| License (code) | AGPL-3.0 | See that repository |
Search results for “rerun” or “rerun ai” often mean the robotics tool. This guide is only about the AI coworkers app.
What Rerun is
Rerun is an open-source app where AI coworkers do work for a team. The README's pitch is: hire AI coworkers that use your tools, work on a schedule, and check with you before anything that matters. You describe what you need; the Foreman interviews you, plans a team and builds it. Each coworker gets a job, its own memory, its own skills and its own computer. You see them on one board and talk to any of them like a colleague.
The code is on GitHub at rerun-build/rerun under the AGPL-3.0 license. The name and logo are not covered by that license; see TRADEMARK.md. On 2026-11-04 the latest GitHub release was v0.5.0, published 2026-11-03.
The open-source build is the same product as Rerun Cloud for coworkers, chat, memory, skills and schedules. Cloud adds hosted machines, included model credit, a template library and some premium features. Details are in the open source vs Cloud doc.
How the pieces fit
The self-hosting overview describes three pieces:
| Piece | What it does |
|---|---|
| App | The website people open: board, chats, settings. A Next.js server (apps/ui) on port 3000, plus the API engines call back. |
| Supabase | Postgres, auth, storage and realtime. A project on supabase.com, open-source Supabase on your server, or npx supabase start locally. |
| Engine | Where coworkers actually work (apps/engine). One engine per workspace: tools, memory, files, schedules, a Chromium browser and a desktop screen you can watch. |
docker compose up starts the app and the engine of your first workspace on one machine. Every other workspace needs a server of its own: you start the engine image elsewhere and attach it from the app.
Credentials for apps and AI providers stay in the engine data-dir and do not go to Supabase, according to the overview.
What it can do
From the README and self-host docs:
- A Foreman that builds the team. Say what you need; it hires coworkers and can answer them by your rules while you are away.
- Coworkers with memory and skills. Each has a soul, skills and memory that grow with tasks.
- One board. Every coworker, Box and running task in sight; chat with files, voice notes, tables and approvals inline.
- Integrations. A services catalog, any MCP server, and Composio for many apps. The README also mentions 200+ ready integrations.
- A computer per workspace. Browser and screen you can watch and take over; on open source you host the machine and attach it in one command.
- Schedules and webhooks. Work while you sleep; triggers without you at the keyboard.
- Models you choose. Default Rerun tiers on your OpenRouter key, plus your own provider keys or a Claude or ChatGPT subscription you already pay for.
- No seat limit on open source. The open-source vs Cloud page says unlimited coworkers and seats on your install, with no plan in between.
What you need
| Need | Required | What the docs say |
|---|---|---|
| Docker with Docker Compose | Yes | About 6 GB of memory available to Docker for the build, and about 60 GB of free disk (images and cache ~40 GB). |
| Node.js 22 | Yes | For npx supabase and the setup check. |
| Git | Yes | To clone the repository. |
| A Supabase project or local stack | Yes | Free project on supabase.com, open-source Supabase on your server, or npx supabase start on your computer. |
| An OpenRouter key | Yes for the Foreman | Runs the Foreman and the default Rerun model tiers. Without it the app can start, but the Foreman stays silent. |
| Other provider keys or plans | No | Optional Anthropic, OpenAI, Google, OpenRouter keys, or a Claude / ChatGPT plan, via the AI providers dialog. |
Install and first run
These steps follow the project's install guide and README. We have not run them. For an AI assistant doing the install, the repo also ships INSTALL.md.
Get the code and .env
Clone the repository, copy .env.example to .env, and fill the Supabase URL and keys, an OpenRouter key, NEXT_PUBLIC_APP_URL, and ADMIN_EMAILS. You need Docker, Node.js 22, and Git.
git clone https://github.com/rerun-build/rerun.git && cd rerun
cp .env.example .env
Keep NEXT_PUBLIC_APP_URL=http://localhost:3000 for a local try. For a team, use the HTTPS address people will open.
Apply the Supabase schema
Pick one path from the install guide: a project on supabase.com, open-source Supabase on your server, or everything on this computer with npx supabase start. Then push the schema and seed.
On supabase.com that is typically npx supabase link --project-ref <ref> and npx supabase db push --include-seed. The local stack uses npx supabase start and copies keys from npx supabase status.
Check and start
Run node scripts/self-host-check.mjs, then docker compose up -d --build. If Supabase is the local stack, use the local-supabase profile. Open the app URL and sign in with the email code.
node scripts/self-host-check.mjs
docker compose up -d --build
# local Supabase:
# docker compose --profile local-supabase up -d --build
Open http://localhost:3000 (or your NEXT_PUBLIC_APP_URL). Sign-in codes land in your inbox, or in Mailpit when using the local stack.
Meet the Foreman
Answer the Foreman in plain words so it can plan a team, or create a coworker yourself on the board. The first workspace uses the engine that docker compose started.
Later workspaces need a server of their own.
What is free and what costs money
- Open source. Free to run under AGPL-3.0. You pay model providers (OpenRouter and any keys or plans you connect). There is no Rerun plan or credit meter on the self-hosted install, according to the models and open-source docs.
- Rerun Cloud (optional). Hosted Rerun plus managed machines, included model credit, template library and premium features. Prices are left out on purpose; see rerun.build/pricing.
- Third-party services. Supabase, OpenRouter, Composio and other providers have their own accounts and terms.
Rerun vs Grok Bot
| Question | Rerun (open source) | Grok Bot |
|---|---|---|
| What it is | Open-source app (AGPL-3.0) you install; optional Rerun Cloud hosted tier. | A hosted app from xAI, on desktop and mobile. |
| The model | You bring OpenRouter and optional provider keys or Claude / ChatGPT plans; pick per coworker. | Comes with the plan that includes Grok Bot; usage draws from that plan's pool. |
| Where work runs | Your machines (app + engine per workspace); Cloud offers ready machines. | A persistent cloud computer in Cursor's cloud, shared by your Bots. |
| Laptop closed | Keeps working only while the host and engine stay up. | Work continues; closing the app or laptop does not stop a background turn or a routine. |
| Access | Free self-host; optional paid Cloud. | Included with certain X Subscription, Cursor, SuperGrok and Grok Business plans. |
See what Grok Bot is and alternatives to Grok Bot. The project's own compare page at rerun.build is marketing copy we have not verified line by line; we did not use its price claims on this page.
Limits of this guide
- We have not installed Rerun, started the Foreman, connected a provider or run a coworker. Everything above comes from the project's README, TRADEMARK.md, releases, website and self-hosting docs, plus the Grok Bot docs, checked on 2026-11-04. If we test it, the run will be logged here with the date, version, machine and output, following how we test.
- Rerun ships often (v0.5.0 was published 2026-11-03), so features and defaults can change after that release.
- Search demand for the AI coworkers product under the bare keyword “rerun” is weak and mixed with the robotics tool; treat this page as coverage for the X-signal keyword, not as a strong SEO volume bet.
FAQ
What is Rerun?
In this guide, Rerun is an open-source app of AI coworkers from the repository rerun-build/rerun. You self-host it under the AGPL-3.0 license. A guide called the Foreman helps you plan a team; each coworker has its own memory, skills and computer, and asks before it sends, pays or deletes anything. It is not the robotics multimodal data tool at rerun.io.
Is this the same as rerun.io?
No. The robotics data visualization and streaming project lives at rerun.io and github.com/rerun-io/rerun. This page is about the AI coworkers app at rerun.build and github.com/rerun-build/rerun. Searching for “rerun” or “rerun ai” often surfaces the robotics tool instead.
Is Rerun free?
The open-source build is free to run, modify and host under AGPL-3.0. You still bring an OpenRouter key (and optionally other provider keys or a Claude or ChatGPT plan) and pay those providers yourself. Rerun Cloud is a hosted option with its own plans; this page does not list prices—see the project's pricing page.
How do I install Rerun?
The install guide needs Docker with Docker Compose, Node.js 22, Git, a Supabase project (or the local Supabase stack), and an OpenRouter key. Clone the repo, fill .env, apply the schema, run the self-host check, then docker compose up -d --build and open the app URL.
Which models can Rerun use?
On a self-hosted install, the default Rerun tiers (Fast, Balanced, Smart) run through your OPENROUTER_API_KEY. You can also add Anthropic, OpenAI, Google or OpenRouter keys in the workspace AI providers dialog, or connect a Claude Pro/Max or ChatGPT Plus/Pro plan. Model choice is per coworker.
How is Rerun different from Grok Bot?
Rerun is software you install and run, or optionally use as Rerun Cloud. You bring the models and, on open source, you host the machines. Grok Bot is a hosted product whose Bots work on a persistent cloud computer in Cursor's cloud, with access from certain X Subscription, Cursor, SuperGrok or Grok Business plans. We have not run either for this page.
Related on bests.one
- What is Grok Bot — a hosted agent, for the comparison.
- Alternatives to Grok Bot
- Hermes Agent: what it is and how to start
- OpenClaw: what it is and how to start
- OpenMausBot: what it is and how to start
- How we test
Sources: Rerun README (GitHub), Rerun releases (GitHub), TRADEMARK.md (GitHub), Rerun website, Rerun pricing, Self-hosting overview (Rerun docs), Install (Rerun docs), Open source and Rerun Cloud (Rerun docs), AI models (Rerun docs), INSTALL.md for AI assistants (GitHub), rerun.io (robotics data tool — different product), rerun-io/rerun (GitHub — different product), Grok Bot (xAI docs), Grok Bot plans and billing. Checked on 2026-11-04.