Supabase Pricing Explained: What an MVP Pays

Supabase's pricing page says "from $25 a month", and for most MVPs that's roughly what you'll pay. The catch is the word "from": compute, extra projects, backups and several add-ons sit outside that number, and some of them escape the spend cap that's meant to protect you. Here's what each plan includes, what founders forget, and the real bill at four stages.

How much does Supabase cost for an MVP?

$0 while you validate on the Free plan, then about $25 a month on Pro once real users depend on the app — the $10 monthly compute credit covers your first project's default server, so the plan fee is the whole bill. Expect $25 to $50 a month for a launched MVP with modest traffic; the bill climbs into the hundreds only when you add larger compute, point-in-time recovery or the Team plan.

Supabase bills per organisation: a plan fee, hourly compute for each project, and usage beyond quotas pooled across the organisation. Every project is its own Postgres server, so every project adds compute.

What does each Supabase plan include?

Prices are in USD as of October 2026, from Supabase's pricing page. Vendors change pricing, so check it before you commit.

Team's extra $574 a month buys SOC 2 and ISO 27001 coverage, dashboard SSO, finer access roles and priority support — answers for an enterprise security questionnaire, not features users notice. Almost every MVP belongs on Pro.

Is the Supabase Free plan enough for an MVP?

For building and validating, yes; for a product paying customers rely on, no. The quotas are generous — 50,000 MAU is more than most MVPs have at launch — which makes it a strong free-tier backend. The catches are operational:

• Projects pause after a week of inactivity. The demo nobody touched over a holiday is asleep when an investor clicks the link. Restoring takes a click.
• Two active projects, counted across every organisation where you're an Owner or Admin.
• No automatic backups. Supabase tells Free users to export regularly with the CLI's db dump command and keep off-site copies.
• 500 MB database cap. Exceed it and the project goes read-only.
• No mixing plans. An organisation is entirely Free or entirely paid, so a free staging project needs its own Free organisation.

Our rule: stay on Free until someone outside your team depends on the app.

How does the Supabase Pro plan's $25 a month work?

The $25 is the organisation's plan fee; compute is billed on top, per project, by the hour, and the $10 monthly compute credit is subtracted from it. The credit covers exactly one project on the default Micro size, which is why a single-project Pro bill is $25. Credits reset monthly and don't roll over.

Sizes run up to 16XL at ~$3,730 a month. Three details catch founders out:

• Every extra project is another server. Staging inside your Pro organisation adds ~$10 a month, because production already used the credit.
• Credits only cover project compute — not read replicas or preview branches.
• Disk is billed as provisioned, not used. It grows 50% automatically when 90% full, so 8 GB becomes 12 GB once your data passes ~7.2 GB. Pennies at $0.125 per GB, but it's on the invoice.

What happens when you hit the Supabase spend cap?

On Pro the spend cap is on by default: once you exceed a quota, Supabase blocks further usage of that item instead of charging for it — and if you keep exceeding it, your projects get restricted. After a warning and a grace period, restrictions can mean paused projects, read-only databases or HTTP 402 errors on API requests. They lift at the next billing cycle, or immediately if you switch the cap off.

The cap covers metered usage — egress, disk, MAUs, storage, invocations, Realtime, logs — but nothing you opt into, such as compute, PITR or the other add-ons below. A capped account still gets a bigger invoice the moment someone upsizes the database. And it's binary: there's no "warn me at $100" setting.

Keep the cap on until launch, then switch it off. A pre-launch project shouldn't run up a bill; a live product shouldn't go read-only because customers uploaded more than expected. Overages are cheap — an extra 100 GB of egress is $9 — so watch the usage page instead of risking downtime.

Which Supabase add-ons do founders forget to budget for?

PITR matters most. With daily backups alone, a bad migration at 5pm can cost most of a day's customer data; PITR restores to any second in its window. It needs at least Small compute and replaces daily backups once enabled. For a B2B product holding customer records, $100 a month is cheap insurance — though rarely before anyone pays you.

What will Supabase actually cost at each stage?

Illustrative estimates from October 2026 list prices: one organisation, spend cap off in (c) and (d).

The jump from (c) to (d) comes mostly from Large compute and PITR, not from users: 25,000 MAU is a quarter of Pro's quota. If (d)'s buyers demand a SOC 2 report, the same setup on Team comes to ~$856.

Supabase is one line of your running costs; the rest is broken down in what it costs to maintain a SaaS.

Is Supabase cheaper than Firebase, Neon or self-hosting?

At MVP scale all four cost close to nothing; what differs is how the bill behaves as you grow.

Firebase can be cheaper on paper until a careless listener multiplies your reads — see Supabase vs Firebase for a SaaS MVP. Neon can undercut Supabase for a quiet product. Self-hosting rarely saves money once you price the hours.

Can I use Supabase with Clerk?

Yes — Supabase supports Clerk as a third-party auth provider, so Clerk session tokens can query your database directly and Row-Level Security policies can read Clerk claims such as the user's organisation and role. Connect the two in Clerk's Supabase setup and Supabase's Third-Party Auth settings. The older JWT-template integration was deprecated on 1 April 2025, so ignore tutorials that have you share your Supabase JWT secret with Clerk.

Users signing in through Clerk count as Third-Party MAUs: 50,000 included on Free, 100,000 on Pro, then $0.00325 each — on top of Clerk's own bill. So if you're on Clerk and choosing a database: Postgres, with Supabase the natural host when you want tenant isolation keyed on Clerk organisation IDs, as in our multi-tenant SaaS architecture guide. Still choosing auth? Read Clerk vs Better Auth.

Our default: Supabase Pro or plain managed Postgres?

Our default stack is Next.js, Postgres (often on Supabase), Clerk, Stripe and Resend on Vercel — reasoning in our SaaS MVP tech stack for 2026. Postgres is the fixed decision; the host isn't.

We choose Supabase Pro when the product uses more than the database: file storage, Realtime, RLS through Supabase's APIs, or Supabase Auth instead of Clerk. You get those services, daily backups and an always-on server for a flat, forecastable ~$25.

We choose plain managed Postgres, usually Neon, when the app only reaches its database from server-side code through an ORM. With bursty traffic and no need for Supabase's extras, scale-to-zero billing can come in cheaper.

Either way: a paid plan before launch, the spend cap off once customers depend on you, staging on the smallest compute, and PITR on when losing a day of data would cost you a customer. Setting that up is part of our DevOps and cloud infrastructure work.

Frequently asked questions

Is Supabase a SaaS?

Yes — hosted Supabase is a managed backend sold as a monthly subscription, though the software underneath is open source. Each project is a dedicated Postgres database bundled with auth, storage, Realtime and Edge Functions. You can self-host the stack with Docker, but you lose managed backups, PITR and branching, and take on the operations yourself.

Is Supabase Pro worth $25 a month for an MVP?

Yes, from the day real users depend on your app. The $25 buys no pausing, seven days of daily backups, 8 GB of disk, 100,000 MAU and email support. One paused demo or unrecoverable table costs more than the fee.

Does Supabase charge UK VAT?

It can: Supabase invoices in USD, and its billing FAQ set VAT collection, where the law requires it, to roll out between 1 May and 30 June 2026. Whether tax appears depends on your billing address. If you're VAT-registered, add your VAT number on the billing page so reverse charge can apply to eligible B2B purchases, and confirm the treatment with your accountant.

Want a Supabase setup costed before you build?

Your Supabase bill is mostly decided in week one: how many projects, which compute size, whether PITR is on, where staging lives. To make those choices deliberately, book a free scoping call. We'll map the right stack to your product, running costs included, and quote the build fixed-price.