Supabase pricing explained: Free, Pro at US$25, and compute add-ons

Supabase Pro starts at US$25 a month with US$10 in compute credits, enough for one Micro project. Free vs Pro quotas, compute add-ons, overage and pausing.

Short answer: Supabase Pro starts at US$25 a month, and one small project within the included usage costs exactly that. That US$25 is the subscription for the whole organization, and it includes US$10 a month in compute credits, which covers your first Micro project. You pay more only when you add a second project, move to a bigger compute size, go past the included usage, or buy add-ons such as a custom domain.

Prices are from the official Supabase pricing page and billing docs as of November 3, 2026, in US dollars before tax.

Free vs Pro vs Team

	Free	Pro	Team
Monthly fee	US$0	From US$25	From US$599
Compute credits	None	US$10/month	US$10/month
Database	500 MB per project	8 GB disk per project, then US$0.125/GB	Same as Pro
File storage	1 GB	100 GB, then US$0.0213/GB	Same as Pro
Egress (uncached)	5 GB	250 GB, then US$0.09/GB	Same as Pro
Cached egress	5 GB	250 GB, then US$0.03/GB	Same as Pro
Monthly active users (MAU)	50,000	100,000, then US$0.00325/MAU	Same as Pro
Automatic backups	None	Daily, kept 7 days	Daily, kept 14 days
Pausing	After 1 week of inactivity	Never	Never
Log retention	1 day	7 days	28 days
Max file upload	50 MB	500 GB	500 GB
Projects	Up to 2 active	First one included, then from US$10 each	Same as Pro

Team also gets SOC2, ISO 27001, SSO for the Supabase dashboard and finer access roles. Enterprise has no public price; you talk to sales.

What the US$25 Pro plan includes

Supabase bills per organization. An organization has one plan, so you can't keep a Free project and a Pro project in the same one. Once you upgrade to Pro, no project in that organization gets paused, and every project gets daily backups.

The quotas are shared by the whole organization. The 250 GB of egress, 100 GB of file storage and 100,000 MAU are summed across all your projects, not given to each one. Database disk is the exception: every project gets its own 8 GB.

Compute is the part people miss. Each project runs its own Postgres server, and you pay for that server by size and hours running, whatever is stored in it. Pro gives you US$10 a month in compute credits, enough for one Micro instance (shared CPU, 1 GB RAM). The credits reset every month, don't roll over, and can't be spent on anything other than compute.

So "Pro is US$25" really means one Micro project, usage within the quotas, US$25 a month.

Billing happens in two parts. The Pro fee is charged up front each billing cycle; overage and compute are billed in arrears when the cycle ends. Supabase also says it adds sales tax, VAT or GST where the law requires it, based on your billing address, so the card charge can be a bit more than US$25.

How compute add-ons are billed

Size	Per month (approx.)	Per hour	CPU / RAM
Micro	US$10	US$0.01344	Shared / 1 GB
Small	US$15	US$0.0206	Shared / 2 GB
Medium	US$60	US$0.0822	Shared / 4 GB
16XL	US$3,730	US$5.12	Dedicated 64 vCPU / 256 GB

From Large up the CPU is dedicated, all the way to 16XL. Compute is billed by the hour, a partial hour counts as a full one, and the total is charged when the billing cycle ends. Scale up for 10 hours and back down, and you pay the bigger size for those 10 hours only.

Supabase's own billing examples:

One Small project for the full month: US$25 + US$15 − US$10 = US$30
Three Small projects for the full month: US$25 + US$45 − US$10 = US$60

By the same math, two Micro projects come to US$25 + US$20 − US$10 = US$35.

Pro has the Spend Cap on by default. When egress, file storage or MAU go past the quota, usage is restricted rather than billed. Compute isn't covered by the Spend Cap, and neither are add-ons you opt into: custom domains (US$10 a month), point-in-time recovery (from US$100 a month) and IPv4. With the Spend Cap on, your bill can still go over US$25.

Egress and storage overage

Egress is data sent from Supabase to your clients. Database queries, sign-ins, file downloads, Edge Functions and Realtime messages all count toward one shared quota. Egress served from the CDN cache is cached egress, with its own quota and price.

An example: if a month has 300 GB of uncached egress, that's 50 GB over the Pro quota, or 50 × US$0.09 = US$4.5.

File storage is measured in GB-hours, which works out to your average size over the billing cycle. Deleting files late in the cycle only lowers the average slowly, so a usage restriction you've already hit may not lift until the next cycle. Database disk is billed on the provisioned size, at US$0.125 per GB per month above the included 8 GB.

When the Free plan pauses your project

A project is paused after 1 week of inactivity.
You get at most 2 active projects. The limit counts every organization where you are Owner or Admin; paused projects don't count and aren't charged.
There are no automatic backups.
If you go over the Free quotas you get a notice, and staying over leads to restricted service.

On a paid plan, an overdue invoice gets your projects paused and the organization moved back to Free.

I covered pausing, the project limit and backups in Day 3: if you already have other projects, check that you still have a free slot and enough quota.

When to move from Free to Pro

Going by the official limits, consider upgrading if any of these apply:

The project can't be paused after a week of inactivity, for example a site that has to stay up.
You need automatic backups. Free has none; Pro keeps daily backups for 7 days.
The database is close to 500 MB, files are over 1 GB, or monthly egress is over 5 GB.
You need to upload single files larger than 50 MB.
You need more than 2 projects running at once.

You can bring a paused project back yourself. In Day 3 I wrote that the free plan makes it easy to start: while on the free tier, check whether the limits cover what you need, and when it's time to pay, look at actual usage, backup needs and maintenance cost.

Estimating your monthly bill

Monthly cost ≈ subscription + compute for every project − US$10 credits + overage + add-ons

Count your projects: what compute size each one runs on, and whether it runs all month.
Check usage: the organization's Usage page shows how close egress, file storage and MAU are to the quotas.
List add-ons: custom domains, PITR and IPv4 are fixed monthly fees the Spend Cap doesn't cover.

One Micro project within the quotas comes to US$25. Each extra project adds at least US$10 for Micro.

How I count it for my own site

In Day 4 I added up what my whole site costs for a year. I'm on Supabase Pro, so US$25 × 12 months = US$300. That post counted the base plan only, with no extra projects, bigger instances or overages. Add a domain at about US$10 a year, and Supabase plus the domain is about US$310 a year.

Before that, Day 3 compared Supabase with self-hosting. At September 2026 prices, Supabase Pro at US$25 and an AWS Lightsail server at US$12 differ by US$13 a month on paper, but self-hosting means handling database updates, backups, user auth and the backend API yourself, plus your own time. I stayed with Supabase mostly because my earlier projects already use it and that experience carries over.

Day 3 used September 2026 prices, and Day 4 used prices checked on October 6, 2026. Against the official pages on November 3, 2026, nothing has changed: Pro still starts at US$25, and Free still has a 500 MB database and 1 GB of file storage per project, pauses after 1 week of inactivity, and allows at most 2 active projects.

FAQ

Is Supabase Pro US$25 per project? No. US$25 is one subscription per organization, and the compute credits pay for the first Micro project. From the second project on you pay its compute, about US$10 a month for Micro.

What is the US$10 that comes with Pro? Monthly compute credits. They only pay for compute, reset every month, don't roll over, and can't cover egress or storage.

With the Spend Cap on, can my bill go over US$25? Yes. The Spend Cap only covers usage items with a quota, such as egress, storage and MAU. Compute, custom domains, PITR and IPv4 are outside it.

Am I charged for a paused Free project? No. Paused projects use no compute and don't count toward the free project limit.

Can one account have both Free and Pro projects? Not in the same organization. Use two organizations, one on Free and one on Pro.