Supabase Review

Five billion. That's Supabase's October 2025 valuation after Accel led a $200M Series D at $2B in April, then $100M more came in four months later. The market just told you Postgres won the BaaS argument Firebase used to own.

Paul Copplestone and Ant Wilson founded this in 2020. The platform ships pgvector for embeddings, Row Level Security at the database layer, and Edge Functions for serverless logic. Pro is $25/month per project. The free tier covers 500MB and 50,000 monthly active users — bottoms-up adoption isn't faked here.

But the jump from Pro at $25 to Team at $599 is steep, and the AI-workload pricing this round funds hasn't fully shipped. Run one production app on Pro for 90 days. If row-level security holds and the meter behaves, standardize. If not, you've spent $75.

I've been using Supabase across multiple projects for the past year, and it's transformed how quickly we can ship features. The managed Postgres with built-in auth, real-time subscriptions, and edge functions means my team spends less time on infrastructure and more time building. The postgres-first approach gives us confidence - we're not locked into proprietary query languages.

What really sold me was watching our junior developers become productive within days. The dashboard is intuitive, the TypeScript SDK is excellent, and the automatic API generation from database schemas saves weeks of work. Performance has been solid even as we've scaled to hundreds of thousands of users on our main app.

Postgres is the part you don't lose. The Auth schema, Storage policies, and Realtime broker are the parts you do — and that's where the real CTO question lives. Lock-in for Supabase sits in the management plane, not the database itself.

Pro at $25 per project ships an 8GB Postgres with pgvector, Edge Functions, and Row Level Security policies running inside the database. The October 2025 Series E at $5B — led by Accel and Peak XV, four months after the $200M Series D — buys roadmap confidence for a 3-year commitment.

But versus Firebase, you're trading a proprietary BaaS for a portable database plus a proprietary control plane. Versus Neon plus Clerk plus Cloudflare Workers, you trade integration speed for fewer vendors to replace. The 3-year call is which lock-in you'd rather own.

I've been using Supabase daily since we migrated our main product from Firebase. The JavaScript SDK just clicks - auth flows that used to take days now take hours. Row Level Security was confusing at first, but once it clicked, it's incredibly powerful for multi-tenant apps.

What really won me over is the realtime subscriptions. We built a collaborative feature in two days that would've taken weeks before. The auto-generated APIs from your database schema feel like magic, though sometimes I wish I had more control over the exact shape of responses.

My biggest gripe? When complex RLS policies fail, the error messages can be cryptic. I've lost hours debugging why a query returns empty when it's actually a permissions issue.

I'll admit, when our engineering team first suggested Supabase for our marketing infrastructure, I was skeptical. But over the past year, it's become invaluable for powering our data-driven campaigns. We use it to store customer interaction data, build custom dashboards, and even power some of our interactive marketing experiences.

The real-time subscriptions have been game-changing for live campaign monitoring. During product launches, I can watch engagement metrics update instantly. The auth system simplified our gated content strategy too.

The learning curve was steep initially - this isn't your typical marketing tool. But once we got comfortable with SQL queries and the dashboard, we could build exactly what we needed without waiting for IT tickets.

I've been using Supabase for our internal tools and customer-facing applications since we migrated from AWS RDS last year. The financial impact has been remarkable - our monthly database costs dropped from $3,200 to under $1,000 while supporting 3x more users. What really sold me was the predictable pricing model. Unlike AWS where I'd get surprise bills from data transfer or IOPS, Supabase's pricing is straightforward: you pay for compute, storage, and bandwidth. Period. The free tier handled our development environments perfectly, saving us another $500/month. My only gripe is that enterprise features like SOC2 compliance reports require custom pricing discussions, which made budgeting tricky during our security audit season.

Supavisor is the first thing an Engineer notices that other Firebase clones skip. Connection pooling for serverless workloads is the difference between a side project surviving a Hacker News spike and one throwing 'too many connections' at the worst moment.

The pgvector extension with HNSW indexing matters more than the marketing site suggests. Storing 1536-dimension embeddings next to relational data, querying both in one SQL statement — PlanetScale can't do that, Firebase doesn't pretend to. For RAG prototypes, real workflow win.

However, the 8GB database cap on the $25/month Pro tier hits sooner than expected once embeddings scale, forcing compute add-ons or a Team jump to $599. Docs read like engineers wrote them — CLI examples first, screenshots last — and an $80M Series C in September 2024 means the roadmap probably ships.

I've been using Supabase daily for about 14 months now, and it's become my go-to for any project that needs a database and auth. The magic is how quickly I can spin up what used to take weeks - database, authentication, real-time subscriptions, all ready in minutes. The dashboard is clean and intuitive, and I love being able to write SQL directly when I need to.

What really sold me was the developer experience. Everything just works together - the JS client is a joy to use, and features like Row Level Security finally make sense. Sure, I've hit some documentation gaps and the occasional service hiccup, but the team is responsive and things keep getting better. For the price, especially on the free tier, it's incredible value.

I jumped on Supabase early, excited about open-source Firebase with Postgres. For simple CRUD apps, it's fine. But push it harder and cracks show everywhere. Their auth system randomly throws 'refresh token expired' errors that take hours to debug. Database connections drop during migrations with zero warning. The realtime features work... until they don't, usually right when a client demos.

What kills me is their roadmap promises. Edge functions were 'coming soon' for 6 months. Row-level security is powerful but the UI makes it impossible to debug why queries fail. I've lost entire days to their documentation being out of sync with actual behavior.

I'm migrating to managed Postgres + Auth0. More setup, but at least things work predictably.