Supabase pricing jump from free to pro tier
π§ workproduct problemSingle report βββββ
A solo developer reports that Supabase's pricing structure lacks a middle tier, forcing a jump from a free plan to a $25/month Pro plan when egress limits are exceeded, which causes an immediate hard-fail of the application.
What people do today
- Upgrading to the $25/month Pro plan
- Waiting for the billing cycle to reset
π§ Fix this
Ideas a builder, maker or community group could start on:
- A 'pay-as-you-go' overage model for egress that allows apps to continue running without forcing a full tier upgrade.
- A 'Solo' tier priced at $5-10/month with scaled-down resource limits between the free and Pro tiers.
- A notification system that provides a soft warning before hitting hard limits to allow for optimization or billing adjustments.
Real voices
βInstead of a soft warning or overage billing, the project hard-fails. Every API request returns 402.β
Related problems
π§ workproduct13 reports
Indeed job feed ignores user preferences
π§ workproduct10 reportsInability to filter AI-generated content on LinkedIn
π§ workproduct8 reportsLinkedIn login verification loop
FixHumanityDaily
The most important new problems, and ideas to fix them, in your inbox.
Placeholder: no data is collected yet.