Supabase pricing cliff forces expensive upgrade for solo builders
π§ workproduct problemSingle report βββββ
A solo builder reports that Supabase's pricing model forces an immediate jump from a free tier to a $25/month Pro tier when egress limits are exceeded, with no intermediate options for small-scale projects. The user notes that exceeding the 5GB egress cap causes the entire application to hard-fail, breaking user-facing features like login and signups, which creates significant operational risk for small developers.
What people do today
- Upgrading to the $25/month Pro tier
- Waiting for the billing cycle to reset
- Self-hosting PostgREST
π§ Fix this
Ideas a builder, maker or community group could start on:
- Develop a 'pay-as-you-go' overage billing model for egress that allows projects to stay online without forcing a jump to the full Pro tier.
- Create a 'Solo' tier priced between $5-$10/month that offers higher egress limits than the free tier but fewer enterprise features than the Pro tier.
- Implement a 'soft-fail' or 'grace period' system that sends alerts when approaching limits instead of immediately disabling all API requests.
Real voices
βInstead of a soft warning or overage billing, the project hard-fails. Every API request returns 402.β
Related problems
π§ workproduct17 reports
Indeed job feed ignores user preferences
π§ workproduct11 reportsInability to filter AI-generated content on LinkedIn
π§ workproduct10 reportsLinkedIn login verification loop
FixHumanityDaily
The most important new problems, and ideas to fix them, in your inbox.
Placeholder: no data is collected yet.