Free tier projects automatically pause after 7 days without traffic. Users report constantly receiving pause warnings even for small active projects. This makes the free tier unsuitable for any production app requiring 24/7 uptime. Feels like 'sabotaging free users to force upgrades.'

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.

The jump from Pro ($25/month) to Team ($599/month) is massive. No middle ground for small teams needing collaboration features. Many team features locked behind this expensive tier. Enterprise requires sales calls with minimum $15,000/year contracts.

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.'

Egress charges ($0.09/GB uncached, $0.03/GB cached) add up quickly. Storage limits, database size, compute power, and bandwidth all get taxed once real users arrive. A small app can unexpectedly jump from $25 to $100+/month. Moving data out of Supabase is not cheap.

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 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.

StatusGator has collected data on over 691 outages affecting Supabase users over the past 3+ years. Users report database going offline during critical times. Some left for Firebase after experiencing multiple outages, concluding they couldn't trust it for production.

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.

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.

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.

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.

Users report difficulty connecting to Postgres through their IDE due to network setup limitations. IPv4 access requires purchasing an add-on. This is frustrating for developers used to direct database access in other tools.

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.