Full-stack-as-a-Platform

These platforms try to collapse "backend, DB, auth, files, jobs, realtime" into one product with one SDK. They trade portability for radical productivity.

Convex

• Reactive database with TypeScript functions — write query/mutation/action functions in TS, the database is a typed document store, queries auto-update on the client.
• Realtime by default — every query subscription is live.
• Auth, files, scheduled jobs, search, vector all included.
• Self-host option released, but the managed SaaS is the main path.
• Why try it: "live queries" feels like cheating once you've used it. Worth a weekend project to internalize the paradigm.

Supabase

• Postgres + auth + storage + realtime + edge functions — open source, self-hostable, also has a generous managed tier.
• Postgres-first — you can drop into raw SQL whenever you want.
• Row-Level Security (RLS) is the auth model. Powerful, with a learning curve.
• Why try it: if you like Postgres, this is the most "you can take it with you" of the BaaS options.

Encore

• TypeScript and Go SDKs — declare services and the platform infers infrastructure (DBs, queues, secrets).
• Local-first dev experience — runs your whole topology on your laptop with a tracing UI.
• Deploy to your own cloud (AWS / GCP) or to Encore's managed platform.
• Why try it: if you've ever wanted "infrastructure-from-code" instead of Terraform/Pulumi, this is the cleanest take.

Firebase

• Still hugely popular in mobile / hobbyist contexts.
• Firestore for the DB, Auth, Storage, Cloud Functions, Cloud Messaging, Hosting.
• Vendor lock-in is real and exit costs are high.

Pocketbase

• Single-binary backend — embedded SQLite, auth, file storage, realtime, admin UI, all in one binary you scp to a VPS.
• Open source, self-host only.
• Why try it: the simplest possible "real backend" you can deploy. Great for prototypes and small products.

Appwrite

• Self-hostable BaaS — auth, DB (mongoid-style), storage, functions.
• Strong open-source positioning; competitive with Supabase if you don't need Postgres specifically.

When to pick a BaaS

• Solo / small team building product, not infra.
• Heavy realtime requirements (Convex, Supabase Realtime, Firestore).
• You want to spend time on UX, not on standing up Postgres + Redis + S3 + auth + queues.

When to skip

• You expect to grow into custom infra and want to delay lock-in.
• Your data model is complex enough that you'd fight the BaaS abstractions.
• You already have ops capacity — just running Postgres + your app is cheaper at any scale.