Supabase: the backend you stand up in an afternoon
If you need users, data, and auth without building a backend from scratch, this is the default. Here's the honest version — including the one thing that will bite you.
What it actually is
Supabase gives you a real PostgreSQL database — not a proprietary document store, an actual relational database you can take with you — wrapped in the parts a product needs: authentication, file storage, realtime subscriptions, edge functions, and auto-generated REST and GraphQL APIs over your tables. The pitch is "the open-source Firebase alternative," but the more useful framing is: it's the 80% of backend plumbing you'd otherwise rebuild on every project, ready in minutes.
In my stack it's the backend behind Folio and my reach-for default on anything that needs accounts and per-user data. The reason is simple: the distance from "empty project" to "logged-in users reading only their own rows" is hours, not a sprint.
Why it's in my stack
- It's real Postgres. You're not locked into a weird query model. SQL, migrations, foreign keys, the whole relational toolbox. If you ever outgrow Supabase, your database is portable.
- Auth is included and good. Email/password, magic links, OAuth providers, and row-level security that ties auth to data access. That combination is the part most people dread building.
- The studio is genuinely usable. A table editor, SQL editor, and a log viewer that make the first weeks of a project fast.
- Generous free tier. You can build, launch, and get your first real users without paying — which matters when you're bootstrapping.
Pricing tiers (the shape, not the fine print)
Verify current numbers on Supabase's pricing page — these move — but the structure is stable:
| Tier | Roughly who it's for | The catch |
|---|---|---|
| Free | Side projects, MVPs, first users. Two projects, a small database, generous monthly active users on auth. | Projects pause after ~a week of inactivity; storage and DB size are capped. |
| Pro | A launched product with real usage. A flat monthly base plus usage, daily backups, no pausing, email support. | Usage-based add-ons stack on top of the base — watch bandwidth and database size. |
| Team / Enterprise | Companies needing SOC 2, SSO, and priority support. | Priced for businesses, not solo founders. |
Who it's for — and who it isn't
Right for you if: you're building an app that needs auth and a real relational database, you like SQL (or are willing to), and you want to ship the product instead of the infrastructure. It's an excellent fit for the solo founder and the small team.
Look elsewhere if: you want a pure managed Postgres with nothing else (consider Neon), or you need a heavily customized backend where Supabase's conventions would fight you more than help. For most indie products, those aren't the situation.
Why it gets a deep dive
Supabase lists integration and agency partners, not an affiliate program, so this link earns nothing. It gets a deep dive because it is the backend I actually build on.
// no affiliate program