What Supabase really costs: Free, Pro, overages and three example bills

The plans, in short

According to the supabase.com pricing page in November 2026: Free from $0 a month, Pro from $25, Team from $599 and Enterprise at a custom price. The “from” matters: on top of those fees comes any usage beyond what's included and, on Pro and Team, each extra project.

Prices are in dollars and can change: check their page before you decide. What follows is what it says today.

What the Free plan includes and where it falls short

2 active projects, a 500 MB database with shared CPU and 500 MB of RAM, 5 GB of egress plus another 5 GB cached, 1 GB of Storage files, 50,000 monthly active users and 500,000 Edge Function calls. It has no automatic backups and logs last 1 day.

What usually hurts first isn't on that list: free projects are paused after a week of inactivity. Here's what to do if yours has been paused.

If you go over a quota you aren't charged: you get a notice and, if you keep going over, restrictions apply, which according to its documentation can mean making the project read-only, pausing it or answering every request with a 402 error.

What Pro includes and what costs extra

Per project, 8 GB of disk; after that, $0.125 per GB. For the whole organization, 250 GB of egress (after that, $0.09 per GB) and another 250 GB cached (after that, $0.03 per GB), 100 GB of Storage (after that, $0.0213 per GB), 100,000 active users (after that, $0.00325 per user) and 2 million function calls (after that, $2 per million).

It has daily backups for 7 days and 7-day logs, and no project is paused for inactivity.

The most confusing part is compute: the size of each project's machine. Pro includes $10 a month in credit, which covers one Micro (1 GB of RAM, $10). Small (2 GB) costs $15 and Medium (4 GB), $60. And each extra project pays its full compute: the credit only stretches to one.

Two add-ons people often want: going back to an exact minute (PITR) is $100 a month per 7 days, and a custom domain, $10 a month per project.

Egress, the one that surprises people

Egress is what leaves Supabase towards whoever uses your app: database rows, Auth responses, Storage files, Realtime, functions. It all comes out of the same quota. Cached egress is Storage served by its CDN, and it's cheaper.

It adds up over the billing cycle and resets when the next one starts. An app with images, or with queries that return whole tables, gets through it sooner than you'd expect: asking only for the columns you use is the first thing that helps.

The spend cap: what it stops and what it doesn't

On Pro, the Spend Cap is on by default. With it you aren't charged extra when you reach the quota for disk, egress, Storage, users, functions or Realtime: that usage is cut off until the next cycle. In other words, you swap a surprise bill for part of your app that stops working, usually just when it has the most people on it.

If you turn it off, everything keeps working and you pay the overage. And there are things the cap doesn't cover: compute, replicas, custom domains and PITR. Creating one more project adds its compute even with the cap on.

Three example bills

One small project within what's included: Pro with a Micro, no overages. $25 a month, because the credit pays for the Micro.

Two small projects (production and staging, say): $25 for Pro plus two Micros ($20) minus the credit ($10). In total, $35 a month.

An app with traffic: one project on Small with 30 GB of disk and 500 GB of egress, with the spend cap off. $25 for Pro, $5 of compute after the credit, 22 GB of extra disk ($2.75) and 250 GB of extra egress ($22.5). In total, $55.25 a month.

None of the three includes tax.

When something else makes sense

If your project fits within what's included, or you want branching, replicas or several regions, stay on Pro: it's the simplest option and you get the whole product. If it's a personal project and you don't mind restoring it, Free is fine.

What changes the sums is egress and having several projects. There are two ways out with open source Supabase. One is running it on your own server with Docker: you pay server prices, and backups, updates and keeping it up are your job.

The other is a machine on NapNodes: from €15 a month (3 GB of RAM for the whole machine, of which ~1 GB is left for Postgres) to €36 (8 GB). Egress isn't metered, with a speed limit of 200 to 400 Mbit/s depending on the plan, and backups, 7-day PITR and a custom domain are included. There's no free plan, no branching, no replicas and no choice of region, and threads and speed are shared if several projects are flat out: if you need those, Pro is better. If it suits you, here's how to move a project without touching the original.

Frequently asked questions