Supabase splits its subscription price from its compute bill

The workload

Supabase prices three named project tiers on its own pricing page, and a separate billing document explains how the fixed subscription and usage-based components combine. The pricing page names each tier's included quota for database size, network egress and monthly active users (MAU), while the billing documentation, retrieved 16 September 2026, states that compute is billed separately from the subscription, so choosing a tier does not by itself fix the total bill. A founder must track both the plan price and the compute instance size chosen per project.

What the documents show

Verified: the Free tier costs $0 per month and includes a 500 MB database on a shared-CPU, 500 MB-RAM instance, 5 GB of egress plus 5 GB of cached egress, and 50,000 MAU, per the pricing page. Verified: the Pro tier costs $25 per month plus compute, and includes 8 GB of disk (then $0.125/GB), 250 GB of egress (then $0.09/GB) and 250 GB of cached egress (then $0.03/GB), and 100,000 MAU (then $0.00325 per additional MAU). Team costs $599 per month plus compute, at the same per-unit overage rates. Verified: the billing documentation states each paid plan includes a built-in usage quota, only usage beyond it is billed as overage, and all paid tiers include $10 per month of compute credit covering one Micro instance.

The operating cost

Verified: Free costs $0 per month, bounded by the figures above. Pro costs $25 per month plus compute, per the pricing page, and the billing documentation states project compute is charged independently of the subscription, so total Pro cost is not fixed at $25. Estimated: for a solo project whose compute is fully covered by the $10 monthly credit and whose usage stays within quota, the monthly total is $25; any egress, storage or MAU beyond that adds the stated per-unit overage, a total the pages cannot compute in advance.

The stop condition

Neither document names a spending ceiling. Editorially, the stop condition implied by the tier structure is usage-based: a Free project should move to Pro once its database size, egress or MAU risks hitting the Free tier's ceilings, since Free has no overage price and the consequence, per a companion entry, is that the project is instead paused rather than billed further. On Pro or Team, the point to reconsider is when recurring overage approaches the base subscription fee itself.

• Does the project's database size, egress and active-user count fit inside the Free tier's named quotas, or is it already paying for Pro in practice?
• Is the $10 monthly compute credit on a paid tier enough to cover the chosen compute instance size, or does compute add its own separate charge?
• Which single usage dimension (storage, egress or MAU) is closest to its included quota, and what does crossing it cost per unit?

A three-tier pricing page states clear entry prices, but the billing documentation is where the more consequential fact sits: compute is priced apart from the subscription on every paid tier, so the subscription price alone understates what a project actually costs.