Vercel, Railway, and Render's own domains each covered a platform for deploying YOUR code. Supabase is a genuinely different category — a backend-as-a-service, meaning a large fraction of what you'd otherwise have to build yourself (auth, an API, realtime, storage) already exists, wired around a real, unrestricted database.
2 min read
Every platform covered so far in this subcategory runs code a team writes — a Next.js app, an API server, a worker. Supabase is different in kind: it's a backend-as-a-service (BaaS), meaning entire categories of backend work — user authentication, an API layer, realtime subscriptions, file storage — already exist, built around a real Postgres database, rather than being something a team builds from scratch on top of a bare database connection.
Supabase is frequently described as "the open-source Firebase alternative" — but the comparison that actually matters technically is narrower and more specific: Firebase's Firestore is a proprietary NoSQL document store, while Supabase's database is genuinely, fully Postgres — the exact same relational database Databases & SQL's own domain teaches, with every feature that implies (real joins, transactions, constraints, the full SQL language) rather than a restricted subset designed around a different data model entirely. A team that outgrows Firebase's document-store limitations often has to migrate data models entirely; a team using Supabase can always drop to raw SQL, because there's nothing proprietary underneath to migrate away from in the first place.
Postgres database — the foundation everything else sits on top of
Row Level Security — Postgres's own access-control feature (lesson 2)
Auto-generated REST API — PostgREST, turning tables into endpoints (lesson 3)
Auth — user management, social login, JWTs (lesson 4)
Realtime — subscribing to database changes live (lesson 5)
Storage — S3-compatible file storage (lesson 6)
Edge Functions — Deno-based serverless functions (lesson 7)
Each piece is genuinely optional — a team can use Supabase purely as a managed Postgres database (ignoring Auth, Realtime, Storage entirely) exactly the way Vercel's own domain described choosing Vercel Postgres as "just a database." The full value of Supabase specifically comes from how deeply these pieces integrate with each other — most visibly, how RLS policies reference Supabase Auth's own user identity directly (lesson 2), which is the one integration this curriculum's own devreps app has already relied on directly for its lesson-videos feature.
Check your understanding
A quick comprehension check — not tracked, not graded, just for you.
1. What category of platform is Supabase, as distinct from Vercel, Railway, and Render?
2. Why does the comparison "real, unrestricted Postgres vs. Firebase's Firestore" matter more than the generic "open-source Firebase alternative" label?
3. Can a team use Supabase purely as a managed Postgres database, ignoring Auth, Realtime, and Storage?
Supabase