Supabase pricing cliff forces solo builders into expensive tier
🧭 workproduct problemSingle report ●●●●●
A solo builder 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. The user notes that exceeding the 5GB free egress cap causes an immediate hard-fail of all user-facing services, including logins and signups, rather than a soft warning or incremental overage billing.
What people do today
- Upgrading to the $25/month Pro plan
- Waiting for the billing cycle to reset
- Self-hosting PostgREST
🔧 Fix this
Ideas a builder, maker or community group could start on:
- A 'pay-as-you-go' overage model for egress that allows projects to stay online without forcing a jump to a high-cost monthly subscription.
- A lightweight 'Solo' tier priced between $5-$10/month that offers higher egress limits than the free tier without enterprise-level features.
- An automated notification system that provides a grace period or soft warning when a project approaches its egress limit, preventing sudden service outages.
Real voices
“Instead of a soft warning or overage billing, the project hard-fails. Every API request returns 402. Login breaks. Signups break.”
Related problems
🧭 workproduct9 reports
Indeed job feed ignores user preferences
🧭 workproduct8 reportsInability to filter AI-generated content on LinkedIn
🧭 workproduct7 reportsLinkedIn login verification loop
FixHumanityDaily
The most important new problems, and ideas to fix them, in your inbox.
Placeholder: no data is collected yet.