Supabase Problems & Issues
Real user-reported problems, complaints, and limitations for Supabase. Based on analysis of 15 signals.
Overall score: 62/100
Issues by Category
Supabase project paused - free projects pause after 1 week
Free projects with low activity over 7 days are paused automatically; paused projects can be restored from the dashboard for up to a year. Users report demos breaking and run keep-alive cron jobs to avoid it. Free projects also have no backups.
Unexpected billing - charged for ghost compute
Users report being charged $300+ when expecting $25/month due to 'ghost compute' resources. Billing for resources users weren't aware they were using. Support often unresponsive while charges accumulate. Small unpaid bills ($16) result in immediate project suspension.
Why is my Supabase bill so high? Per-project compute adds up
Pro is $25 but each project is billed its own compute; the $10 credit covers only one Micro instance, so a second project adds $10+ and larger instances run $60-$410/month. Egress allowance rose to 250 GB on Pro, but MAU, disk, PITR ($100/month) and add-ons still push small apps past $100/month.
Team plan jumps to $599/month - big leap from $25 Pro
The jump from Pro ($25/month) to Team ($599/month) is huge, and Team keeps the same usage quotas as Pro - the money buys SOC 2, ISO 27001, scoped roles, SSO and longer backups/logs. Uptime SLAs need Enterprise with custom pricing.
Supabase down again? Outages still frequent in 2026
Status trackers log hundreds of Supabase incidents since 2021. In September 2026 alone: Nano projects became unresponsive after long uptime (fixed by manual restart), a Dashboard/permissions incident and an eu-west-1 hardware failure; in August project creation failed for ~2.7 hours.
Real-time subscription limits cause dropped connections
Subscription limit exceeded errors when active subscriptions surpass plan limits. Connection limits cause WebSocket drops. JavaScript timer throttling prevents heartbeats, causing silent disconnections. High-concurrency apps hit these limits quickly.
Auth emails stop sending - 'email rate limit exceeded'
The built-in email sender is only meant for testing and allows a handful of auth emails per hour, so confirmation and password-reset emails silently stop once real users sign up. Custom SMTP is effectively mandatory for production.
Auth errors and email link failures
500 errors in Auth typically indicate database or SMTP provider issues. Email link authentication commonly fails with 'Database error finding user from email link.' Session timeouts and bugs cause work loss. Auth-helpers package being deprecated adds migration burden.
RLS policies complex and impact performance significantly
Row Level Security is powerful but performance impact is significant, especially for queries scanning every row. Calling functions in RLS policies evaluates for each row, causing slowdowns. Complex workflows still need app-level checks. Learning curve is steep for developers.
Local development with CLI is unreliable - Docker issues
The Supabase CLI for local development has broken Docker containers, migration system issues, and breaks frequently. Val Town reported the CLI couldn't be reliably used - migrations failed, containers wouldn't start. Forces developers to test against remote database.
Database hits connection limits as user base grows
Each compute instance has maximum database connections and connection pooler limits. Real-world reports of queries taking 8+ seconds, database hitting connection limits, and real-time subscriptions dropping constantly as user base grows. Throttling occurs when IOPS limits hit.
Edge Functions cold starts and execution limits
Edge Functions have 60-second execution limit and 2-second CPU time per request. Cold starts historically ranged from 400ms to 1.2s. Web Worker API not available. Heavy long-running jobs must be moved to background workers. Not suitable for all serverless use cases.
No live chat even on Enterprise - support feels outdated
No live chat support even on Enterprise plans, which feels outdated in 2026. No phone support at any tier. Free users get Discord community support with variable response times. Complex Postgres issues get bounced back as 'database questions, not Supabase questions.'
Inconsistent documentation frustrates developers
Documentation is inconsistent and can frustrate developers navigating advanced features. Lack of easy access logs makes debugging database issues challenging. Knowledge base needs more troubleshooting guides for edge cases. Auth documentation especially problematic.
Can't connect to Supabase database - direct connection is IPv6 only
The direct host db.<ref>.supabase.co resolves only to IPv6, so many hosts (Railway, Fly regions, home networks, some CI) fail with 'Network is unreachable'. The free fix is the Supavisor pooler string; a dedicated IPv4 address is a paid add-on.
Regret Patterns
Common reasons users regret choosing Supabase.
Free project paused right before demo/launch
Users sign up expecting 'free backend' only to have their project pause after a week of development. Scrambling to upgrade or restore before an important demo or launch. The 7-day pause policy isn't prominently communicated.
Unexpected bill 10x higher than expected
Users on Pro plan expecting ~$25/month receive bills for $100-300+ due to egress, compute, or storage overages. Usage-based pricing makes costs unpredictable. Some report 'ghost compute' charges for resources they weren't using.
RLS policies killed query performance at scale
Developers implement RLS for security, then discover queries slow to 8+ seconds as data grows. Performance impact wasn't apparent during development with small datasets. Requires significant refactoring to optimize.
Local development CLI broke mid-project
CLI worked initially but broke after update, leaving developers unable to run migrations locally. Had to test against remote database, slowing development. Some teams migrated away citing local dev issues.
Outage during critical business moment
Database went offline during product launch, demo, or high-traffic period. Support wasn't responsive. Some users lost customers and revenue. Led to loss of trust in platform reliability for production use.
Needed team features but Team plan costs $599/month
Started on Pro, then needed SSO or team collaboration. Discovered the only option is Team at $599/month - a 24x price increase. No middle-ground plan available. Felt trapped between features and budget.
When Supabase Breaks Down
Specific scenarios where Supabase fails or underperforms.
Running a production app on free tier
Your app works in development but pauses after 7 days without traffic in production. Critical for any app needing 24/7 availability. Must upgrade to Pro ($25/month) or find workarounds.
App with high bandwidth/media serving
Egress costs at $0.09/GB add up fast for apps serving images, videos, or heavy API responses. Small app can jump from $25 to $100+/month unexpectedly. Calculate bandwidth needs before committing.
Complex RLS policies on large tables
Row Level Security evaluates per-row, causing severe slowdowns on tables with millions of rows. Queries taking 8+ seconds. Requires query optimization, indexing, or hybrid auth approach.
High-concurrency real-time app
Subscription and connection limits cause dropped connections. WebSocket heartbeats fail under throttling. Apps with many concurrent users hit limits quickly, causing poor user experience.
Need urgent support during incident
Database goes down and you need immediate help. Free tier has Discord only. Pro has email with variable response times. No live chat or phone at any tier. Enterprise is only tier with dedicated support.
Small team needing SSO or compliance
Growing startup needs SSO/SAML for enterprise clients or SOC 2 compliance. Only available on Team plan at $599/month. No middle ground between $25 Pro and $599 Team.
Local development workflow
Need to develop and test locally before deploying. CLI has Docker issues, migration failures, and breaks after updates. Some developers forced to test against remote database, slowing iteration.