Supabase Pricing in 2026: What You'll Actually Pay (with Calculator)

Supabase pricing is one of those questions that looks simple until you open the pricing page and realize the $25 Pro plan is only the starting line. There is a compute credit, a compute tier ladder, separate meters for storage and egress, and a free tier with limits that change what "free" means in practice. Most articles flatten all of that into "it's $25 a month" and leave you to discover the rest on your first invoice.

This post breaks down what you will actually pay, verified against our Supabase pricing calculator and modelled across four real workloads.

Verified against Supabase's published rates as of May 2026. Every number in this post comes from our pricing calculator's source-of-truth provider file, not from rough estimates. Where a figure is not in that file (Team and Enterprise base fees), I say so instead of guessing.

Supabase's 2026 Pricing Model in 60 Seconds

Supabase sells a Backend-as-a-Service, not just a database. That single fact drives everything about how the pricing reads. When you pay for Supabase Pro you are paying for Postgres, Auth, Storage, Edge Functions, and Realtime in one line, which is why a per-gigabyte comparison against a pure-database provider is misleading until you add back the services it bundles.

Here are the plans:

The Pro plan is where almost every paying SaaS lives, and it works like this: $25 per month gets you the full bundle plus a $10 monthly compute credit. The credit covers one Micro compute instance, so if your database fits on Micro, your compute line is effectively free. Everything past that is billed on a handful of meters.

Here are the Pro meters with verified May 2026 rates:

The thing that trips people up is compute. Unlike Neon, Supabase does not scale to zero on Pro. You pay for the selected compute instance 24/7, so picking the right tier matters more than it does on a serverless provider.

Supabase Free Tier Limits

The Supabase free tier is genuinely usable for prototypes and side projects, but it has two limits that decide whether you can ship on it.

Supabase Free plan limits:

• Database: 500 MB Postgres storage
• Auth: 50,000 monthly active users (MAU)
• Egress: 5 GB per month
• File storage: 500 MB
• Projects: up to 2 active projects
• Pausing: projects auto-pause after 1 week of inactivity

That last line is the one that bites. A free project with no traffic for a week goes to sleep, and you have to manually restore it from the dashboard. That is fine for a demo, not fine for anything a customer might hit on day eight. The 50,000 MAU allowance is unusually generous (Auth is the service most providers charge for first), so the wall you hit first is almost always the 500 MB database or the auto-pause, not the user count.

If either of those is a problem, you are on Pro, and Pro removes pausing entirely. Free projects pause; Pro projects stay running.

Supabase Compute Pricing

Supabase compute is provisioned as dedicated instances, not serverless functions. You pick a tier, and you pay for it around the clock. The $10 Pro credit is subtracted from whatever tier you choose, so the real cost of moving up a tier is the difference, not the full sticker price.

The Micro instance (2-core ARM, 1 GB RAM) handles most early-stage SaaS workloads, which is why so many Pro accounts sit at a flat $25/month: the compute credit fully covers Micro. Move to Small (2 GB) when you need more concurrent connections, Medium (4 GB) for compute-heavy queries, and Large (8 GB) for high-throughput production databases.

The jump from Small ($5 extra) to Medium ($50 extra) is the steepest step on the ladder, so it is worth profiling your queries before assuming you need Medium. A connection pooler (Supavisor, included) often buys you more headroom than a bigger instance.

Supabase Storage Pricing

Supabase database storage is billed simply: 8 GB is included on the Pro plan, and overage is $0.125 per GB per month.

That rate applies to your Postgres database storage. So a 20 GB database costs the $25 base plus 12 GB of overage at $0.125, which is $1.50 a month on top. Storage is rarely the line that dominates a Supabase bill, even at scale: a 50 GB database is only $5.25/month of storage overage.

Two things to keep straight. First, file storage (uploads, images, the Storage service) is metered separately from database storage and ships with its own generous allowance on Pro, so the 8 GB figure here is specifically the Postgres database. Second, Point-in-Time Recovery is a separate add-on at $100/month per 7-day retention window, which is the single most expensive optional line most teams forget to budget for.

Supabase Egress Cost

Egress (data transferred out of Supabase) is included up to 250 GB per month on Pro, then $0.09 per GB after that.

This is the meter most likely to surprise you at scale, because it scales with traffic rather than with how much data you store. A media-heavy app serving 1 TB of egress pays for 750 GB of overage at $0.09, which is $67.50/month on top of the base. For comparison, the 250 GB included allowance covers a typical API-driven SaaS comfortably; you have to be serving large files or a lot of them to blow past it.

If egress is your dominant cost, that is a signal to put a CDN in front of file delivery rather than serving everything straight from the database or Storage origin.

Supabase Pricing Examples: 4 Real Workloads

Here is what Supabase actually costs across four workloads, computed from the calculator's rates. Inputs are stated so you can reproduce each number.

1. Side project (Free plan) Inputs: 500 MB database, under 5 GB egress, low traffic. Cost: $0/month. The free tier covers it, with the caveat that the project auto-pauses after a week of inactivity.

2. Early SaaS (Pro, Micro compute) Inputs: Micro compute (1 GB RAM), under 8 GB storage, under 250 GB egress. Cost: $25/month. The compute credit covers Micro, and you stay inside the included storage and egress allowances. This is the flat-rate sweet spot.

3. Growing SaaS (Pro, Small compute) Inputs: Small compute (2 GB RAM), 20 GB storage, 300 GB egress. Cost: $36/month. That is $25 base, plus $5 compute (Small $15 minus the $10 credit), plus $1.50 storage (12 GB over 8 at $0.125), plus $4.50 egress (50 GB over 250 at $0.09).

4. Scale (Pro, Medium compute) Inputs: Medium compute (4 GB RAM), 50 GB storage, 1 TB egress. Cost: $148/month. That is $25 base, plus $50 compute (Medium $60 minus credit), plus $5.25 storage (42 GB over 8), plus $67.50 egress (750 GB over 250). Note how egress is now the largest single line.

The pattern across all four: compute and egress drive the bill, storage barely moves it, and the bundled services (Auth, Storage, Edge Functions, Realtime) cost nothing extra at these tiers.

Supabase vs Neon, PlanetScale, Xata, and Convex

This is where the BaaS-versus-pure-database distinction earns its keep. The table below models the same workload across five providers using each provider's own rates from our calculator: 1 GB RAM, 20 GB storage, 300 GB egress, always-on.

Read that table carefully, because the cheapest number is not the best deal. Supabase at $31 includes Auth and Storage and Edge Functions and Realtime. The $15 Xata bill and the $23 PlanetScale bill are database only. To match what Supabase bundles, you would add an auth provider (Clerk or Auth0 run $20 to $30/month at 10K+ MAU) and object storage with a CDN ($5 to $15/month on S3 plus CloudFront). Add those back and Supabase is the cheaper bundle, not the more expensive one.

Where each alternative genuinely wins:

• Neon ($46 always-on, less with scale-to-zero): pure serverless Postgres with scale-to-zero and instant branching. Best when compute is bursty and you are happy running Auth and Storage yourself.
• PlanetScale ($23 single-node, $43 HA): millisecond billing and true 3-node HA from $15/month. Best when high availability is non-negotiable.
• Xata ($15): the cheapest pure-Postgres option here, with scale-to-zero and copy-on-write branches. Best for cost-sensitive Postgres workloads that do not need a bundled backend.
• Convex ($55): reactive queries and a TypeScript-native document model. Best for real-time apps, but it is not Postgres, so migration means rewriting your data layer, and per-seat pricing grows with team size rather than usage.

For a wider view of the category, see our guide to the best database software for startups and our head-to-head on Supabase vs Firebase.

Why Supabase Is MakerKit's Default

I will be straight about the bias: MakerKit ships with first-class Supabase integration, so when I recommend it I have skin in the game. Here is the honest version of why it is our default anyway.

The bundle is the argument. For a new SaaS you need a database, authentication, file storage, and usually some realtime and serverless glue. Supabase gives you all of it for $25/month with Auth at 50,000 MAU included, which is the line that would otherwise be your first painful bill on a dedicated auth provider. Assembling the equivalent from a pure database plus Clerk plus S3 plus a functions layer costs more and means four dashboards instead of one.

The second argument is Postgres with Row Level Security. You get standard Postgres (no proprietary query language, works with every ORM) and per-row access control enforced at the database layer. MakerKit leans on RLS heavily for multi-tenant isolation; if you want the details, read our Supabase RLS best practices guide. Pair it with Drizzle and you get typed queries on top of policies you can actually reason about.

Where I would not pretend Supabase is perfect: it does not scale to zero on Pro, so an idle-heavy workload pays for compute it is not using, and Neon or Xata will be cheaper there. And at very high egress, the $0.09/GB meter adds up, so put a CDN in front of file-heavy delivery.

If you are choosing the rest of your stack at the same time, our modern SaaS stack for 2026 covers database, auth, payments, and deployment together.

Calculator: Estimate Your Real Supabase Bill

This post explains the numbers; the Supabase pricing calculator computes them for your workload. Plug in your compute tier, storage, and egress, and it returns a line-by-line monthly estimate using the exact rates in this article.

Then switch to the calculator hub to run the same workload against Neon, PlanetScale, Xata, and Convex side by side. Every number here traces back to that calculator's source code, so you can check the math against Supabase's published rates.

Quick Recommendation

Supabase is best for:

• Teams that want a full backend (database, auth, storage, realtime) from one provider
• Postgres-first SaaS that relies on Row Level Security for multi-tenancy
• Apps where the bundled Auth at 50,000 MAU replaces a separate, pricier auth bill
• MakerKit projects, where the integration is first-class out of the box

Skip Supabase if:

• Your workload is idle-heavy and scale-to-zero would save real money (look at Neon or Xata)
• You need true multi-node HA as a hard requirement (PlanetScale ships it from $15/month)
• You want a reactive document model over Postgres (Convex)

Our pick: Supabase Pro at $25/month for the first stage of almost any Postgres SaaS. The compute credit keeps most early apps at a flat $25, and the bundled Auth and Storage make it the cheapest real backend once you account for the services it includes. Re-evaluate against Neon or Xata only when idle compute or egress starts dominating your bill, which our calculator will show you before the invoice does.

Disclosure: MakerKit ships Next.js SaaS kits with first-class Supabase integration. We make money when you buy a kit. We are not paid by Supabase or any other provider on this list, and every price here is verified against our open calculator code.

Next Steps

If you are picking a database, compare the field in our guide to the best database software for startups, or read Supabase vs Firebase for the head-to-head. Choosing the whole stack at once? Our modern SaaS stack for 2026 covers database, auth, payments, and deployment together, and the Supabase pricing calculator will give you a real number for your own workload.