13 documented complaints against Supabase — paraphrased from BBB filings, Trustpilot reviews, Reddit threads, and public forum posts. Newest complaints first.
Sourced from public platforms across US, UK, and global markets — each report links to the original source.
Billing Problems
HIGH
Source: Reddit · Mar 14, 2025
Added 23d ago
Unpredictable Usage-Based Bills Shock Developers on Free and Pro Tiers
Supabase's usage-based pricing model has repeatedly caught developers off guard, with hobbyist projects suddenly accumulating charges for egress, storage reads, and realtime connections that weren't clearly communicated upfront. Multiple Reddit and Hacker News threads from 2024 and 2025 describe developers waking up to bills of $50–$400 on projects they considered low-traffic. The free tier's pausing behavior — where inactive projects get suspended after one week — also causes confusion when users upgrade just to keep a project alive, then face a recurring $25/month Pro plan charge they didn't fully anticipate.
"I thought I was building a side project on the free plan. Then realtime kicked in during a small traffic spike and my bill jumped to $180 in a single month. Nothing in the onboarding made that risk obvious."
Customer Complaints
HIGH
Source: News · Feb 28, 2026
Added 23d ago
Supabase Blocked in India Under IT Act 69A Disrupts Live Applications
In late February 2026, Supabase was blocked in India under Section 69A of the Information Technology Act, cutting off access for an unknown number of Indian users and businesses running production applications on the platform. The block appeared sudden, with no advance notice to affected customers, leaving teams scrambling to implement VPN workarounds or migrate database endpoints. Supabase acknowledged the situation but had limited ability to force a swift resolution given the government mandate.
"Our entire backend runs on Supabase and our Indian users just couldn't connect. We had zero warning. Support told us to use a VPN as a workaround — that's not a fix for a production app."
Support Failures
HIGH
Source: G2 · Jul 22, 2025
Added 23d ago
Pro Plan Support Response Times Leave Paying Customers in the Dark
Developers on Supabase's $25/month Pro plan consistently report that support ticket response times stretch from 48 to 96 hours, even for database outage situations. G2 and Hacker News threads from 2024–2025 note that the company's support infrastructure hasn't kept pace with its rapid user growth following high-profile funding rounds. Meaningful SLA guarantees only kick in at the $599/month Team plan, a fact that many Pro users say wasn't made clear when they signed up.
"My production database was throwing 500s for six hours. I had a ticket open with Supabase support and didn't hear back for two days. Two days. On a paid plan."
Customer Complaints
MEDIUM
Source: Reddit · Apr 18, 2025
Added 23d ago
Row-Level Security Misconfigurations Lead to Accidental Data Exposure
A recurring pattern in Supabase community forums and Reddit from 2023 through 2025 involves developers accidentally exposing data because they didn't realize Supabase tables are publicly readable by default via the auto-generated REST API when Row Level Security (RLS) is disabled. Supabase has added more warnings to its dashboard, but the problem persists: users spin up a project assuming sensible defaults and only learn about the exposure after a security audit or an outright breach. At least a handful of startup post-mortems cited Supabase's default open API exposure as a contributing factor.
"We shipped our MVP with Supabase and six months later a security researcher told us our entire users table was queryable without authentication. RLS was off and we had no idea that was the default."
Support Failures
MEDIUM
Source: G2 · Aug 30, 2024
Added 23d ago
Database Backups on Free Plan Are Nonexistent — Policy Buried in Docs
Supabase does not provide point-in-time recovery or automated backups on the free tier, and daily backups only start at the $25/month Pro plan. Several developers discovered this the hard way after accidental table drops or botched migrations left them with no recovery path. The policy is documented, but it sits several clicks deep in the platform's documentation and isn't surfaced during project creation or in dashboard warnings. G2 reviewers in 2024 specifically called this a dangerous omission for any developer who treats their free-tier project as a learning environment but stores real data.
"I dropped a table by accident during a migration gone wrong on the free plan. I opened a support ticket hoping Supabase kept backups. They don't, and nowhere obvious told me that before it happened."
Churn & Retention
MEDIUM
Source: Hacker News · Jan 9, 2025
Added 23d ago
Free-Tier Project Pausing Policy Drives Developers Away Before They Convert
Supabase pauses free-tier database projects after seven days of inactivity, which has become one of the most-cited frustrations on Reddit and Hacker News among early-stage builders. While the policy is documented, new users routinely discover it only after their project goes dark mid-demo or mid-hackathon. The workaround — upgrading to the $25/month Pro plan — feels punitive to users who are still evaluating the platform, and many report simply moving to alternatives like PlanetScale, Neon, or self-hosted PostgreSQL rather than paying to keep a test project alive.
"I was demoing my app to potential co-founders and Supabase had paused my database. Zero email warning that morning. That was the day I decided to self-host Postgres instead."
Misleading Marketing
MEDIUM
Source: News · Mar 22, 2026
Added 23d ago
'Open Source' Branding Obscures Proprietary Managed-Service Lock-In Risks
Supabase markets itself prominently as open source, but the practical reality for most users is that they're running on Supabase's managed cloud, where key features — including their Edge Functions infrastructure, Realtime server, and dashboard tooling — aren't straightforwardly self-hostable without significant engineering effort. A March 2026 comparison piece highlighted that migrating away from managed Supabase to a self-hosted stack requires rebuilding auth integrations, storage bucket logic, and realtime subscriptions from scratch, contradicting the implied portability of the open-source pitch. Several Capterra reviewers from 2024–2025 specifically flagged this gap between the marketing and migration reality.
"They say open source like it means you can leave whenever you want. When we tried to self-host after a pricing change, we realized we'd built against their proprietary Realtime layer. Migration took three weeks of engineering time."
Billing Problems
MEDIUM
Source: Trustpilot · Nov 5, 2024
Added 23d ago
Egress and Storage Read Costs Not Prominently Displayed in Pricing Calculator
Supabase's pricing page leads with per-project dollar amounts but buries egress fees ($0.09/GB after the free allowance) and storage read/write costs in smaller print. Developers building media-heavy apps or applications with high read frequency have reported that their actual monthly bills ran 3–5x what the pricing calculator suggested when they only input row counts and project numbers. Trustpilot and Capterra reviews from late 2024 and 2025 call out the calculator as misleading for anything beyond a basic CRUD app.
"The pricing calculator said maybe $30 a month. My first real bill was $140. The difference was all egress and storage reads, neither of which the calculator made obvious."
Customer Complaints
LOW
Source: Reddit · Feb 11, 2025
Added 23d ago
Realtime Feature Instability Reported During Connection Spikes
Supabase's Realtime feature, which lets clients subscribe to database changes via websocket, has drawn complaints about dropped connections and message delivery failures during traffic spikes. Teams building collaborative apps or live dashboards reported in 2024 and early 2025 that Realtime connections would silently drop and not reconnect without a client-side workaround, leading to stale UI states. Supabase has pushed multiple Realtime v2 improvements, but the underlying reliability concerns continue to show up in community channels for projects running on the lower-tier plans.
"Our collab feature uses Supabase Realtime. During our launch day, connections started dropping silently. Users saw outdated data and had no idea. We spent the whole day firefighting something the platform was supposed to handle."
Churn & Retention
LOW
Source: Hacker News · Jun 3, 2025
Added 23d ago
Edge Functions Cold Start Latency Pushes Performance-Sensitive Teams Away
Supabase Edge Functions, built on Deno Deploy, have drawn consistent criticism for cold start times that can exceed 1–2 seconds when a function hasn't been called recently. For teams building user-facing features that need sub-200ms response times, this makes Edge Functions effectively unusable without architectural workarounds like scheduled keep-alive pings. Multiple Hacker News and Discord threads from 2025 document teams switching to Cloudflare Workers or AWS Lambda for latency-critical workloads while keeping Supabase only for database access.
"We loved Supabase for the database side, but Edge Functions were killing our API response times with cold starts. We ended up running Cloudflare Workers in front of it just to keep latency acceptable."
Billing Problems
MEDIUM
Source: G2
Added 3mo ago
Bandwidth and compute add-on overages harder to predict than base plan cost
Growing projects describe the base subscription cost being manageable, but bandwidth and compute add-ons scaling unpredictably once real user traffic arrives.
Customer Complaints
MEDIUM
Source: Reddit
Added 3mo ago
Free-tier projects paused after inactivity, surprising developers
Developers report returning to free-tier projects after a week or two of inactivity to find the database paused, requiring manual restoration and causing downtime for side projects and demos.
Support Failures
LOW
Source: Reddit
Added 3mo ago
Community support can be slow for complex self-hosting issues
Developers self-hosting Supabase describe getting fast community help for common issues, but slower resolution times for complex infrastructure problems compared to a paid enterprise support plan.