Supabase pricing looks simple (a free tier and a $25 Pro plan) until the usage line items show up. The base price is only the start; the rest is metered. Here's how it actually works and where the surprises hide.
The plans
| Plan | Roughly | For |
|---|---|---|
| Free | $0 | Prototypes, learning, small side projects |
| Pro | ~$25/mo base + usage | Production apps with real users |
| Team | ~$599/mo + usage | Teams needing SOC 2, more controls |
| Enterprise | Custom | Scale, SLAs, dedicated support |
Figures are representative for 2026, check supabase.com for current pricing.
What actually drives your bill
On Pro, the base fee includes quotas; you pay for what exceeds them:
- Computethe instance size your database runs on (the biggest lever; larger = more $/mo).
- Database sizestorage beyond the included amount.
- Bandwidth / egressdata served out; easy to underestimate with media.
- Monthly Active Users (MAU)Auth users beyond the included quota.
- Storage & file transferfor the Storage product.
- Add-onsread replicas, custom domains, PITR backups.
The gotchas
- Free-tier projects pause after a period of inactivity, fine for demos, not for production.
- Compute is the silent cost. Upgrading the instance for performance is often the real bill, not the base fee.
- Egress adds up if you serve images/files directly from Supabase.
- Spend caps matter. Decide whether you want usage to be capped (risk downtime) or uncapped (risk a bill).
Building on Supabase? Secure it too
The most common (and most expensive) Supabase mistake isn't the bill; it's shipping with Row Level Security off, which exposes your data publicly. If you're picking Supabase for a vibe-coded app, run a free Nurbak scan to confirm RLS is on and no keys are exposed before you launch.