Ask HN: 超过 Supabase 的免费→$25 定价门槛。有没有中端选项？
独立开发者因Supabase免费层级出站流量限制导致应用功能失效，需升级至Pro层级（$25/月）或等待重置。Pro层级提供250GB流量，是免费配额的50倍，但缺乏中间选项，使部分开发者面临资源不足与成本之间的困境。
1 分•作者: cgozdemm•大约 2 小时前
我是一个独立开发者。我从一月份开始在Supabase的免费层级上运行sqlquest.app——一个自适应的SQL教学工具。流量很小，可能每天只有10到20个真实的会话。不过每次页面加载都会涉及5到6个表，当你的应用正确地进行状态同步时，出站流量会迅速累积。
我超出了每月5GB免费出站流量的限额约15%。而不是给出软警告或计费超支，项目会直接失败。每个API请求都返回402错误。登录无法进行，注册也无法进行，所有面向用户的功能都失效了。
有两个选择：
1. 等待账单周期重置，并希望“重置后的短延迟”不会持续数小时（它确实如此）
2. 升级到Pro层级，每月25美元，立刻恢复使用
就在这个情况发生时，我距离一个实际的付费学生演示只有20分钟。我支付了25美元。
Pro层级提供250GB的出站流量——是我所需50倍的量。对于那些超出免费限额但又不需要企业级资源的独立开发者来说，没有中间层级可选。
针对HackerNews的问题：
1. 有人遇到过这种情况吗？如何...
查看原文
Solo builder here. I'm running sqlquest.app — an adaptive SQL tutor — on Supabase's free tier since January. Traffic is tiny, maybe 10-20 real sessions a day. Every page load touches 5-6 tables though, and egress adds up quick when your app does state sync properly.<p>Went ~15% over the 5GB/month free egress cap. Instead of a soft warning or overage billing, the project hard-fails. Every API request returns 402. Login breaks. Signups break. Everything user-facing dies.<p>Two options:
1. Wait for the billing cycle to reset and hope the "short delay after reset" doesn't stretch into hours (it did)
2. Upgrade to Pro at $25/mo, instantly unblocked<p>I was 20 minutes from a live paid student demo when this hit. Paid the $25.<p>The $25 tier gives 250GB egress — 50× what I need. There's no middle ground for solo builders who've crossed the free cap but don't need enterprise headroom.<p>Questions for HN:<p>1. Has anyone else hit this? How'd you handle it?
2. Any existing workarounds (PostgREST + self-hosted, different provider with better pricing ladder)?
3. Is there a case to be made to Supabase for a $5-10/mo "solo" tier between Free and Pro? Or is the $25 tier strategically important for their unit economics?<p>Not trying to bash the product — I love the DX and I'm not switching. Just frustrated with the pricing jump. Curious if the community has opinions.