Platform · 2020–now · Platform Wars
Supabase
Firebase's shape on Postgres. Auth, storage, and a database you can still dump.
How Supabase mutated
Supabase mutated backend-as-a-service by putting it back on SQL. Parse died on a shutdown clock. Firebase hid a document model until the bill. A Postgres API with row-level security is a real exit — and the actual authorization boundary. Generated apps that skip those policies are a client mistake, not a verdict on the company. It stuck with teams that wanted a weekend backend and a relational escape hatch. It fails when the dashboard is treated as a security model.
Patterns
Sources
Compare with
Related
Platform · 2014–now
Firebase
Auth, realtime DB, and hosting as a product. Prototype paradise; vendor lock purgatory at scale.
Platform · 2011–2017
Parse
BaaS before Firebase owned the category. Open-sourced on the way out; trust never recovered.
$ Facebook shut down Parse with a year's notice, forcing thousands of mobile backends into emergency migrations or self-hosted forks.
Platform · 1996–now
PostgreSQL
The open-source relational default — JSON, extensions, and enough correctness to survive every NoSQL wave.
Platform · 1974–now
SQL / Relational
Declarative data that outlived every ORM fashion cycle. Postgres and friends keep winning by being boring.