Developer · 9 min
Supabase pricing explained: plans, compute, and spend caps
Understand organisation billing, project compute, included quotas, overages, and the limits of the Pro spend cap.
Supabase paid cost is not only a plan fee. Estimate the organisation subscription, compute for every active project, metered usage, and optional add-ons before production launch.
Understand organisations and projects
Each organisation has one plan and can contain multiple projects. Each project has its own Postgres compute, so adding projects can add cost even when database traffic is low.
Build a realistic estimate
- Count production, staging, preview, and development projects
- Estimate database size, egress, storage, active users, realtime messages, and function calls
- Include compute and add-ons that are not covered by ordinary quotas
- Review tax and the upcoming invoice in the billing dashboard
Know what the spend cap covers
- The Pro spend cap can restrict covered usage instead of charging overages
- Compute and several explicitly enabled add-ons are not covered
- A cap is not a substitute for alerts, application rate limits, and usage monitoring
- Test restriction behaviour before relying on it for a production service
Official sources
Prices and policies can change. Confirm the final terms on the official site before purchase.