Supabase

I tested Supabase by building 2 production applications on it (a SaaS web app with auth + database + storage + realtime subscriptions, and a smaller admin tool with RLS policies), running them across the free tier and Pro tier over a month. Disclosure: MytheAi itself runs on Supabase, so I have additional production-scale familiarity with the platform beyond a typical demo. The cohort I had in mind was indie developers and small engineering teams wanting a Firebase-alternative on Postgres with auth, storage, and realtime bundled, distinct from Railway (S157) which is general-purpose PaaS hosting and from Neon or PlanetScale which are pure database services without the BaaS layer.

The Postgres-first plus bundled-services model is the actual product. Spinning up a project gets you a Postgres database, a Postgres-backed auth system, S3-compatible storage, realtime websocket subscriptions, and an auto-generated REST plus GraphQL plus client SDK in roughly 5 minutes. Row-Level Security policies with Postgres `auth.uid()` provide multi-tenant isolation at the database layer rather than at the application layer, which removes a class of authorization bugs. The Postgres choice (versus Firebase NoSQL) keeps you on standard SQL skills and migration paths to other Postgres providers later. Pricing on the free tier is generous for personal projects and indie products and the Pro tier at 25 dollars per month covers serious production traffic.

What broke me was the rough edges around scale and operational maturity. Cold-start latency on serverless edge functions adds 200-400ms which is noticeable on user-facing API calls. The Realtime subscriptions handle thousands of concurrent connections fine but past the 10k mark you need careful channel design to avoid bandwidth costs. The dashboard occasionally shows stale data after schema changes which has tripped me up debugging migrations. Some integrations I expected to be deep are still developing (custom SMTP for transactional email, certain auth providers) where workarounds add complexity. The self-hosted option exists but operating it is a significant ops investment.

Supabase is the right pick for indie developers, small teams, and bootstrapped SaaS companies wanting bundled BaaS on Postgres with reasonable pricing and standard SQL skills. Skip it if your scale is consistently above 100k monthly active users where the bandwidth and database-tier costs ramp aggressively (consider managed Postgres plus separate auth like Clerk plus dedicated storage), if your team needs Firebase-specific features (Firestore offline-sync, FCM push notifications) where Firebase is still stronger, or if you need enterprise-grade SLA and support that the platform is still maturing toward.