# Plans and limits

> SupaHost's Builder, Pro, Business and Enterprise plans side by side: server size, included projects, shared quotas, backups, branching, SSH and measured capacity.

Source: https://supahost.app/docs/platform/plans · Updated 2026-11-11

Every plan is a flat monthly price for one [instance](/docs/platform/instances). The price covers the VM, a number of projects, and a pool of database, file storage and egress that all projects on the instance share. There are no fees per monthly active user, per Realtime connection or message, or per Edge Function invocation.

## The plans

Prices are in USD per month. The price per month when billed annually is in brackets.

| | Builder | Pro | Business | Enterprise |
|---|---|---|---|---|
| Price | $25 ($20 annual) | $49 ($39 annual) | $99 ($79 annual) | Custom |
| Projects included | 5 | 15 | 30 | Custom |
| Server | Small VM, 2 shared vCPU, 4 GB RAM | Dedicated VM, 2 vCPU, 8 GB RAM | Dedicated VM, 4 vCPU, 16 GB RAM | Custom |
| Database (shared) | 8 GB | 25 GB | 50 GB | Custom |
| File storage (shared) | 100 GB | 250 GB | 500 GB | Custom |
| Egress per month (shared) | 250 GB | 500 GB | 1 TB | Custom |
| Custom domains | 1 | 3 | 10 | Custom |
| Daily database backups kept | 7 days | 7 days | 14 days | Custom |
| Point-in-time recovery | No | 7 days | 14 days | Custom |
| Branching | No | Yes | Yes | Yes |
| Restricted SSH and direct Postgres (SSH tunnel) | No | No | Yes | Yes |

"Shared" means the quota is a total for the instance, not per project. Ten small projects and one large one draw from the same 25 GB of database on Pro.

## Extras

| Extra | Price |
|---|---|
| Project beyond the plan's allowance | $3/month each |
| Custom domain beyond the plan's allowance | $2/month each |
| Database add-on | $1.25 per 10 GB per month |
| File storage add-on | $1.05 per 50 GB per month |
| Egress add-on | $12 per 100 GB per month |

Usage above your plan plus add-ons is billed as overage: database $0.125/GB, file storage $0.021/GB, egress $0.12/GB. How usage is measured, and how add-ons and alerts work, is on [Usage, quotas and add-ons](/docs/platform/usage).

A worked example: a Builder instance with 7 projects and 2 custom domains costs $25 + 2 × $3 + 1 × $2 = $33 a month before any add-ons or overage.

## What every plan includes

All plans run the same Supabase stack with the same features: Auth with email, magic links, 19 OAuth providers, anonymous sign-ins and TOTP MFA; the Data API; Storage; Realtime; Edge Functions; pg_cron and pgmq; Studio for every project; custom domains with automatic HTTPS; daily backups; one-click exports; import from Supabase Cloud; and the MCP server for AI coding tools. The full feature list is on [Supabase features on SupaHost](/docs/getting-started/feature-support).

The plans differ in server size, quotas, backup retention, and three features:

- **Point-in-time recovery** (Pro and up). See [Point-in-time recovery](/docs/platform/point-in-time-recovery).
- **Branching** (Pro and up). See [Branching](/docs/platform/branching).
- **Restricted SSH and direct Postgres** through an SSH tunnel (Business and up). See [SSH access and direct Postgres](/docs/platform/ssh).

## How much each plan handles

There's no hard cap on users. These guides come from load tests run in November 2026, assuming a typical app where 5% of monthly users are active in the busiest hour and each active user makes one request every 10 seconds.

| | Builder | Pro | Business |
|---|---|---|---|
| Monthly active users (guide) | about 25,000 | about 50,000 | about 100,000 |
| Concurrent Realtime connections (guide) | about 5,000 | about 15,000 | about 30,000 |
| Measured API reads | about 300/s | about 540/s | about 950/s |
| Measured password sign-ins | about 19/s | about 18/s | about 38/s |

Password sign-ins are limited by CPU, because hashing passwords is deliberately slow. In a separate test a Business instance held 15,000 concurrent Realtime connections.

Your numbers will differ. Heavy queries, missing indexes and large responses lower them; caching and well-indexed tables raise them. Treat the table as a starting point and watch your own usage.

## Choosing a plan

- **Builder** suits side projects, prototypes and a handful of small production apps. The CPU is shared, so performance can vary more than on the dedicated plans.
- **Pro** is the usual choice for production: dedicated CPU, point-in-time recovery and branching.
- **Business** adds more CPU and memory, 14 days of backups and PITR, and SSH access with a direct Postgres tunnel for tools like `psql`, `pg_dump` and ORMs.
- **Enterprise** is for larger or custom setups. Email supahost@volods.com.

You can change plan later; it resizes the VM with about a minute or two of downtime. See [Changing plans](/docs/platform/changing-plans).

## What no plan includes

SupaHost is in public beta. No plan includes read replicas, a connection pooler, multi-server failover, an SLA, or SOC 2, ISO 27001 or HIPAA compliance. If you need any of those today, SupaHost isn't the right fit yet.

## Related

- [Free trial and billing](/docs/platform/trial-and-billing)
- [Limits reference](/docs/platform/limits)
- [Can SupaHost scale as my app grows?](/kb/scaling)