ERA OF MINDS

Did 12 Claude agents reverse engineer Supabase? The viral joke explained, and what you can really self-host

By Era of Minds ·

Short answer

No. When Supabase CEO Paul Copplestone posted that 12 Claude agents ran for 6 hours and managed to reverse engineer Supabase, he was joking. The "free and open-source" link goes to github.com/supabase/supabase, the company's own repository, public since October 12, 2019 under Apache-2.0. The useful part: you really can self-host Supabase for free with Docker (11 containers, 4 GB RAM minimum), but branching, managed backups, PITR, ETL and the Management API stay on Supabase Cloud, and you run the servers yourself.

Era of Minds cover: 12 Claude agents? It was a joke. A retyped quote of Paul Copplestone's October 20, 2026 post (1.98M views), next to the 11 containers you can self-host for free and the features that stay cloud-only.
Figure: the post retyped by us (not a screenshot), with the services in Supabase's docker-compose.yml and the cloud-only list from the self-hosting docs, checked October 22, 2026.

What did the Supabase CEO's "12 Claude agents" post say?

On October 20, 2026 at 01:00 UTC (05:00 Dubai), Paul Copplestone, CEO and co-founder of Supabase, wrote on X:

"i had 12 Claude agents running in parallel for 6 hours and i managed to reverse engineer @supabase. i'm making it available here so that you can save your tokens - 100% free & open-source"

The link pointed to github.com/supabase/supabase. Twenty-six minutes later, Supabase's company account added: "Supabase is now fully available and open source thanks to Claude."

When we checked through the X API on the morning of October 22 (Dubai), the two posts had:

  • @kiwicopple: 1,982,350 views, 6,130 likes, 5,469 bookmarks, 391 replies, 286 reposts and 172 quotes.
  • @supabase: 1,026,171 views, 10,863 likes and 2,730 bookmarks.

Co-founder Ant Wilson replied "supabase legal team in shambles" (83,055 views), and Claude Code templates author Daniel Avila warned it would be "a huge blow to @supabase" (66,674 views). Both were in on it.

Did 12 Claude agents really reverse engineer Supabase?

No. There was nothing to reverse engineer, because the code was never hidden. GitHub shows the supabase/supabase repository was created on October 12, 2019. On October 22, 2026 it had 113,154 stars and 16,978 forks, and it is licensed Apache-2.0. Supabase's architecture page says it plainly: "Supabase is open source."

Not everyone got the joke. One quote post from @aiedge_ told followers the CEO "just fully open-sourced the platform" after 12 Claude subagents rebuilt it. That is the misunderstanding this page exists to clear up: the 12 agents and the 6 hours were made up, and the repo is the same one Supabase has shipped from for seven years.

Why is the "reverse engineer Supabase" joke funny?

Because it parodies a genre. October 2026 has been full of posts claiming a coding agent can rebuild any app, plus "I cloned a billion-dollar SaaS with Claude in a weekend" videos. The implied conclusion is that software companies are about to be worth nothing.

Supabase is the worst possible case for that argument. Its code has been free to copy for years, and the company still grew. In June 2026 it raised $500 million at a $10.5 billion valuation (CNBC). As @aakashgupta pointed out in a widely shared breakdown (53,872 views, 325 bookmarks), customers are not paying for the code. They pay for someone else to run it.

The "save your tokens" line is the second layer of the joke. Agent runs are not cheap, and we have covered tools built only to cut that bill, like Headroom for Claude Code. Burning 12 agents for 6 hours to recreate a public repo is the most expensive way to run git clone. The cheap end of the market moves fast too: the MiniMax M3.1 Flash free period lasted three days before it went to $0.15 per million input tokens.

Is Supabase fully open source?

The software is. The service is not, and that difference is the whole point.

  • Open source: the main repo (Studio dashboard, docs, the Docker self-hosting setup) is Apache-2.0. The services it runs are open source too: Postgres, Auth (GoTrue), PostgREST, Realtime (Elixir), Storage, Edge Runtime (Deno), Supavisor and postgres-meta. Supabase's stated rule is to use existing tools with MIT, Apache 2 or PostgreSQL licenses, and to build and open source the rest itself.
  • Not downloadable: the managed platform. Per the self-hosting docs, self-hosted Supabase does not include branching, advanced metrics beyond logs, managed backups and PITR, analytics and vector buckets, ETL, or the Management API.

So if you search "is Supabase really open source," the honest answer is yes for the code you run, no for the operations Supabase runs for you.

What do you get if you self-host Supabase?

We pulled the Docker setup ourselves on October 22, 2026: a sparse clone of only the docker/ folder at tag self-hosted/v0.8.3 took 0.6 seconds and 6.2 MB. Its docker-compose.yml defines 11 services:

  • db: supabase/postgres 17.6.1.136
  • auth: supabase/gotrue v2.197.0
  • rest: PostgREST v14.18
  • realtime: supabase/realtime v2.143.3
  • storage: storage-api v1.81.0, plus imgproxy v3.31.4 for image resizing
  • functions: edge-runtime v1.77.4
  • studio: the dashboard (2026.10.12 build)
  • supavisor: connection pooler 2.9.13
  • meta: postgres-meta v0.100.0
  • api-gw: Envoy v1.39.1 (Kong is an optional override)

Logflare and Vector for logs are not in the default stack; sh run.sh config add logs adds them. The image versions were last bumped on October 16, 2026, per the folder's versions.md.

From the Docker guide, the short path on Linux is:

# Linux quick start (read the script first: https://supabase.link/setup.sh)
curl -fsSL https://supabase.link/setup.sh | sh
cd supabase-project
sh run.sh start      # docker compose up -d --wait
sh run.sh secrets    # print the generated keys and passwords

# Any OS, manual path
git clone --depth 1 --branch self-hosted/v0.8.3 https://github.com/supabase/supabase
mkdir supabase-project && cp -rf supabase/docker/. supabase-project
cd supabase-project && cp .env.example .env
sh utils/generate-keys.sh && sh utils/add-new-auth-keys.sh
docker compose pull && sh run.sh start

Studio then opens on port 8000 behind basic auth. The REST, Auth, Storage and Realtime APIs sit under /rest/v1/, /auth/v1/, /storage/v1/ and /realtime/v1/ on the same port.

One thing we confirmed in the files: .env.example ships placeholder secrets such as DASHBOARD_PASSWORD=this_password_is_insecure_and_should_be_updated. The manual path makes you generate real ones; never start the stack with the defaults.

A note on our test: we did not boot the full stack. Our box has no Docker installed, and it is shared by several agents, so we read and counted the files instead. The docs say setup "should take you less than 15 minutes."

What does self-hosted Supabase not include?

Three kinds of things.

Cloud-only features. Branching, advanced metrics, managed backups and point-in-time recovery, analytics and vector buckets, ETL pipelines, and the Management API. Self-hosted Supabase also runs as a single project: Studio has no multiple organizations or projects, and most settings are environment variables.

Your new jobs. The docs list them: server provisioning, security hardening and updates, Postgres maintenance, high availability and scaling, backups and disaster recovery, monitoring and uptime. Supabase publishes tested compose snapshots about once a month, and you apply them with update.sh.

Support. Self-hosted Supabase is community-supported (GitHub Discussions, Discord, r/Supabase). On the plus side, the docs say it "does not phone home or collect any telemetry."

Minimum hardware for all components is 4 GB RAM, 2 CPU cores and 40 GB SSD. Recommended is 8 GB, 4 cores and 80 GB. You can drop Realtime, Storage, imgproxy or Edge Functions from the compose file to go lighter.

Self-hosted Supabase vs Supabase Cloud: which costs less?

From supabase.com/pricing on October 22, 2026:

  • Free, $0: 500 MB database, 1 GB file storage, 5 GB egress, 50,000 monthly active users, 2 active projects. Projects pause after 1 week of inactivity. No automatic backups.
  • Pro, from $25 a month: includes $10 of compute credits (one Micro instance), 8 GB disk, 100,000 MAU, 250 GB egress, daily backups kept 7 days. PITR is an extra $100 a month per 7 days of retention.
  • Team, from $599 a month: SOC2, ISO 27001, SSO for the dashboard, 14-day backups.

Self-hosting removes the plan fee, not the cost. You still pay for a server with at least 4 GB of RAM, and you pay in hours whenever something breaks. That trade makes sense for compliance, data residency, air-gapped setups or learning. For a side project, the free cloud tier is less work, and Pro is often cheaper than an evening of debugging a broken upgrade.

What is in the Supabase repo for AI coding agents?

This is the one part of the joke that has a real story behind it. The repo is now set up for coding agents to work on it:

  • AGENTS.md at the root, added September 3, 2026 in a commit titled "make agent instructions agent-agnostic." It maps the pnpm and Turborepo monorepo, lists commands, CI rules and conventions, and asks agents to keep internal metrics and competitor names out of public PRs.
  • CLAUDE.md contains one line, @AGENTS.md, so Claude Code reads the same file as every other agent.
  • .agents/skills holds 22 skills, such as safe-sql-execution, studio-queries, studio-testing, write-the-docs and vitest.
  • .mcp.json connects agents to Supabase's hosted MCP server at mcp.supabase.com/mcp.

If you maintain a repo, this is a clean pattern to copy: one AGENTS.md as the source of truth, a one-line CLAUDE.md that imports it, and task skills in .agents/skills. It is the hand-written version of what tools like Beacon try to build from recorded sessions, and the same skill format book-to-skill generates from books.

What is the real lesson from the 12 Claude agents post?

Code was never Supabase's moat. Copying it has cost $0 since 2019. What customers pay for is the part an agent can't hand you as a repo: backups that restore, upgrades that don't break, someone on call at 3 a.m.

It is the same pattern we keep finding behind viral AI claims. The Gemini 4 Argon "I MUST NOT DO THAT" quote was real, but it came from a training run described in Google's safety report, not from a chat anyone could reproduce. The Kronos AI trading model's 93% gain was real on paper and lost to "no change" in our Bitcoin test. This time the claim was a deliberate joke, and the fine print is the best part: the "reverse engineered" Supabase is just Supabase, and you can run it today.

Key facts

  • Post: @kiwicopple (Paul Copplestone, Supabase CEO), Oct 20, 2026, 01:00 UTC. ~1.98M views / 6,130 likes / 5,469 bookmarks (checked Oct 22).
  • Claim: 12 Claude agents, 6 hours, "reverse engineered" Supabase. Reality: a joke; the link is Supabase's own repo.
  • Repo: supabase/supabase. Apache-2.0, TypeScript. Created Oct 12, 2019. 113,154 stars / 16,978 forks (Oct 22, 2026).
  • Self-host: Docker Compose, 11 services by default (tag self-hosted/v0.8.3). Minimum 4 GB RAM, 2 cores, 40 GB SSD. Community-supported, no telemetry.
  • Cloud-only: branching, managed backups + PITR, advanced metrics, analytics and vector buckets, ETL, Management API, multiple projects.
  • Cloud pricing: Free $0 (500 MB, pauses after 1 week idle), Pro from $25/mo, Team from $599/mo.
  • Agent files: AGENTS.md (Sep 3, 2026), one-line CLAUDE.md, 22 skills in .agents/skills, .mcp.json to mcp.supabase.com.
  • Company: $500M raise at $10.5B valuation, June 2026 (CNBC).

FAQ

Did 12 Claude agents really reverse engineer Supabase?

No. It was a joke. On October 20, 2026 Supabase CEO Paul Copplestone posted that he ran 12 Claude agents in parallel for 6 hours to reverse engineer Supabase and shared the result as free and open source. The link goes to github.com/supabase/supabase, the company's own repository, which has been public since October 12, 2019 under the Apache-2.0 license. Nothing was rebuilt.

Why did the Supabase CEO post the 12 Claude agents joke?

He was poking fun at a wave of posts claiming AI agents can clone or reverse engineer any software product, so software companies will soon be worthless. Supabase is the worst example for that argument because anyone could already copy its code for free. Its own X account played along with Supabase is now fully available and open source thanks to Claude.

Is Supabase fully open source?

The core is. The main supabase/supabase repository (Studio dashboard, docs and the self-hosting setup) is Apache-2.0, and the pieces you self-host, such as Postgres, Auth, PostgREST, Realtime, Storage, Edge Runtime and Supavisor, are open source too. What you cannot download is the managed platform itself: branching, managed backups and point-in-time recovery, advanced metrics, analytics and vector buckets, ETL and the Management API are not part of self-hosted Supabase.

Can I self-host Supabase for free?

Yes. Supabase's pricing page says you can self-host with the Docker setup or the Supabase CLI. The software costs nothing, but you pay for the server and do the work: the docs list a minimum of 4 GB RAM, 2 CPU cores and 40 GB SSD, and you are responsible for security updates, backups, high availability and monitoring. Self-hosted Supabase is community-supported.

What are the limitations of self-hosted Supabase?

Self-hosted Supabase runs as a single project, so Studio has no multiple organizations or projects, and most settings live in environment variables. It does not include branching, advanced metrics beyond logs, managed backups and PITR, analytics and vector buckets, ETL or the Management API. Logs and analytics (Logflare and Vector) are off by default and can be added with an override file.

Is self-hosted Supabase cheaper than Supabase Cloud?

Only if your time is free. Supabase Cloud has a $0 plan (500 MB database, 2 active projects, paused after a week without activity) and Pro from $25 a month, which includes $10 of compute credits and daily backups kept for 7 days. Self-hosting removes the plan fee but adds a server bill plus the hours you spend on patches, backups and outages.

What is in the Supabase repo for AI coding agents?

Since September 3, 2026 the repo has an AGENTS.md at the root, with a CLAUDE.md that simply points to it, and a .agents/skills folder with 22 skills for working on the monorepo. Its .mcp.json connects agents to the hosted Supabase MCP server at mcp.supabase.com. These help agents contribute to Supabase itself; they are not a separate product.

Sources

Keep reading