Product Feedback: Free Tier Architecture, Egress Models, and Founder Runway

[navyask911]

Dear Supabase Product & Leadership Team,

I am writing to share feedback as an early-stage creator and non-technical founder building an application (VibeSync) on Supabase. Tools like Supabase have made building ambitious software accessible, but several structural limits in the current free tier create steep bottlenecks before pre-revenue projects can even validate product-market fit.

I would like to highlight key friction points and share suggestions on how Supabase could better support emerging builders:

1. Free Egress & Storage Alignment (The Cloudflare R2 Model)
   Currently, egress is capped at 5 GB on the free tier. When building media-rich or interactive products, this forces developers to route file storage entirely to Cloudflare R2, which offers 10 GB free storage with zero bandwidth/egress fees ($0.00/GB). Providing unmetered or significantly higher baseline egress for file storage would keep developers within the Supabase ecosystem instead of offloading storage externally.

2. Database Sizing: Expanding from 500 MB to 5 GB
   A 500 MB database cap behaves like a "full bottle with a tiny neck." For data-intensive applications, indexing, and modern schemas, 500 MB gets consumed very quickly during testing and early adoption. Expanding the free allowance to at least 5 GB per project would give early builders the runway needed to launch and gather real traction before hitting hard infrastructure barriers.

3. Log Query Constraints During Early Development
   Non-technical founders working closely with AI tools run iterative debugging sessions that naturally generate large log query volumes. Even with low ingestion, inspecting logs easily exceeds the planned 100 GB log query limit. An allowance structure that doesn't penalize active debugging would greatly reduce anxiety for learners and solo builders.

4. Built-in Authentication & Open-Source Integrations
   Expanding out-of-the-box authentication to include localized and zero-friction identity providers (such as Truecaller verification or wider plug-and-play open-source identity adapters) would substantially reduce friction for builders targeting global and mobile-first markets.

A program or tier offering generous infrastructure until a startup reaches verified revenue or investment would nurture the next wave of breakout products directly on your platform. Just as developers grow into paying enterprise customers, supporting upcoming founders at the earliest stage creates long-term platform loyalty.

Thank you for your dedication to open source and developer tooling, and for considering this feedback.

Warm regards,
VibeSync Team