Nubase vs Supabase
Supabase is an excellent open-source backend, but its self-hosted stack is built around a single project and has no built-in memory layer. Nubase keeps the parts that work — Postgres, REST, JWTs, Row Level Security, Storage and a Studio — and adds first-class Memory, an AI Gateway, native MCP tooling and many isolated projects from one self-hosted control plane.
| Capability | Supabase | Nubase |
|---|---|---|
| License | Apache-2.0 | Apache-2.0 |
| Multi-project self-hosting | Single project (self-hosted) | Many isolated projects, one Studio |
| Project isolation | One local project | Dedicated Postgres database per project |
| Database API | PostgREST | PostgREST-compatible |
| Auth | Yes | Email, OAuth, MFA, OTP, SSO |
| Storage | Yes (S3) | S3 / R2-compatible |
| Built-in AI memory | No | First-class Memory pillar |
| AI Gateway (OpenAI/Anthropic) | No | Per-project keys + usage |
| MCP for coding agents | No | Native — Claude & Codex |
| Realtime / Edge Functions | Yes | Not yet |
Why teams choose Nubase
- Memory is a first-class primitive — extraction, entity graph and hybrid retrieval, not a separate vector script.
- One control plane provisions and routes to many isolated project databases.
- Coding agents operate it over MCP: schema, SQL, auth, storage and memory.
When Supabase is the better pick
Pick Supabase if you need Realtime or Edge Functions today, or want a managed cloud with a single dedicated project.
FAQ
Is Nubase a drop-in Supabase replacement?
Nubase follows the Supabase developer model (apikey + Bearer JWT, PostgREST-style REST, RLS), so Supabase-style clients feel at home — but it is not byte-for-byte API compatible and does not yet implement Realtime or Edge Functions.
Can I self-host many projects?
Yes. Unlike single-project self-hosted Supabase, one Nubase control plane manages many projects, each with its own database, JWT secret and roles.