Supabase
An open-source Firebase alternative — Postgres database, auth, real-time subscriptions, storage, and edge functions in one platform. Free tier, self-hostable. The fastest way to get a production backend without building one.
Paul Copplestone, Ant Wilson · Co-founded Supabase in 2020
- New projects needing a backend fast.
- Real-time apps (chat, live updates).
- When you want Postgres + auth without building it.
- Prototypes and MVPs.
- When you need full control (self-host Postgres).
- High-scale apps (manage your own infra).
- When you need a specific database (not Postgres).
Definition
Supabase is a backend-as-a-service built on PostgreSQL. You get: a real Postgres database, auth (email, OAuth, magic links), real-time subscriptions (websockets), storage (S3-compatible), edge functions (Deno), and auto-generated APIs (REST, GraphQL via PostgREST).
Why it exists
Building auth, database, real-time, and storage from scratch is weeks of work. Supabase gives you a production backend in minutes — open source and Postgres-based (no vendor lock-in to a proprietary database).
How it works
Create a project → get a Postgres database + auto-generated API. Auth UI handles signup/login. Real-time via Supabase Realtime (websockets on Postgres changes). Storage buckets for files. Edge Functions (Deno) for serverless logic. Client libraries for JS/TS, Python, etc.
Scaling limits
Postgres limits (connection pooling needed — use Supabase Pooler). Real-time scales to a point. Edge functions have limits. Free tier is generous but has limits. Vendor lock-in to Supabase APIs (mitigated by Postgres being standard SQL).
Cost shape
Free tier (500MB DB, 1GB storage, 2M edge function calls). Pro $25/month. Pay for more.
Alternatives
- Firebase — Google's BaaS, NoSQL, more mature, more lock-in.
- PlanetScale — MySQL-only, serverless, no auth/real-time.
- Custom backend — Full control, more work.
Failure modes
- Connection limits (use pooler).
- Free tier limits.
- Real-time scaling.
- Edge function limits.
- Vendor lock-in to APIs.