Supabase’s pricing model is “flat platform fee + included usage + per-unit overages.” That’s a different shape from most database pricing. Here’s what each tier really gives you, what overages cost, and how to predict your bill at 1K, 10K, and 50K MAU.
The three Supabase tiers are Free ($0/month), Pro ($25/month), and Team ($599/month), with an Enterprise tier above that for committed contracts. Each tier has a generous bundle of included usage and then bills overages per resource — database storage, bandwidth, monthly active users, file storage, and a few smaller categories. The official tier sheet lives at supabase.com/pricing and changes a few times a year. This guide walks each resource one at a time so you can predict your bill instead of guessing it.
Pricing source & method. All numbers in this guide were pulled from supabase.com/pricing in May 2026. Where Supabase has changed a number recently, we note it. Always reconcile with the live page before committing — Supabase adjusts overage rates more often than tier prices. How we research.
Most managed database providers price one of two ways: by compute (you pay for the size of the instance) or by usage (you pay per query, per row, per byte). Supabase does something in between. You pay a flat monthly platform fee that gets you a Postgres database, auth, storage, edge functions, and realtime — bundled. Then you get an included quota of each resource. If you exceed any individual quota, you pay overage on just that resource.
This bundled-then-overage shape is generous on the way up. You don’t need to forecast your peak workload precisely — you start at the right tier and pay slightly more if you exceed it on one axis. The downside is that newcomers find it harder to predict the bill, because four or five different resources can each tip into overage.
Three resources to mentally track: database size, monthly active users (MAU), and bandwidth. Almost every overage line on a real Supabase bill comes from one of those three.
The Free tier is real, not a trial. It lasts indefinitely as long as your project stays within limits and gets used. Here’s what it includes, per the official pricing page:
The most-misunderstood line on Free is the auto-pause. If your Free-tier project sees no requests for seven days, Supabase pauses it. You restore it with one click, but the project is unreachable until you do. This is fine for hobby projects and unacceptable for anything production. Even “low-traffic but real” SaaS apps get tripped up by this on slow weeks.
Free tier’s 50K MAU is high enough to support a fair-sized side-project user base. Database size at 500 MB is the more common ceiling — for an app with serious user-generated content, you can hit it surprisingly fast.
Pro is where most real solo SaaS founders end up. It’s the tier that exists to be “not Free” without being “startup-money expensive.” Per the pricing page, here’s the included usage:
The single biggest reason to upgrade to Pro isn’t database size or MAU — it’s the no-auto-pause guarantee. That alone makes Pro the floor for any real product. The 16× jump in database storage (500 MB to 8 GB) and 50× jump in bandwidth (5 GB to 250 GB) are the secondary reasons.
One important catch on Pro: $25/month covers the platform fee, but the included “compute” is the smallest instance. If your workload genuinely needs more CPU or RAM than the default instance provides — and most don’t until well past 1K customers — you can add compute add-ons starting around $10/month for a step up.
Team starts at $599/month and unlocks features that solo founders almost never need:
For solo SaaS founders, almost none of those matter. The honest test: if your customers aren’t enterprise buyers asking for SOC 2 and SSO, you don’t need Team. The ~$575/month gap between Pro and Team is overwhelmingly purchasing compliance, not capacity. If your product is consumer-facing or sells to small businesses, stay on Pro indefinitely — you can upgrade the day a deal requires it.
Once you exceed Pro’s included usage on a given resource, you start accruing overages. The published rates as of May 2026 (always re-check on supabase.com/pricing — they tweak these):
Roughly $0.125 per GB-month beyond the 8 GB included on Pro. So an extra 10 GB of database costs about $1.25/month. Database storage is rarely the runaway line item for normal SaaS workloads — it takes serious user-generated text or embeddings to push past 8 GB.
Roughly $0.09 per GB beyond 250 GB included. This is the line item that catches founders most often, because every API response, every image fetch, and every realtime message counts toward egress. A SaaS that serves a lot of media or has a chatty realtime channel can burn through 250 GB faster than expected.
Roughly $0.00325 per MAU beyond the 100,000 included. So 50,000 extra MAU = ~$162/month additional. Worth noting: a “monthly active user” in Supabase’s terms is a user who has authenticated at least once in the past 30 days, not a paying subscriber. Free-trial users count too.
Roughly $0.021 per GB-month beyond the 100 GB included on Pro, with bandwidth charged separately when files are downloaded. For typical SaaS where files are user-uploaded documents or images, you’ll hit bandwidth limits before file storage limits.
Roughly $2 per million invocations beyond the 2M included. Cheap enough that it’s rarely the line item that hurts — but if you’re running an AI proxy or a heavily-trafficked webhook handler, the count adds up.
The pattern across all overages: each individual rate is reasonable, but multiple resources tipping over at the same time can compound. Two GB of extra database, fifty GB of extra bandwidth, and 20K extra MAU is almost a full extra Pro tier in overages, even though you’ve barely exceeded any single quota.
Let’s assume a typical B2B SaaS with 1,000 monthly active users, 50 of whom are paying. Average user uploads ~2 MB of content per month. Average user generates ~30 MB of bandwidth per month (page loads, API calls).
| Resource | Estimated usage | Bill impact |
|---|---|---|
| Pro platform fee | — | $25.00 |
| Database storage | ~1 GB total (well under 8) | $0.00 |
| Bandwidth | ~30 GB (well under 250) | $0.00 |
| MAU | 1,000 (well under 100K) | $0.00 |
| File storage | ~2 GB (well under 100) | $0.00 |
| Predicted Supabase bill | $25.00 | |
Same SaaS, ten times the users. Now it gets interesting on a couple of axes.
| Resource | Estimated usage | Bill impact |
|---|---|---|
| Pro platform fee | — | $25.00 |
| Database storage | ~8 GB (right at the limit) | $0.00 |
| Bandwidth | ~300 GB (50 over) | $4.50 |
| MAU | 10,000 (well under) | $0.00 |
| File storage | ~20 GB (well under) | $0.00 |
| Predicted Supabase bill | ~$30/month | |
At 10K MAU you’re still mostly within Pro’s envelope. Bandwidth is the first quota you typically tip over, and even there the math is a few dollars. Database may also push past 8 GB depending on how much content your users generate.
Now we’re in “real product” territory. Same SaaS, fifty times the original users.
| Resource | Estimated usage | Bill impact |
|---|---|---|
| Pro platform fee | — | $25.00 |
| Database storage | ~30 GB (22 over) | $2.75 |
| Bandwidth | ~1.5 TB (1,250 over) | $112.50 |
| MAU | 50,000 (under 100K) | $0.00 |
| File storage | ~100 GB (right at limit) | $0.00 |
| Compute add-on (likely) | Small instance bump | $10.00 |
| Predicted Supabase bill | ~$150/month | |
The big takeaway: Pro is genuinely viable up to 50K MAU and beyond. You only need Team for compliance reasons, not capacity reasons. Many products with 100K+ MAU stay on Pro and just absorb the overages.
A short list of things you might assume are bundled but aren’t:
files.yourdomain.com instead of your-project.supabase.co, that’s a Custom Domain add-on (~$10/month).None of those line items matter for a solo founder pre-$10K MRR. They become relevant when you’re running a real B2B product with enterprise buyers or compliance requirements. For everyone else, the unmodified Pro tier is the right answer.
Cost-driven migration off Supabase usually happens for one of three reasons. Two are real, one is usually a mistake.
If you’re serving large media files or have a high-throughput realtime workload, Supabase’s $0.09/GB egress can become the largest line item on your bill. At a few thousand dollars per month of bandwidth, you can save real money by moving file delivery to Cloudflare R2 (which has zero egress fees) and keeping the Postgres+auth on Supabase. This is a partial migration, not a full one.
If you need fine-grained control over Postgres extensions, custom replication, or a different region than Supabase offers, you might land on a self-managed Postgres on RDS, Neon, or Render. Supabase vs Neon walks through the tradeoffs and the cost ceilings where each starts to look attractive.
Pro at $25 is genuinely cheap for what it bundles. If your bill feels expensive, the cause is almost always overage on a single axis (usually bandwidth) rather than the platform fee. Moving to a self-hosted Postgres + your own auth + your own storage almost never works out cheaper unless your time is free, because you’ve replaced one $25 bill with three smaller bills plus DevOps work.
The honest cost ceiling: if your Supabase bill exceeds $300/month and is dominated by overage, look at whether moving file storage off-platform makes sense. If your bill exceeds $1,000/month and you have time to maintain infrastructure, look at self-hosted Postgres. Below those numbers, stay.
Firebase’s pricing model is structurally different — per-read, per-write, per-document — which means certain workloads are dramatically cheaper on one or the other. Supabase tends to win for relational data with predictable query patterns; Firebase wins for sparse, document-shaped data with low write rates. The full breakdown is in Supabase vs Firebase.
If you’re early enough that you haven’t picked yet, the cost-only argument favors Supabase for typical SaaS workloads with users, posts, and relations. The $25 flat Pro fee makes budgeting much easier than Firebase’s per-operation model.
Supabase Auth is bundled into the platform fee. There’s no separate auth bill, just the MAU quota. Compared to standalone auth providers like Clerk — which charges per MAU above its free tier — Supabase is cheaper by a wide margin once you’re above 1K MAU. We covered the head-to-head in Clerk vs Supabase Auth.
The tradeoff is feature depth. Clerk has more polished out-of-the-box UI components and more auth providers ready to go. Supabase Auth is fine for ~80% of use cases and free at the margin once you’re paying for Supabase anyway.
One question we hear: does using Prisma or Drizzle on top of Supabase change the bill? Almost no. Supabase bills based on what hits the database — queries, storage, MAU. The ORM you choose affects developer ergonomics, not the meter. Prisma vs Drizzle covers the developer-experience side; cost-wise, treat them as equivalent on Supabase.
Pro at $25/month is the right answer for almost every solo SaaS in 2026. Free is for prototyping. Team is for enterprise compliance. Overages on Pro are reasonable until your bandwidth hits the multi-TB-per-month range, at which point you should consider partial migration of file delivery to a flat-fee CDN.
The mental shortcut: budget $25/month for Supabase from launch through 5K–10K MAU. Above that, watch the bandwidth and database storage lines on your monthly invoice and add a small buffer ($30–$50) into your budget. Don’t pre-emptively buy compute add-ons or jump to Team.
The stack, prompts, pricing, and mistakes to avoid — for solo founders building with AI.