# Supabase pricing explained: what you actually pay

> Supabase Pro costs $25 a month with one Micro project included; each extra project adds its own compute, from $10 a month, plus any usage overages.

Source: https://supahost.app/guides/supabase-pricing-explained · Updated 2026-11-11

Supabase has a Free plan for small projects and a Pro plan that starts at $25 a month. The $25 covers one project on the smallest compute size; every additional project adds its own compute charge (from $10 a month), and usage above the included quotas is billed on top, so for many apps it's the per-project compute that drives the bill.

Prices below are from [supabase.com/pricing](https://supabase.com/pricing), checked November 2026.

## The plans at a glance

| | Free | Pro |
|---|---|---|
| Base price | $0 | $25/mo |
| Projects | 2 active projects | Each project billed for its own compute |
| Compute | Smallest size, shared | $10/mo compute credit (covers one Micro project) |
| Database disk | 500 MB per project | 8 GB per project, then $0.125/GB |
| Monthly active users | 50,000 | 100,000, then $0.00325/MAU |
| Egress (uncached) | 5 GB | 250 GB, then $0.09/GB |
| Cached egress | 5 GB | 250 GB, then $0.03/GB |
| File storage | 1 GB | 100 GB, then $0.0213/GB |
| Backups | None | Daily, kept 7 days |
| Pausing | After 1 week of inactivity | Not paused for inactivity |

Above Pro there is a Team plan (from $599/mo) aimed at larger teams and companies with compliance requirements, and a custom Enterprise plan. Most indie developers and startups choose between Free and Pro.

The Free plan suits prototypes and side projects. Its practical limits are the two-project cap, the 500 MB database and pausing: an inactive project is paused after a week and must be restored before it answers again.

## How the per-project compute model works

This is the part of Supabase pricing that surprises people. On paid plans, every project runs on its own dedicated Postgres instance, and each instance is billed for compute by the hour. The Pro plan's $25 includes a $10 compute credit, which covers exactly one project on the Micro size.

| Compute size | Price per project |
|---|---|
| Micro | $10/mo |
| Small | $15/mo |
| Medium | $60/mo |
| Large | $110/mo |

Larger sizes exist; see the [compute add-ons page](https://supabase.com/docs/guides/platform/compute-add-ons) for the full list and specs. Our guide to [Supabase compute sizes](/guides/supabase-compute-sizes) explains when each one makes sense.

A few details worth knowing, from the [compute usage docs](https://supabase.com/docs/guides/platform/manage-your-usage/compute):

- Compute is billed hourly, and a partial hour counts as a full hour.
- The $10 credit resets monthly and does not carry over.
- The credit does not cover branching compute or read replica compute, which are billed separately.
- Compute is not covered by the spend cap, so turning the cap on does not limit what extra projects cost.

## Usage overages and the spend cap

The Pro quotas in the table above apply across your organization (disk is the exception, at 8 GB per project). Supabase also meters Realtime and Edge Functions:

| Metered item | Included on Pro | Overage |
|---|---|---|
| Realtime concurrent connections | 500 | $10 per 1,000 |
| Realtime messages | 5 million | $2.50 per million |
| Edge Function invocations | 2 million | $2 per million |

The spend cap is on by default on Pro. With it on, you are not charged for usage beyond the quotas; instead you get notified and a grace period starts, and staying over can lead to your project being restricted. Turn the cap off if you would rather pay the overage than risk your app being limited.

Some example overages for a single Pro project:

| Scenario | Extra cost |
|---|---|
| 150,000 MAU (50,000 over) | 50,000 × $0.00325 = $162.50 |
| 400 GB uncached egress (150 GB over) | 150 × $0.09 = $13.50 |
| 20 GB database (12 GB over) | 12 × $0.125 = $1.50 |

MAU tends to grow fastest for consumer apps; disk and file storage are cheap per GB. For egress, see [Supabase egress: what counts and how to cut it](/guides/supabase-egress).

## Add-ons

| Add-on | Price (November 2026) |
|---|---|
| Custom domain | $10/mo per project |
| Point-in-time recovery | From $100/mo per project (7 days) |
| IPv4 address | $4/mo |
| Log drains | $60/mo per drain, plus event and egress charges |

Custom domains and point-in-time recovery are per project, so they multiply the same way compute does. More on domains in [Custom domains for Supabase](/guides/supabase-custom-domain).

## Worked monthly totals

These totals assume every project runs on Micro and usage stays inside the Pro quotas. The formula is $25 + ($10 × number of projects) − $10 credit.

| Projects | Base bill | With a custom domain on every project |
|---|---|---|
| 1 | $25 | $35 |
| 5 | $65 | $115 |
| 10 | $115 | $215 |
| 20 | $215 | $415 |

A more realistic five-project setup might look like this: two production apps on Small, three smaller apps on Micro, and custom domains on the two production apps.

```
Pro plan                      $25
Compute: 2 × Small ($15)      $30
Compute: 3 × Micro ($10)      $30
Compute credit               -$10
Custom domains: 2 × $10       $20
-----------------------------------
Total                         $95/mo  (before usage overages)
```

Add point-in-time recovery to one production project and the total becomes $195. To run your own numbers, try the [Supabase pricing calculator](/supabase-pricing-calculator).

## How to keep Supabase costs down

- **Use the Free plan for side projects.** Two free projects are enough for many experiments. Accept the pausing, or move a project to Pro once it has real users.
- **Delete projects you don't use.** On Pro, an idle project still costs its compute every hour it exists.
- **Start on Micro and upgrade on evidence.** Fix slow queries and add indexes before buying a bigger size. Compute changes are quick to apply later.
- **Only add a custom domain where users see it.** A domain matters for OAuth consent screens on production, not on staging.
- **Be careful with branches.** Preview branches run on compute that the credit does not cover.
- **Cut egress at the source.** Select only needed columns, paginate, resize images and cache Storage files.
- **Watch MAU on consumer apps.** Bots and fake sign-ups count as users too.
- **Consider fewer projects.** Closely related apps can share one project using separate schemas, at the cost of a shared Auth user pool and shared limits.

## When Supabase Cloud is the right choice

For one or two production projects, Supabase Pro is good value: $25 to $35 a month for managed Postgres, Auth, Storage, Realtime and Edge Functions, with read replicas, a connection pooler, a log explorer and image transformations available as you grow. If you need SOC 2, HIPAA or an SLA, stay on Supabase Cloud.

## An option for many projects: SupaHost

If your bill is mostly per-project compute, a flat-price host can be cheaper. [SupaHost](/pricing) runs the open-source Supabase stack on a VM dedicated to your account, and one plan covers many projects. Each project still has its own database, Auth, Storage, API URL and keys, so supabase-js works unchanged.

| Projects | Supabase Pro (Micro, no add-ons) | SupaHost (November 2026) |
|---|---|---|
| 1 | $25 | $25 (Builder) |
| 5 | $65 | $25 (Builder, 5 projects included) |
| 10 | $115 | $49 (Pro, 15 included) or $40 (Builder + 5 extra at $3) |
| 20 | $215 | $64 (Pro + 5 extra at $3) or $99 (Business, 30 included) |

The trade-offs are real. All projects on an instance share one server and its resources (Builder: 2 shared vCPU and 4 GB RAM; Pro: dedicated 2 vCPU and 8 GB; Business: dedicated 4 vCPU and 16 GB). SupaHost is in public beta and has no SLA, no SOC 2, no read replicas, no connection pooler and no image transformations. It doesn't charge per MAU, Realtime connection or function invocation, and includes 1, 3 or 10 custom domains depending on the plan.

To compare against your actual usage, use the savings calculator on [/migrate/supabase-cloud](/migrate/supabase-cloud), or read the full [SupaHost vs Supabase Cloud comparison](/compare/supabase-cloud). For other routes, see [Supabase alternatives](/guides/supabase-alternatives) and [how to self-host Supabase](/guides/self-host-supabase).

## FAQ

### Is Supabase free?
Yes, the Free plan costs nothing and includes two active projects with a 500 MB database, 50,000 monthly active users and 5 GB of egress each month. Free projects pause after a week of inactivity, and there are no automatic backups.

### How much does Supabase Pro cost per month?
Pro starts at $25 a month, which includes one project on Micro compute. Each extra project adds at least $10 a month for its compute, so five Micro projects cost $65 and ten cost $115, before overages and add-ons.

### Why is my Supabase bill higher than $25?
The usual reasons are extra projects (each billed for compute), larger compute sizes, add-ons such as custom domains or point-in-time recovery, and usage over the quotas, most often MAU or egress. Your organization's usage page breaks the bill down by line item.

### Does the spend cap stop all extra charges?
No. The spend cap stops charges for usage beyond the quotas, such as egress and MAU, but compute hours are not covered. Extra projects and larger compute sizes are always billed.

### What is the cheapest way to run many Supabase projects?
On Supabase Cloud, keep non-critical projects on the Free plan and run paid projects on Micro. If you have more than a handful of production projects, a flat-price host like SupaHost or [self-hosting](/guides/self-host-supabase) usually costs less, in exchange for fewer managed features.