What people actually say about Supabase
101 mentions across 6 sources · 63% positive · researched Oct 13, 2026
Hacker News, YouTube, Product Hunt, Stack Overflow, GitHub, Lemmy
What users praise
- • Real Postgres with full SQL, not a NoSQL abstraction that limits queries later
- • Auth with Row Level Security gives row-by-row access control out of the box
- • Instant REST APIs via PostgREST mean no hand-written CRUD endpoints
What frustrates them
- • Edge Functions cap CPU at roughly 2 seconds, limiting heavier serverless workloads
- • RLS policies have a steep learning curve and are easy to misconfigure dangerously
- • AI assistants frequently generate broken Supabase code, especially connection strings and joins
This is a summary. The full report adds every quote we found, a per-source breakdown, recurring themes, hidden costs and the learning curve — run a free scan below, or see the full Supabase review.
What comes up again and again about Supabase
Recurring themes across everything we collected, with where each one showed up.
Relational Postgres beats NoSQL for real apps
praised · seen on YouTube, Hacker News
Deno acquisition raises Edge Function runtime questions
criticised · seen on Hacker News
RLS and SQL fluency create an intermediate skill floor
mixed · seen on Stack Overflow, Hacker News
AI-generated Supabase code often breaks
criticised · seen on Stack Overflow
Open-source portability is the key differentiator vs Firebase
praised · seen on Product Hunt, Hacker News
Bundled platform (auth + storage + realtime) saves backend assembly
praised · seen on YouTube, Product Hunt
MCP and Cursor/Claude Code integration is gaining traction
praised · seen on Hacker News
Edge Function CPU limits restrict heavier workloads
criticised · seen on YouTube
How hard is Supabase to learn?
Users describe it as intermediate · typically A few hours to get going
Where people get stuck
- • Writing correct RLS policies requires understanding SQL and Postgres roles
- • Connecting via the pooler needs the right connection string, which AI tools get wrong
- • Edge Function runtime (Deno) differs from Node.js, causing environment mismatches
- • Self-hosting involves orchestrating Postgres, PostgREST, Realtime, and Storage
Who Supabase actually suits
Works well for
- • Startups and product teams that want Postgres with auth, storage, and realtime bundled
- • Developers migrating off Firebase who want SQL and an open-source exit
- • AI app builders storing and querying vector embeddings alongside relational data
- • Full-stack engineers comfortable with SQL who want to skip backend boilerplate
Not the right fit for
- • Absolute beginners who want zero server management and no SQL
- • Teams needing long-running serverless compute beyond a few seconds of CPU
- • Projects where Firebase's NoSQL and no-config defaults are a deliberate fit
- • Enterprises requiring granular infrastructure control like AWS RDS or GCP
What people are discussing right now
Discussion volume is high and trending up
- Supabase vs Firebase relational database debate
- Deno acquisition impact on Edge Functions
- MCP server adoption by Claude Code and Cursor
- RLS policy configuration and best practices
- Turso acquisition and edge database strategy
- Scoped personal access tokens and enterprise security
What people really think about Supabase
A real-time sweep of the open web — social media, forums, review sites, video reviews and live community discussions — distilled into one honest verdict with the actual mentions behind it.
What's inside your Supabase report
Everything you need to decide — distilled from real, current user opinion.
Live mentions
The actual posts, reviews & complaints about Supabase — with links and dates.
Honest verdict
A straight answer on whether it lives up to the hype — and who it’s really for.
Praise & gripes
What users genuinely love and the frustrations that keep coming up.
Real quotes
Representative voices from real users, not marketing copy.
Recurring themes
The patterns across hundreds of opinions, surfaced at a glance.
Red flags
Hidden costs and dealbreakers people only discover after signing up.
How it works
Sign up free
Create an account in seconds — get 5 free scans, no card.
We sweep the web
Live social media, forums, reviews & video opinions — in ~30–60s.
Get your report
An honest, downloadable verdict with the real mentions behind it.
Ready to see the real verdict on Supabase?
Your scan is ready in under a minute · $1.
Top alternatives to Supabase
Researching options? Explore the closest alternatives.
Neon
Neon is serverless Postgres with database branching, autoscaling, and scale-to-zero for apps and AI agents
Firebase
Firebase is Google's app development platform for shipping AI-powered mobile and web apps with managed backend, auth and Gemini
Render
Render deploys web services, Postgres, Key Value, and durable workflows from a Git repo with load-based autoscaling
Gadget
Gadget builds and hosts full-stack JavaScript apps with a managed Postgres database, auto-generated APIs, and an AI assistant.
Db2rest
Db2Rest turns PostgreSQL, MySQL, MariaDB, CockroachDB, and SQLite into instant REST data APIs with no ORM.
ClickHouse
ClickHouse is an open-source columnar OLAP database for real-time analytics on billions of rows.
Check sentiment on these too
Run a live scan on the alternatives before you decide.
Supabase — questions buyers ask
What do people complain about most with Supabase?
The complaints that recur most often are edge Functions cap CPU at roughly 2 seconds, limiting heavier serverless workloads, RLS policies have a steep learning curve and are easy to misconfigure dangerously and AI assistants frequently generate broken Supabase code, especially connection strings and joins. Drawn from 101 mentions across 6 sources.
What do users like about Supabase?
Users consistently praise real Postgres with full SQL, not a NoSQL abstraction that limits queries later, auth with Row Level Security gives row-by-row access control out of the box and instant REST APIs via PostgREST mean no hand-written CRUD endpoints.
Is Supabase hard to learn?
Users describe it as intermediate; most people are up and running in a few hours; the usual sticking points are writing correct RLS policies requires understanding SQL and Postgres roles and connecting via the pooler needs the right connection string, which AI tools get wrong.
Who should not use Supabase?
Based on what users report, it is a poor fit for absolute beginners who want zero server management and no SQL, teams needing long-running serverless compute beyond a few seconds of CPU and projects where Firebase's NoSQL and no-config defaults are a deliberate fit.
What are people saying about Supabase right now?
Discussion volume is high and trending up. Current topics: supabase vs Firebase relational database debate, deno acquisition impact on Edge Functions and MCP server adoption by Claude Code and Cursor.
How current is this report?
Each scan runs live the moment you click — it reflects what people are saying now, and every report lists the dated mentions behind it.
Can I download it?
Yes — download the full report as a polished, shareable PDF.