SUPABASE BILL ESTIMATOR · RUNS IN YOUR BROWSER

What will your Supabase bill be, and what cuts it most?

Enter your usage from the Supabase dashboard and get an estimated monthly bill by line and a ranked list of levers (compute rightsizing, egress trimming, database cleanup, storage cleanup, Edge Function caching, Realtime batching, fake sign-up blocking) with a dollar saving for each.

Nothing is uploaded. Calculated in this browser from numbers you enter and approximate list prices you can edit. It cannot see your plan or your invoice.

1. Your monthly usage

Prices, allowances and assumptions (editable)

LinePrice per unit (USD)Included per month

Change a price here and press Estimate. Defaults are approximate list prices; check supabase.com/pricing and your plan.

Prefer a CLI, or want a budget gate in CI?

node cli.mjs template > usage.csv
node cli.mjs estimate usage.csv
node cli.mjs estimate usage.csv --budget 500      # exit 1 over budget
node cli.mjs estimate usage.csv --set egress_gb=2000 --json
node cli.mjs estimate usage.csv --prices prices.json --assume assumptions.json

Get cli.mjs and engine.mjs — Node 18+, nothing to install, no network call. More: how to reduce your Supabase bill.

Common questions

Does this read my Supabase account or invoice?

No. It reads only the usage numbers you type or paste (copy them from the Usage page of your Supabase dashboard) and multiplies them by list prices you can edit. It cannot see your plan, regions, spend limits, enterprise contract or real invoice. Treat every figure as a way to compare options, never as what you will be charged.

Where do the prices come from?

They are approximate public Pro-plan list prices from Supabase's pricing documentation as best known in 2025 (Pro is $25 per organization per month), shown with an as-of date, and every one is editable, including the included allowances (the bundled $10 compute credit is modeled as the compute line's allowance). Supabase changes prices and packaging, so check supabase.com/pricing before relying on a number.

How is the saving for each lever calculated?

Each lever re-runs the estimate with one change applied under an assumption shown beside it (for example, rightsizing that removes 30% of compute spend) and reports the difference. The assumptions are editable. Levers overlap, so the savings are not additive.

Is my usage data uploaded anywhere?

No. The browser page calculates in your own browser and never sends anything. The CLI reads a local file or stdin and makes no network call.