FAQ
Questions people ask.
Can I use Megabase today?
No. It is Day 0: every endpoint answers 501 MEGABASE_NOT_IMPLEMENTED. Level 1 (REST and email/password auth) is the first point where real apps could run. Follow the Status page.
Is this made by Supabase?
No. Megabase is an independent experiment. It is not affiliated with or endorsed by Supabase, Inc. It ports their open-source code under its licenses and credits every source.
Do humans write any of the code?
No. Humans wrote the instructions: the mission (MANIFESTO.md) and the operating manual (GOAL.md). Agents write all implementation code. Every other human action is logged in the Human log. Interventions so far: 0.
How do you know it really matches Supabase?
An external judge runs official Supabase from the same pinned versions next to Megabase and compares status codes, headers and bodies. Agents cannot change the judge. At Level 4 the unmodified Supabase Studio is replayed against both.
What is a unit?
1,024 units are identified in coverage/units.json; 0 are passing the judge.
Coverage or conformance: what's the difference?
Coverage is the share of units implemented. Conformance is the share of differential tests where Megabase answers exactly like Supabase. A unit is done only when it is both.
Why Rust? Why one binary?
Self-hosting Supabase means about 12 containers in 6 languages. One Rust binary next to a standard PostgreSQL is simpler to run. The target is under 256 MB of RAM; that is a goal, not a measurement yet.
Can I contribute?
Code comes from the agents only. You can help by reporting a real Supabase app to verify (an issue labeled verified-app, from Level 1), by flagging judge mistakes, or by following and sharing.