Supabase Pricing Explained (and What It Really Costs)
Supabase pricing starts with a Free plan ($0, two active projects, 500 MB of database each) and a Pro plan from $25 a month, which includes $10 of compute credits for one Micro instance. What you really pay on top depends on four things: how many projects you run (each one needs its own compute), monthly active users above 100,000, egress above 250 GB, and add-ons like point-in-time recovery at $100 a month.
All Supabase figures below are as of November 2026, taken from supabase.com/pricing and the Supabase docs. We build StitchDB, a hosted backend that speaks the same APIs, so we compare it at the end. The first part of this guide is useful whichever platform you pick.
#The plans at a glance
| Free | Pro | Team | Enterprise | |
|---|---|---|---|---|
| Base price | $0 | from $25/mo | from $599/mo | Custom |
| Compute credits | n/a (shared CPU, 500 MB RAM) | $10/mo (covers one Micro) | $10/mo | Custom |
| Database disk | 500 MB per project | 8 GB per project | 8 GB per project | Custom |
| Egress | 5 GB (+5 GB cached) | 250 GB (+250 GB cached) | Same as Pro | Custom |
| File storage | 1 GB | 100 GB | Same as Pro | Custom |
| Monthly active users | 50,000 | 100,000 | Same as Pro | Custom |
| Edge Function invocations | 500,000 | 2 million | 2 million | Custom |
| Daily backups | None | 7 days | 14 days | Up to 30 days |
| Log retention | 1 day | 7 days | 28 days | 90 days |
Team includes the same usage quotas as Pro. You pay the extra for compliance (SOC 2, ISO 27001), dashboard SSO, longer backups and logs, priority support with SLAs, and access controls. For a solo developer or small team, the real choice is Free or Pro.
#Supabase free tier limits
The Free plan is generous for prototypes. These are the limits that matter in practice:
- Two active projects. Not two per app: two per organization.
- 500 MB of database per project on shared CPU with 500 MB of RAM.
- 5 GB of egress plus 5 GB of cached egress per month. Image-heavy apps can use this up quickly.
- 1 GB of file storage and a 50 MB maximum upload size.
- 50,000 monthly active users, 500,000 Edge Function invocations, 200 concurrent Realtime connections and 2 million Realtime messages.
- No automatic backups. Supabase's own backup docs recommend that Free projects export their data regularly, for example with
db dump. - Pausing. Free projects are paused after one week of inactivity. You restore them from the dashboard.
The pause rule is the one that catches people. A demo you send to a client on Monday may be paused by the following Monday if nobody uses it.
#How the Pro plan bill is built
The $25 is a starting point. A Pro bill has three layers.
#1. The base plan
$25 a month, charged up front. Usage above the included quotas is billed at the end of the month.
#2. Compute per project
Every Supabase project runs on its own compute instance, and every instance costs money. The $10 of monthly compute credits covers one Micro instance. As of November 2026 the compute add-ons are:
| Size | RAM | Price |
|---|---|---|
| Micro | 1 GB, shared CPU | $10/mo |
| Small | 2 GB, shared CPU | $15/mo |
| Medium | 4 GB, shared CPU | $60/mo |
| Large | 8 GB, 2 dedicated vCPUs | $110/mo |
So a second project on Pro is not free. Supabase's own example: a Pro organization with two Micro projects costs $35 a month ($25 + $20 of compute − $10 of credits).
#3. Usage above the quotas
| Meter | Included on Pro | Price above |
|---|---|---|
| Database disk | 8 GB per project | $0.125 per GB |
| Egress | 250 GB | $0.09 per GB |
| Cached egress | 250 GB | $0.03 per GB |
| File storage | 100 GB | $0.0213 per GB |
| Monthly active users | 100,000 | $0.00325 per MAU |
| SSO MAU | 50 | $0.015 per MAU |
| Edge Function invocations | 2 million | $2 per million |
| Realtime messages | 5 million | $2.50 per million |
| Realtime peak connections | 500 | $10 per 1,000 |
| Image transformations | 100 origin images | $5 per 1,000 origin images |
The spend cap is on by default on Pro. With it on, usage stops at the included quotas instead of growing your bill. Turn it off and the rates above apply.
#Add-ons that change the picture
- Point-in-time recovery: $100 a month per 7 days of retention. Supabase's backup docs add that PITR needs at least the Small compute add-on.
- Branching: $0.01344 per branch per hour.
- Custom domain: $10 per domain per month, per project.
- Log drains: $60 per drain per month, plus $0.20 per million events and $0.09 per GB of egress.
- Disk performance: IOPS above 3,000 cost $0.024 each, and throughput above 125 MB/s costs $0.095 per MB/s.
#Worked examples
These use the Pro rates above. Treat them as estimates. Disk is billed on the provisioned size, which can grow ahead of your actual data.
#A side project
One project, 200 MB of data, 2,000 users, 3 GB of egress. Free plan: $0. Watch the one-week pause and the lack of backups.
#A small production app
One project, 4 GB of data, 30,000 MAU, 120 GB of egress, no PITR. Pro: $25. Everything fits in the quotas and the credits cover the Micro instance.
#An app that is growing
One project, 20 GB of data, 150,000 MAU, 400 GB of uncached egress, and you want 7 days of PITR.
| Line | Cost |
|---|---|
| Pro base | $25.00 |
| Small compute ($15 − $10 credits), needed for PITR | $5.00 |
| Disk: 12 GB over 8 GB × $0.125 | $1.50 |
| MAU: 50,000 over 100,000 × $0.00325 | $162.50 |
| Egress: 150 GB over 250 GB × $0.09 | $13.50 |
| PITR, 7 days | $100.00 |
| Total | about $307.50 |
Two lines dominate: monthly active users and PITR. Disk and egress are small by comparison.
#An agency with four small client apps
Four projects, each small enough for Micro. Pro: $25 + 4 × $10 − $10 = $55 a month, before any usage.
#How to estimate your own bill
You don't need a third-party Supabase pricing calculator. Take these numbers from your analytics or your current dashboard and run them through the tables:
- Number of projects and the compute size each needs. Staging environments count.
- Database size per project in 3 to 6 months, not today.
- Peak monthly active users. Anonymous sign-ins count as users on most platforms, so check how your app uses them.
- Egress, split into cached (CDN) and uncached if you can. Storage downloads and API responses both count.
- Recovery needs. If you could not live with losing a day of data, price PITR in from the start.
Then add a margin. Usage-based bills rarely go down by themselves.
#Where Supabase pricing is a good deal
Be fair to the $25 plan: for one production project with under 100,000 users and modest traffic, it is a solid price for Postgres, Auth, Storage, Realtime and Edge Functions with 7 days of daily backups. Supabase also offers many AWS regions, a self-hosted option and the largest ecosystem in this space. If you need US or APAC hosting, those count more than a few dollars.
#How StitchDB pricing compares
StitchDB runs the same open APIs (PostgREST-style REST, Auth, Storage, Realtime and Deno Edge Functions), so code written with supabase-js keeps working when you change the URL and keys (compatibility). Its plans, as of November 2026 (see pricing and plans and limits):
| Free | Pro | Scale | |
|---|---|---|---|
| Price | $0 | $15.99/mo | $49/mo |
| Projects included | 2 | 1 (extra: $9/project-month) | 2 (extra: $15/project-month) |
| Database | 500 MB per project | 10 GB per project | 20 GB per project |
| Egress | 25 GB | 1 TB | 2 TB |
| File storage | 1 GB | 100 GB | 250 GB |
| Monthly active users | 50,000 | 100,000 | 200,000 |
| Point-in-time recovery | None | 7 days, included | 14 days, included |
Run the "growing app" example on StitchDB. On Pro: $15.99, plus 10 GB of extra database at $0.12 ($1.20), plus 50,000 extra MAU at $0.002 ($100), for about $117 with the spend cap off. On Scale, the same app fits in the included amounts: $49. The four-project agency costs $15.99 + 3 × $9 = $42.99 on Pro.
Other differences that affect cost:
- Free projects don't pause after a week. Idle Free projects keep the database online and their API services wake on the next request. Only accounts nobody has used for a year are paused (inactive projects).
- Usage is prepaid. Overage is charged from prepaid credit, with a monthly spending cap that defaults to $20 (spend cap). That means no surprise invoice, but you need to raise the cap and top up before a big month.
- Pro includes one project. If you run many tiny projects, Supabase's $10 Micro instances can be cheaper per project than StitchDB's $9 extra project plus its own database allowance. Do the math for your case.
The honest trade-offs: StitchDB hosts only in the EU (Germany and Finland), has no self-hosted edition, and is a younger platform with a smaller community. If those matter more than the bill, Supabase is the better fit. For a full side-by-side, see StitchDB vs Supabase; to move a project, see how to migrate from Supabase.
#FAQ
#Is Supabase free forever?
The Free plan has no time limit, but projects are paused after one week of inactivity and you get two active projects. It has no automatic backups, so export your data yourself.
#Why is my Supabase bill higher than $25?
Usually because of extra projects (each needs compute beyond the $10 credit), monthly active users above 100,000, egress above 250 GB, or add-ons like PITR ($100 per 7 days) and custom domains ($10 each).
#Does the Supabase spend cap stop all charges?
On Pro, the spend cap is on by default and limits usage-based charges to the included quotas. Compute for extra projects and add-ons you choose are still billed.
#How much does point-in-time recovery cost on Supabase?
$100 a month per 7 days of retention as of November 2026, and the project needs at least the Small compute add-on.
#Can I move a Supabase project without rewriting my app?
To a compatible platform, yes. StitchDB's Import from Supabase copies the database, auth users with their passwords, files, cron jobs and function code; the app keeps its client calls and gets a new URL and keys.
Compare your own numbers on the StitchDB pricing page.