Supabase Pricing 2026: Free, Pro and the Real Monthly Bill

Supabase lists Pro at $25 a month, and for one small project that is the whole bill. It grows in two places the plan cards make easy to miss: every extra project, and every step up in database compute. Below are the plans exactly as Supabase publishes them (read on October 18, 2026), the compute table that decides most real bills, and four worked examples.

TL;DR: the gotcha

Pro is $25 for one project on the smallest compute size. Paid plans come with a $10 monthly compute credit, which covers exactly one Micro instance (shared CPU, 1 GB of RAM). A second project, such as staging, adds at least $10. Moving production to a bigger instance adds that instance's price minus the $10 credit: Medium (4 GB of RAM) is $60, Large (2 dedicated vCPUs, 8 GB) is $110.

The Free plan really is $0, but it pauses a project after a week without activity and allows two active projects. That suits a demo, not something people rely on.

The plans, exactly

API requests are unlimited on every plan; Supabase does not charge per query. Team adds SOC 2 and ISO 27001, SSO for the dashboard, and HIPAA as a paid add-on. Enterprise is priced on request.

Compute is the real price list

Every Supabase project is its own Postgres instance, billed by the hour at these monthly rates:

The $10 credit covers one Micro instance or takes $10 off any larger one. It does not stretch to a second project.

What real bills look like

The last row is $25 for the plan, $100 for Large after the credit, $5.25 for 42 GB of extra disk and $13.50 for 150 GB of extra egress.

Add-ons that appear later: point-in-time recovery from $100 a month for 7 days of history, a custom domain for $10 a month, log drains at $60 per drain a month, branching at $0.01344 per branch per hour, phone multi-factor auth at $75 a month for the first project, and disk IOPS above the included 3,000 at $0.024 each.

The one you will actually hit

The first limit most growing apps meet is not a quota on the plan card; it is the size of the machine. Micro has 1 GB of RAM, a shared CPU and 60 direct connections. When queries slow down or connections run out, the fix is a bigger instance, and that is the step where $25 becomes $75 (Medium, one project) or $125 (Large).

Pro also starts with a spend cap switched on. Supabase's own description: the cap keeps costs inside the plan's included quota, and you switch it off to pay for anything beyond it. Check it before a launch, so that a traffic spike is billed instead of capped.

What changed in 2026

On October 2, 2026, Turso announced that Supabase is acquiring it. Turso builds lightweight SQLite databases meant to be created by the thousand, one per agent or per user, and the stated plan is a path from those databases into Postgres on Supabase. Turso says its databases, APIs and plans keep running as they are, and Supabase's pricing page did not list any Turso product when we checked. If you price Turso today, use Turso's own plans.

When Supabase is the right call anyway

Supabase is good value when you use what it bundles: relational data, auth with 100,000 monthly active users included, file storage, realtime and edge functions, all for one plan fee plus compute. Because there is no per-request charge, a read-heavy app pays the same compute bill at ten queries a second as at one, as long as its instance keeps up; only egress grows with traffic. And it is plain Postgres, so leaving is a database dump, not a rewrite.

If all you need is key-value

We build BaseKV, a disk-backed key-value store, so weigh this paragraph accordingly. If the data you keep is sessions, feature flags, caches or one document per user, an hourly-billed Postgres instance is more machine than the job needs. Put your own numbers into the KV cost calculator to compare Supabase with DynamoDB, Upstash, Cloudflare Workers KV, Turso and BaseKV on the same workload.

---

Related: KV cost calculator, When Supabase is too complex, Turso pricing and free tier limits, Just use Postgres, or a KV store?