
Reviews Embed
Built a full marketplace as a solo founder on Supabase (auth, postgres, RLS, storage, edge functions, realtime, serverless webpages). I'd have needed a small backend team to wire all of that up myself. Postgres underneath means I'm never locked in and never fighting a custom DSL.
RLS in particular is the unlock, security policies live next to the data, not buried in middleware that drifts out of sync.
Running Supabase locally feels like having a full backend “starter kit” living right next to your code.
I spin it up and suddenly I’ve got Postgres, auth, file storage, and realtime all running together, plus a clean web dashboard so I’m not wrestling with random containers or config files. It still feels like my stack though - it’s just Postgres and open-source services under the hood, so there’s no weird lock-in or mystery billing later.
For side projects and experiments, local Supabase has basically become my default backend: I start it, point my app at it, and I’m off building features instead of wiring up yet another database + auth + storage combo.
