How Much Does Supabase Cost? Cloud Plans vs Self-Hosting in 2026

Supabase Cloud is free for small projects, $25 a month on Pro and $599 a month on Team. That's the floor, not the bill. A real bill is the plan plus compute, disk, egress, monthly active users and add-ons, and for the three example setups below it comes to about $35, $440 and $3,900 a month.

Self-hosting drops the plan fee and the per-user charges, then hands you the servers, the backups and the upgrades. On Google Cloud, the same three setups cost about $117, $230 and $2,045 a month in infrastructure. What decides it is the engineering time to run them.

We run self-hosted Supabase on Google Cloud for Hexis and set it up for clients, so we price both sides often. Supabase's numbers come from its pricing page and compute docs. Cloud prices are list prices for Google Cloud's Iowa region (us-central1) and AWS's N. Virginia region (us-east-1). Everything was checked on October 28, 2026, in US dollars, on demand and before tax.

To price your own setup, use our Supabase pricing calculator, which runs this model for both Supabase Cloud and self-hosting on Google Cloud.

Supabase Cloud plans

The plan is per organization. Compute is per project, and the $10 credit covers one Micro instance, so a staging project pays for its own compute from day one.

What makes the bill grow

Compute

Every project runs on its own instance, billed by the hour. Monthly figures assume a full month:

Micro to Medium share CPU with other projects. Large is the first size with dedicated cores.

Usage over the quota

On Pro and Team:

• Database disk: $0.125 per GB over 8 GB.
• Egress: $0.09 per GB over 250 GB. Cached egress has its own quota, at $0.03 per GB.
• File storage: $0.0213 per GB over 100 GB.
• Monthly active users: $0.00325 each over 100,000. This is the line that surprises consumer apps. At a million monthly active users it's $2,925 a month, more than an 8XL instance.
• Edge Functions: $2 per million invocations over 2 million.
• Realtime: $10 per 1,000 peak connections over 500, and $2.50 per million messages over 5 million.

Add-ons

• Point-in-time recovery: about $100, $200 or $400 a month for 7, 14 or 28 days. It needs Small compute or larger.
• Read replicas: billed at the primary's compute size plus 1.25 times its disk. The compute credit doesn't apply.
• Custom domain $10 a month, dedicated IPv4 $4 a month, log drain $60 a month plus $0.20 per million events.
• HIPAA: Team or Enterprise only, with a signed BAA. Supabase doesn't publish the price.

Pro's spend cap is on by default and stops most usage charges. It doesn't cover add-ons: point-in-time recovery, replicas, IPv4, custom domains and log drains are billed either way.

Two changes from 2026 to budget for. Supabase now adds sales tax, VAT or GST to invoices where it applies. And on September 25 it announced that logs move to usage-based pricing. That isn't enforced yet, and existing organizations have a grace period into early 2027.

Work out your own bill

For Pro, add up:

$25 for the plan
+ the main project's compute, minus the $10 credit
+ compute for every other project (staging, previews)
+ $0.125 per GB of database disk over 8 GB
+ $0.09 per GB of egress over 250 GB
+ $0.0213 per GB of file storage over 100 GB
+ $0.00325 per monthly active user over 100,000
+ add-ons

For Team, start from $599 instead of $25.

The Supabase pricing calculator does this sum for you, and prices the same setup self-hosted next to it.

Three example bills on Supabase Cloud

• Launch: one app with 10,000 monthly active users and 100 GB of egress, inside Pro's quotas, plus a staging project.
• Growing SaaS: 150,000 monthly active users, Large compute, a 50 GB database, 200 GB of files, 500 GB of egress, 7 days of point-in-time recovery, a staging project and a custom domain.
• Scale with compliance: the Team plan for its SOC 2 report and HIPAA eligibility, 300,000 monthly active users, 4XL compute with one read replica, a 500 GB database, 1 TB of files, 3 TB of egress, 14 days of point-in-time recovery, a Medium staging project, a log drain and a custom domain.

The same setups, self-hosted on Google Cloud

These run Supabase's Docker setup on Compute Engine, sized to Supabase's stated requirements: at least 4 GB of RAM and 2 cores, with 8 GB and 4 cores recommended. In the first two setups Postgres runs on the same VM, with a reverse proxy on it for HTTPS. In the third, Postgres gets two dedicated VMs, a primary and a replica, and the Supabase services run on two VMs behind a load balancer. Files and backups go to Cloud Storage at $0.02 per GiB a month, with WAL archives standing in for point-in-time recovery. Egress is billed at Google's default Premium Tier, $0.12 per GiB for the first TiB. The backup sizes and log volume are our assumptions, so the lines are rounded.

There's no charge for monthly active users when you self-host, which is most of the gap at the larger sizes.

Then there's the time. Supabase shipped 25 self-hosted releases in the 12 months to October 16, 2026, according to its changelog, and flagged four as breaking. Two of those switched the default to Postgres 17 and replaced Kong with Envoy as the API gateway. Someone also has to restore backups to prove they work, patch the hosts and answer alerts. For these examples we assume 2 to 4 hours a month for the launch setup, 4 to 8 for the growing one and 10 to 20 for the large one. At our rates of $100 to $150 an hour:

Supabase Cloud wins the first two easily. At the third, the invoice gap is about $1,850 a month, so self-hosting pays off only if running it takes less than 12 to 18 hours a month. That's achievable with good automation, and it's also where a bad month with a failed upgrade erases the savings.

On AWS

AWS prices land close to Google's:

A managed database takes the database work off your plate, but Supabase's services expect a superuser and extensions that managed services don't always allow. Our GCP post's FAQ covers what breaks on Cloud SQL. For a real number: in our multi-region setup for Hexis, each self-managed PostgreSQL node costs about $120 to $140 a month with its disk, against the $400 to $500 a month we estimated for each Cloud SQL replica.

Costs that catch people out

• Every project pays for compute. Staging, previews and per-client projects each add at least $10 a month on Supabase Cloud.
• Egress can flip the math. On Google Cloud's Premium Tier, egress costs $0.12 per GiB for the first TiB, more than Supabase's $0.09. Google's Standard Tier gives 200 GiB free, then $0.085 per GiB. An app that serves a lot of files should price this first.
• Point-in-time recovery isn't free on either side. On Supabase Cloud it's $100 to $400 a month. Self-hosted, it's WAL archiving you set up, monitor and test.
• Self-hosting drops platform features. Per Supabase's self-hosting docs: branching, managed backups and point-in-time recovery, advanced metrics, the Management API and multiple projects in one dashboard. Support is the community.

When it isn't about price

• Where the data lives. Supabase Cloud runs in 17 AWS regions, none of them in the Middle East. If your data has to stay in the Gulf, self-hosting in AWS's UAE region or Google Cloud's Doha or Dammam regions is how you get there.
• Whose account it's in. Some audits and contracts need the database inside your own cloud project, on a private network. That was one of Hexis's requirements.
• HIPAA. Supabase Cloud needs the Team plan, a BAA and the add-on. Self-hosted, Supabase says its HIPAA controls aren't supported out of the box, so the safeguards are yours to build, as we explain in Supabase HIPAA compliance.

If you do move, the setup is a one-time cost. We set up self-hosted Supabase in your own Google Cloud project as a two-week, fixed-price project from $8,000. A move with live users gets its own fixed quote once we've seen it. What it takes to run in production is in our production guide.