PLEASE Help - TIME SENSITIVE - Scalability & Architecture Questions for Supabase
We’re building a web-based SaaS (with iOS & Android) using Supabase. Before full launch, we’d like to validate our architecture and scaling with real-world input.
1) Target scale:
We’re planning for 30,000+ active users across multiple organizations. Please share best practices and case studies (especially around database sizing, concurrency, cost-control). If you know of 5+ examples of orgs running web + mobile at this scale, even better.
2) Backend stack & hosting:
Front-end: Next.js (React/TS) or equivalent; mobile: React Native or Flutter. Hosting on Vercel or edge/serverless. We need guidance on:
Mixed web + iOS + Android clients raise mobile-specific needs: offline sync, push notifications, device data. What architecture/add-ons do you recommend for mobile scale?
4) Enterprise & compliance readiness:
We may serve enterprise clients (franchises or regulated industries). Please confirm support for:
If starting small (hundreds of users) and scaling to tens of thousands, what transitions or upgrade paths do you recommend (e.g., single instance → read-replicas → sharding)? What common pitfalls should we avoid?
6) Cost estimates:
What rough cost ranges should we expect at ~10,000 users and ~30,000 users? No need for exact numbers — just ball-park estimates for budgeting.
Thank you for your time and support. We look forward to your guidance.
1) Target scale:
We’re planning for 30,000+ active users across multiple organizations. Please share best practices and case studies (especially around database sizing, concurrency, cost-control). If you know of 5+ examples of orgs running web + mobile at this scale, even better.
2) Backend stack & hosting:
Front-end: Next.js (React/TS) or equivalent; mobile: React Native or Flutter. Hosting on Vercel or edge/serverless. We need guidance on:
- Read/write scaling (connection pools, read-replicas, geo-distribution)
- Limitations (writes/sec, heavy real-time, large media/file storage)
- Use of edge/serverless logic above Supabase
- Rough cost rules of thumb for 30k+ users (MAU, storage, bandwidth)
Mixed web + iOS + Android clients raise mobile-specific needs: offline sync, push notifications, device data. What architecture/add-ons do you recommend for mobile scale?
4) Enterprise & compliance readiness:
We may serve enterprise clients (franchises or regulated industries). Please confirm support for:
- Enterprise SLA terms
- SSO/SAML/RLS at scale
- Multi-tenant isolation patterns used by large clients
If starting small (hundreds of users) and scaling to tens of thousands, what transitions or upgrade paths do you recommend (e.g., single instance → read-replicas → sharding)? What common pitfalls should we avoid?
6) Cost estimates:
What rough cost ranges should we expect at ~10,000 users and ~30,000 users? No need for exact numbers — just ball-park estimates for budgeting.
Thank you for your time and support. We look forward to your guidance.
