Free, with no sign-up. Prices checked on 2 November 2026.
Supabase pricing calculator
Estimate your Supabase Cloud bill line by line, then see what the same setup costs self-hosted on Google Cloud, including the engineering time it takes to run. Start from one of three example setups, or enter the numbers from your own usage page.
Start from an example, then change anything
- Supabase Cloud
- $437
- Self-hosted
- $980
Your estimate
- Supabase Cloud
- $437.38a monthPro plan, Large compute
- Self-hosted on Google Cloud
- $980.16a month$230.16 of infrastructure and $750 of engineering time
Supabase Cloud is cheaper by $542.78 a month ($6,513 a year), with your team's time counted.
Self-hosting is cheaper while your team spends fewer than 1.6 hours a month running it.
List prices, before tax.
See it line by lineLine by line
Monthly, in US dollars, before tax. Lines that come to nothing are left out.
Supabase Cloud
The Pro plan, billed by Supabase.
| Line | Per month |
|---|---|
| Pro plan | $25 |
| Main project compute, after the creditLarge, 2 vCPUs, 8 GB | $100 |
| Staging and other projects1 × Micro | $10 |
| Database disk over 8 GB50 GB provisioned | $5.25 |
| Egress over 250 GB500 GB | $22.50 |
| File storage over 100 GB200 GB | $2.13 |
| Monthly active users over 100,000150,000 users | $162.50 |
| Point-in-time recovery7 days | $100 |
| Custom domain | $10 |
| Total a month | $437.38 |
This assumes Pro's spend cap is off. With it on, the default, Supabase restricts the project instead of billing usage over the quota.
Self-hosted on Google Cloud
Supabase's Docker setup on one VM, with Postgres on the same machine. Iowa (us-central1), on-demand list prices.
| Line | Per month |
|---|---|
| Supabase VMOne e2-standard-4 running Postgres and the Supabase services | $97.84 |
| Disk100 GB SSD persistent disk | $17 |
| Staging and other projects1 × e2-standard-2 with a 40 GB disk | $52.92 |
| Files in Cloud Storage200 GB | $3.73 |
| Backups and WAL archives150 GB in Cloud Storage | $2.79 |
| Egress500 GB on Premium Tier | $55.88 |
| Infrastructure | $230.16 |
| Engineering time6 hours at $125 an hour | $750 |
| Total a month | $980.16 |
No plan fee and no charge per user. You run the upgrades, backups and alerts yourself.
Next steps
Talk it through
In 30 minutes we can check these numbers against your real usage and say whether a move makes sense. If staying on Supabase Cloud is cheaper, we'll tell you. Your numbers are already in the booking notes.
Email me this comparison
Both bills line by line, with a link that reopens the calculator on your numbers, to share with your team.
How we calculate this
The calculator runs the model from our post on what Supabase costs, and its three examples are the presets. Everything is a list price in US dollars, before tax, for a 730-hour month.
Prices checked on 2 November 2026
Supabase Cloud
The bill is the plan, plus compute for each project, plus usage over the plan's quotas, plus add-ons. Compute uses Supabase's monthly figures, from $10 for Micro to $3,730 for 16XL, minus the $10 credit on paid plans.
Over the quota on Pro and Team: disk is $0.125 per GB over 8 GB per project, egress $0.09 per GB over 250 GB, cached egress $0.03 per GB over 250 GB, file storage $0.0213 per GB over 100 GB, and monthly active users $0.00325 each over 100,000. Edge Function invocations and Realtime connections and messages are billed in whole packages.
Add-ons: point-in-time recovery is $100, $200 or $400 a month for 7, 14 or 28 days. A read replica costs the main project's compute plus 1.25 times its disk. A custom domain is $10, a dedicated IPv4 address $4 per database, and a log drain $60 before events.
We assume Pro's spend cap is off, so usage over the quota is billed. Not included: tax, the HIPAA add-on (Supabase doesn't publish its price), extra disk IOPS and throughput, branching, single sign-on users and image transformations. Supabase lists logs ingest at $0.50 per GB over 20 GB, but won't bill it before the start of 2027.
Self-hosted on Google Cloud
Supabase's Docker setup on Compute Engine, at on-demand prices in Iowa (us-central1). Supabase asks for at least 4 GB of RAM and 2 cores, and recommends 8 GB and 4 cores. Up to XL with no read replicas, Postgres runs on the same VM as the Supabase services, with a reverse proxy for HTTPS. From 2XL, or with any read replica, Postgres gets n2 VMs of its own, one per server, and the services run on two e2-standard-4 VMs behind a load balancer at $18.25 a month plus $0.008 per GiB processed.
Micro and Small keep Postgres on balanced persistent disk at $0.10 per GB, at least 40 GB. Medium and up use SSD persistent disk at $0.17 per GB, at least 100 GB per server. Either way, the disk matches your database disk if that's bigger. Files and backups go to Cloud Storage at $0.02 per GiB a month, and we assume backups and WAL archives, which stand in for point-in-time recovery, take three times the database disk.
Egress is on Google's default Premium Tier: $0.12 per GiB for the first TiB, $0.11 up to 10 TiB and $0.08 after that, to North America. Standard Tier is cheaper for heavy egress: 200 GiB free, then $0.085 per GiB. With a log drain, we assume 100 GiB of logs a month in Cloud Logging, at $0.50 per GiB after the free 50 GiB.
Engineering time is your hours times your rate. For a small single VM we budget 2 to 4 hours a month, for a bigger one 4 to 8, and for a setup with its own database servers 10 to 20: upgrades, restore tests, patches and alerts.
Not included: the sustained-use discount Google gives n2 VMs that run all month (up to 20%), committed-use discounts, public IPv4 addresses at $3.65 a month per VM, Cloud NAT, boot disks for the service VMs, the free tiers and tax. We price Postgres on VMs. Cloud SQL costs more, but takes upgrades and backups off your plate, and our setup uses it where your extensions allow.
How we size the VMs
Each Supabase compute size, and the Google Cloud machine we price it as. A single VM also runs the Supabase services, so it has more memory than the database alone.
| Supabase compute | Google Cloud machine, a month |
|---|---|
| Micro, $10shared CPU, 1 GB | e2-standard-2, $48.92With the Supabase services. With read replicas, n2-standard-2 at $70.90 per database server. |
| Small, $15shared CPU, 2 GB | e2-standard-2, $48.92With the Supabase services. With read replicas, n2-standard-2 at $70.90 per database server. |
| Medium, $60shared CPU, 4 GB | e2-standard-4, $97.84With the Supabase services. With read replicas, n2-standard-2 at $70.90 per database server. |
| Large, $1102 vCPUs, 8 GB | e2-standard-4, $97.84With the Supabase services. With read replicas, n2-standard-2 at $70.90 per database server. |
| XL, $2104 vCPUs, 16 GB | e2-standard-8, $195.67With the Supabase services. With read replicas, n2-standard-4 at $141.79 per database server. |
| 2XL, $4108 vCPUs, 32 GB | n2-standard-8, $283.58Postgres only, per database server. |
| 4XL, $96016 vCPUs, 64 GB | n2-standard-16, $567.17Postgres only, per database server. |
| 8XL, $1,87032 vCPUs, 128 GB | n2-standard-32, $1,134.34Postgres only, per database server. |
| 12XL, $2,80048 vCPUs, 192 GB | n2-standard-48, $1,701.51Postgres only, per database server. |
| 16XL, $3,73064 vCPUs, 256 GB | n2-standard-64, $2,268.68Postgres only, per database server. |
To try the self-hosted side yourself, our open-source Pulumi template sets up Supabase Studio on Google Cloud.
Sources
Supabase
Prices checked on 2 November 2026. Google's prices are for Iowa (us-central1).
Questions people ask
How much does Supabase cost a month?
The Free plan is $0. Pro starts at $25 a month and Team at $599, per organization, and on top come compute for each project and any usage over the quotas. Our three examples come to $35, $437.38 and $3,895.30 a month: an app at launch with a staging project, a SaaS app with 150,000 monthly active users, and a 4XL setup on Team with a read replica.
How is Supabase compute billed?
By the hour, for each project, from $10 a month for Micro to $3,730 for 16XL. Paid plans include $10 of compute credit a month, enough for one Micro instance, so a staging project pays for its own compute from day one. Read replicas run at the main project's size, and the credit doesn't cover them.
What happens if I go over the Pro plan's quotas?
Pro's spend cap is on by default. With it on, Supabase restricts the project instead of billing for usage over the quota. With it off, the usage is billed: $0.09 per GB of egress over 250 GB, $0.125 per GB of disk over 8 GB, $0.0213 per GB of file storage over 100 GB and $0.00325 per monthly active user over 100,000. Compute, point-in-time recovery, read replicas and the other add-ons are billed either way.
Is self-hosting Supabase cheaper than Supabase Cloud?
Only at scale, and only if running it doesn't take much time. In our largest example, self-hosting on Google Cloud cuts the monthly invoice by about $1,850, which pays off if your team spends fewer than 12 to 18 hours a month running it, at $100 to $150 an hour. For the two smaller examples, Supabase Cloud is cheaper once you count the time.
What does self-hosted Supabase cost on Google Cloud?
The software is free and the servers aren't. A small setup is about $117 a month in Iowa (us-central1): an e2-standard-2 VM with a 40 GB disk, and a second one for staging. The growing example comes to about $230, and the 4XL setup, with its own database servers and a load balancer, about $2,045, all before engineering time. There's no charge for monthly active users.
How accurate is this calculator?
It uses list prices in US dollars, before tax, checked on 2 November 2026. Supabase compute uses Supabase's monthly figures, though it's billed by the hour. The self-hosted side rests on our assumptions: the VM sizes, the disks, backups at three times the database, and the hours to run it. It leaves out Google's sustained-use and committed-use discounts and small items such as public IP addresses. Use it to plan, then check a real invoice before you decide.
Paying a lot for Supabase Cloud?
We set up self-hosted Supabase in your own Google Cloud project in two weeks, at a fixed price from $8,000, with every resource defined in Pulumi and a restore tested before handover. A move with live users gets its own fixed quote once we've seen it. If staying on Supabase Cloud is cheaper, we'll tell you.
More on running Supabase yourself: self-hosted Supabase in production, how we moved Hexis to Google Cloud and Supabase and HIPAA. Built your app with Lovable? Check it against our Lovable and Supabase security checklist. Before a big move, a code audit shows what you'd be moving.