Supabase's pricing page looks simple: Free, Pro at $25 and Team at $599. The bill is less simple, because the plan is charged once per organisation while every project runs its own server, billed by the hour, and usage past the quotas is billed on top.
The short answer: Supabase has four plans. Free is $0, with 500 MB of database per project, 5 GB of egress, 1 GB of file storage and 50,000 monthly active users, two active projects, and pausing after a week of low activity. Pro starts at $25 a month and includes $10 of compute credit, enough for one project on the Micro size, so a single Micro project costs $25 and each extra project adds its compute (from $10). Past the quotas, Pro charges $0.125 per GB of disk over 8 GB, $0.09 per GB of egress over 250 GB, $0.00325 per user over 100,000 MAUs, $0.0213 per GB of storage over 100 GB and $2 per million Edge Function calls over 2 million. Team starts at $599 a month and adds SOC 2, SSO for the dashboard and longer backups; Enterprise is a custom price. A spend cap is on by default on Pro, but it doesn't cover compute or add-ons. Prices checked 12 November 2026.
Fastero
Connect your database. Ask questions. Get dashboards.
Postgres, BigQuery, Snowflake, and 10+ sources — live-connected, AI-powered, no dashboard builder learning curve.
Try free →Supabase plans at a glance (checked 12 November 2026)
| Free | Pro | Team | Enterprise | |
|---|---|---|---|---|
| Price | $0 | From $25 a month | From $599 a month | Custom |
| Compute | Shared CPU, 500 MB RAM | $10 credit a month (one Micro) | $10 credit a month (one Micro) | Custom |
| Database | 500 MB per project | 8 GB disk per project, then $0.125 per GB | Same as Pro | Custom |
| Egress | 5 GB, plus 5 GB cached | 250 GB, plus 250 GB cached | Same as Pro | Custom |
| Monthly active users | 50,000 | 100,000 | 100,000 | Custom |
| File storage | 1 GB | 100 GB | 100 GB | Custom |
| Edge Function calls | 500,000 | 2 million | 2 million | Custom |
| Backups | None | Daily, kept 7 days | Daily, kept 14 days | Custom |
| Log retention | 1 day | 7 days | 28 days | 90 days |
| Pausing | After 1 week of inactivity | Never | Never | Never |
| Support | Community | Priority email and SLAs | Dedicated |
Every plan has "unlimited API requests" and unlimited team members. Team adds SOC 2 and ISO 27001, project-scoped and read-only roles, SSO for the Supabase dashboard, platform audit logs, AWS PrivateLink and HIPAA as a paid add-on. Enterprise adds uptime SLAs, designated support and 24×7 cover.
How a Supabase bill is built
Supabase bills per organisation. You pick one plan for the organisation, and "each project within it runs on its own compute instance". The plan includes $10 of compute credit a month, which resets monthly and doesn't accumulate. Supabase's own example: "a Pro org with 2 projects on Micro compute costs: $25 (plan) + $10 (project 1) + $10 (project 2) - $10 (credits) = $35/month."
The quotas, on the other hand, are shared: they apply "to your entire organization, independent of how many projects you launch within that organization". Pro is charged up front each month; usage beyond the quotas is billed at the end of it.
Compute sizes and prices
| Size | Per month | Per hour | CPU | RAM | Direct / pooler connections |
|---|---|---|---|---|---|
| Nano (Free) | $0 | $0 | Shared | Up to 0.5 GB | 60 / 200 |
| Micro | $10 | $0.01344 | Shared | 1 GB | 60 / 200 |
| Small | $15 | $0.0206 | Shared | 2 GB | 90 / 400 |
| Medium | $60 | $0.0822 | Shared | 4 GB | 120 / 600 |
| Large | $110 | $0.1517 | 2 dedicated vCPUs | 8 GB | 160 / 800 |
| XL | $210 | $0.2877 | 4 dedicated vCPUs | 16 GB | 240 / 1,000 |
| 2XL | $410 | $0.562 | 8 dedicated vCPUs | 32 GB | 380 / 1,500 |
| 4XL | $960 | $1.32 | 16 dedicated vCPUs | 64 GB | 480 / 3,000 |
| 8XL to 16XL | $1,870 to $3,730 | $2.562 to $5.12 | 32 to 64 dedicated vCPUs | 128 to 256 GB | 490 to 500 / 6,000 to 12,000 |
The usage docs give Large as "~$111" by its hourly rate; the pricing page rounds to $110. Compute is billed by the hour, and "If a project runs for part of an hour, you are still charged for the full hour." Paused projects don't count. A Nano project brought over from Free is billed like Micro once the organisation is on a paid plan, and you can't create new Nano projects there.
What usage costs beyond the quota
| Usage | Free | Pro and Team include | Then | Under the spend cap? |
|---|---|---|---|---|
| Disk size | 500 MB database | 8 GB per project | $0.125 per GB a month | Yes |
| Egress | 5 GB | 250 GB | $0.09 per GB | Yes |
| Cached egress | 5 GB | 250 GB | $0.03 per GB | Yes |
| Monthly active users | 50,000 | 100,000 | $0.00325 each | Yes |
| File storage | 1 GB | 100 GB | $0.0213 per GB | Yes |
| Edge Function calls | 500,000 | 2 million | $2 per million | Yes |
| Realtime messages | 2 million | 5 million | $2.50 per million | Yes |
| Realtime peak connections | 200 | 500 | $10 per 1,000 | Yes |
| Log ingestion | 1 GB | 20 GB | $0.50 per GB | Yes |
How each one is counted:
- Disk is billed on the provisioned size, not the data in it. On Pro it grows by itself when the database reaches 90% of the disk, by 50% (8 GB becomes 12 GB), at most four times in 24 hours. High-performance (io2) disks cost $0.195 per GB from the first byte.
- Egress is everything sent out to clients: database queries, Auth, Storage downloads, Edge Functions and Realtime. Queries through the Supavisor pooler show as "Shared Pooler Egress".
- MAUs are distinct users who sign in or refresh their token in the billing cycle; each counts once.
- Storage is measured in GB-hours, so the quota is effectively the average size over the month.
- Edge Functions are billed in packages of a million calls; 1,000,001 calls over the quota is two packages.
Add-ons
| Add-on | Price |
|---|---|
| Point-in-time recovery | $100 a month per 7 days of retention |
| Custom domain | $10 a month per project |
| Dedicated IPv4 address | $4 a month |
| Database branching | $0.01344 per branch per hour, about $10 a month for a branch left running |
| Log drains | $60 per drain a month, plus $0.20 per million events and $0.09 per GB |
| Phone multi-factor auth | $75 a month for the first project, $10 for each more |
| Image transformations | 100 origin images included, then $5 per 1,000 |
| Read replicas | Their own compute, disk (from the first byte) and IPv4 |
Apart from image transformations, none of these are covered by the spend cap.
The spend cap: what it stops and what it doesn't
"Spend caps are on by default on the Pro Plan." With the cap on, once you pass a quota "further usage of that item is disallowed until the next billing cycle", and Supabase may restrict the organisation under its Fair Use Policy if you keep exceeding it. With the cap off, usage is billed at the prices above.
The cap covers the usage items in the table: disk size, egress, MAUs, storage, Edge Functions, Realtime and logs. It doesn't cover compute, branches, read replicas, custom domains, IPv4, extra IOPS or throughput, log drains, phone MFA or point-in-time recovery, because those are "predictable and explicitly opted into by the user". It also isn't a budget: there are no per-item limits or alerts. Supabase's docs say the cap is "available only with the Pro Plan", and organisations billed through AWS Marketplace can't use it.
Connect any database. Ask in plain English.
Start free →Free plan limits and pausing
Free gives you two active projects, as many paused ones as you like, and no automatic backups. Three limits catch people out:
- Pausing. Supabase pauses Free projects that show low activity over 7 days. "Typically a few user requests to the database each day over the previous week is enough to keep the project from being paused." You get "A warning email roughly one week before the pause takes effect", and you can restore a paused project "for up to 1 year after it was paused". Paid projects are never paused.
- Disk. "Free Plan projects have a fixed disk size of 2 GB", and at 95% full the database goes read-only. If the disk fills, Postgres shuts down "until you upgrade to the Pro Plan".
- The 500 MB quota. Exceeding it doesn't make the database read-only. Instead the organisation can be restricted, with API requests returning a 402 error, and it's judged on "the average daily database size over the billing period", summed across your projects.
Worked examples: a small app's monthly bill
Calculated from the prices above, before tax:
| Scenario | Line items | Monthly bill |
|---|---|---|
| A side project on Free, inside every quota | Free plan | $0, and it pauses after a quiet week |
| A launched app: one Pro project on Micro, inside the quotas | $25 plan + $10 Micro − $10 credit | $25 |
| The same app growing: Small compute, a 20 GB disk, 300 GB of egress, 120,000 MAUs, spend cap off | $25 + $15 Small − $10 credit + $1.50 disk (12 GB) + $4.50 egress (50 GB) + $65 MAUs (20,000) | $101 |
| Production plus staging: two Micro projects, 7 days of point-in-time recovery and a custom domain on production | $35 for the two projects + $100 PITR + $10 domain | $145 |
| A preview branch for a pull request, open 30 hours on Micro | 30 × $0.01344 | $0.40, plus any egress |
Two lessons from the table. Users are the expensive part of a growing app: in the third example, 20,000 extra sign-ins cost more than the server, the disk and the egress together. And backups are what push a small production setup past $100: Pro's daily backups are included, but restoring to any second costs $100 a month per week of history.
Neon, the other popular hosted Postgres, prices the other way: compute by the CU-hour it actually runs ($0.106 on its Launch plan), and "Suspended (scaled-to-zero) compute = $0." Our Neon vs Supabase comparison and free Postgres hosting guide compare the two.
When a Supabase database feeds a team's dashboards
A Supabase project is ordinary Postgres underneath, and the data in it usually ends up in someone's reports. Fastero is an AI and data platform where people and AI agents work together on a team's data, and it connects Supabase as Postgres:
- Guided setup. Choose Supabase in the connection list, paste the Session pooler string from your project's Connect dialog, and type the password Supabase never displays. Fastero connects over SSL.
- Only your tables. The table list leaves out the schemas Supabase keeps in every project, except
auth.users, where your sign-ups are. - A read-only role. Connect with a role that can only
SELECT, and every dashboard, query and notebook SQL cell runs with it. - Dashboards colleagues open with their own login. They refresh on a timer (1, 5, 15 or 60 minutes) or, on Postgres, when the data changes. Each refresh is a query, and its results count toward your Supabase egress, so pick the interval to match. Viewers are free.
- Claude can query it too, read-only, through Fastero's connector in Claude's directory.

The Postgres connection form after pasting a connection string, with invented values.
More on the Supabase MCP server and Postgres connection strings.
FAQ
How much does Supabase cost per month?
Free is $0. Pro starts at $25 a month for the organisation, and with one project on Micro compute that's the whole bill until you pass a quota. Team starts at $599 a month, and Enterprise is a custom price. Checked 12 November 2026.
Is Supabase Pro $25 per project?
No, $25 per organisation, with $10 of compute credit. The first Micro project is covered; each further project adds its compute, from $10 a month on Micro.
What happens when I go over the Free plan limits?
Supabase notifies you, and if you keep exceeding them it restricts the organisation, which can mean API requests return a 402 error. Separately, a Free database goes read-only when its 2 GB disk is 95% full.
Does the Supabase spend cap stop all charges?
No. It stops overage on disk, egress, MAUs, storage, Edge Functions, Realtime and logs. Compute, branches, read replicas, custom domains, IPv4, point-in-time recovery and other add-ons are charged whether it's on or off.
Why was my Supabase project paused?
Free projects are paused after 7 days of low database activity. Supabase emails a warning about a week before. You can restore a paused project within a year, or move to Pro, where projects are never paused.
How much does Supabase branching cost?
$0.01344 an hour per branch on Micro compute, about $10 a month for a branch left running, plus any disk and egress it uses. Branching needs Pro or above.
Sources
Checked 12 November 2026:
- Supabase: Pricing, Billing on Supabase, Control your costs, Billing FAQ, Compute and disk, Database size, Project pausing
- Supabase usage docs: Compute, Disk size, Egress, Monthly active users, Storage size, Edge Function invocations, Branching, Point-in-time recovery, IPv4, Custom domains, Read replicas
Fastero Dev Team