Aanchal Parmar
Product Marketing Manager, Flexprice
Supabase is a leading open-source backend platform built on PostgreSQL, offering developers a complete toolkit to build, scale, and manage modern web and mobile applications. From real-time databases and authentication to edge functions and storage, it provides the infrastructure teams need, without the complexity of managing it themselves.
Its pricing model is built to match that flexibility, scaling smoothly from hobby projects to enterprise deployments without forcing you to re-architect or renegotiate. In this guide, we'll break down how Supabase pricing works: plan tiers, usage-based overages, compute and storage add-ons, and how to choose the right setup based on your needs (or apply the same logic to your own SaaS).
What is Supabase?
Supabase is an open-source backend-as-a-service that gives developers everything they need to build, ship, and scale modern applications, without managing infrastructure. It's built on PostgreSQL and offers a full set of tools out of the box: database, authentication, file storage, edge functions, and real-time APIs.
It's often called the "open-source Firebase alternative," but Supabase is designed with SQL-first devs in mind. You get a familiar relational database, unrestricted data access, and the ability to self-host or deploy instantly in the cloud. Whether you're building an internal tool, an AI or agentic product, or a mobile app, Supabase handles the backend so you can focus on your app logic.
More recently, Supabase has been shipping heavily toward AI-native and analytics workflows. A one-click Stripe Sync Engine now pulls customers, subscriptions, and invoices straight into your Postgres so you can query billing data with plain SQL. The dashboard added AI table filters that turn natural language into the right Postgres queries, and an Index Advisor that flags missing indexes automatically. Through the Hydra acquisition, Supabase Warehouse is rolling out as an open data warehouse for analytics workloads, and Multigres adds horizontal sharding for teams scaling Postgres past a single node.
Key Features:
PostgreSQL database with instant REST & GraphQL APIs
Authentication & user management with email, OAuth, magic links, and more
Supabase Storage for file uploads, access control, and CDN delivery
Edge Functions (based on Deno) for server-side logic and scheduled jobs
Real-time subscriptions for syncing data via websockets
Row-level security and policies for fine-grained access control
Built-in dashboard for managing usage, projects, roles, and logs
Self-hosting support for full ownership and compliance
How Supabase's pricing model works today
Supabase uses what's called a hybrid pricing model: base fee with usage-based charges. That means you pay a fixed monthly fee for a base plan, then pay extra if you cross certain usage limits.
This model isn't unique to Supabase. You'll see it in most AI and agentic platforms, because it aligns pricing with actual resource usage. But what makes Supabase more transparent than most is that it clearly separates fixed and variable costs, and gives developers control over spend through usage dashboards and a default spend cap.
How Supabase plans scale with you
Supabase offers four main pricing tiers: Free, Pro, Team, and Enterprise. On paper, they look like standard SaaS plans, but in practice, each tier is structured to match a very specific stage of growth.
Free is meant for side projects and experiments. You get generous limits.
50k MAUs
500 MB database
5 GB egress and 5 GB cached egress
1 GB file storage
500K Edge Function invocations
But only two active projects and limited backups
Inactivity also leads to auto-pausing, which keeps infrastructure costs in check.
Pro ($25/month) is the default choice for solo devs, indie projects, or early-stage startups. It bumps up your limits.
100k MAUs
8 GB DB per project
250 GB egress and 250 GB cached egress
100 GB file storage
2 million Edge Function invocations
$10 of compute credit included
Importantly, the Pro tier turns on spend caps by default, so your bill stays predictable. Each project runs on its own compute instance and is billed separately, so as you spin up additional projects, your monthly cost scales with them.
Team ($599/month) is where compliance kicks in. You get SSO for the Supabase Dashboard, SOC 2 and ISO 27001 certifications, AWS PrivateLink, longer backup retention, and log storage for 28 days. You're not paying for more compute, you're paying for enterprise-grade security.
Enterprise (custom pricing) adds SLAs, 24/7 support, a private Slack channel, and the ability to deploy in your own cloud (BYO cloud). This tier isn't usage-driven; it's risk-driven. If your company needs legal reviews and uptime guarantees, this is what you choose.
What's notable here is the steep jump from Pro to Team. It's intentional. Supabase doesn't blur the lines between indie use and enterprise use. If you're asking for SSO and audit logs, you're likely a B2B company, and Supabase prices accordingly.
We'll get into the actual resource allocations in the next section. But for now, the key takeaway: these tiers aren't just about features, they're about stage of usage.
What you get with each Supabase plan
Pricing pages usually show numbers, MAUs, GBs, and API calls. But what do those limits actually mean when you're building a real product?
Let's break it down:
100k MAUs on Pro is more than enough for most SaaS or mobile apps in early stages. MAU here means a user who makes a request during the month. So if your app has 20k users, but only 10k use it monthly, you're using 10k MAUs.
250 GB egress sounds like a lot, but it depends on what you're serving. For a chat app or text-based API, you'll barely touch it. But if you're serving media, it adds up fast. For example, 5,000 users downloading a 50 MB audio file equals 250 GB egress, your entire monthly quota.
8 GB of database per project is generous for most early apps. If you serve heavy files, large reports, image-heavy dashboards, or exports, you'll need to monitor usage more closely.
Edge functions: Pro gives you 2 million invocations per month. This easily covers authentication, webhooks, and lightweight processing. If you're running cron jobs or heavy AI workflows, this will be the first thing that hits a limit.
Storage (100 GB) covers basic file uploads like profile pictures, PDFs, and small media. But you'll want to monitor this if you're working with audio, video, or user-generated content.
Most devs won't hit these limits for months, but once you do, overages kick in. And that's where understanding usage upfront matters. Supabase gives you headroom to build, but if you're not tracking usage, things can add up quickly.
When and why overages kick in
Every Supabase paid plan includes generous monthly limits, but once you cross those, overages start. These aren't hidden fees; they're usage-based charges tied directly to infrastructure costs.
Here's how it works:
Metric | Pro Plan Limit | Overage Rate |
MAUs | 100,000 | $0.00325 per extra user |
Egress (bandwidth) | 250 GB | $0.09 per extra GB |
Cached Egress | 250 GB | $0.03 per extra GB |
File Storage | 100 GB | $0.021 per extra GB |
Edge Function Calls | 2 million/month | $2 per million calls |
Realtime Concurrent Connections | 500 | $10 per 1,000 |
Realtime Messages | 5 million/month | $2.50 per million |
Let's say your app grows to 150k MAUs; that's 50k over the limit. You'll pay 50,000 × $0.00325 = $162.50 extra that month.
This is standard for infrastructure pricing. You get a base quota, and then pay linearly beyond that. Think of it like a phone plan, your monthly charge covers normal use, and you're billed extra for anything beyond.
What's helpful is that Supabase gives you usage dashboards and lets you set a spend cap. So if you don't want to ever go above $25/month, you can lock it there. But if you're okay with variable cost based on growth, the system scales with you.
How Supabase handles compute, storage, and performance upsells
Supabase lets you scale specific parts of your infrastructure: compute power, disk type, and disk size, without jumping to a higher pricing tier.
This is especially useful if most of your projects are small, but one of them needs more power or performance.
Compute instances
Each Pro project starts with a Micro instance (1 GB RAM, 2-core ARM), and the $10 monthly compute credit on Pro and Team plans covers one Micro instance. You can upgrade to more powerful configurations, all the way up to 64-core, 256 GB instances.
Pricing scales linearly. Example:
Micro: $10/month (covered by the included compute credit)
Small: $15/month, 2 GB RAM
Medium: $60/month, 4 GB RAM
Large: $110/month, 8 GB RAM, dedicated CPU
XL: $210/month, 16 GB RAM
2XL: $410/month, 32 GB RAM
It scales up through 4XL, 8XL, 12XL, and 16XL at $3,730/month with 64 cores and 256 GB RAM. Beyond that, sizing is custom.
So if one of your apps is CPU-bound or handling heavier queries, you can scale just that instance without changing your Supabase plan.
Disks and storage performance
By default, Supabase uses General Purpose disks. If your app needs faster read/write speed, you can switch to High Performance disks for an added cost.
General Purpose: $0.125 per GB (after the first 8 GB), 3,000 IOPS included, then $0.024 per IOPS, 125 MB/s throughput included, then $0.095 per MB/s, max size 16 TB, 99.9% durability.
High Performance: $0.195 per GB, $0.119 per IOPS, throughput scales automatically with IOPS, max size 60 TB, 99.999% durability.
You pay based on disk size, the IOPS (Input/Output Operations per Second) you provision, and throughput. This modular approach gives you control. You're not forced into paying $599/month just because one database needs better performance. You upgrade what matters, leave the rest alone.
Optional add-ons
Beyond compute and disk, Supabase has a handful of priced add-ons you can switch on when you need them:
Point-in-Time Recovery (PITR): $100/month per 7 days of retention
Custom Domain: $10 per domain per month per project
Database Branching: $0.01344 per branch, per hour
Advanced MFA (Phone): $75/month for the first project, then $10/month for each additional project
SAML / SSO Auth: 50 MAUs included, then $0.015 per MAU
Log Drains: $60 per drain per month, plus $0.20 per million events and $0.09 per GB egress
Image Transformations: 100 origin images included, then $5 per 1,000 origin images
These are mostly things you don't need on day one, but they're useful to know about before you go looking for them in a higher tier.
How Supabase reduces bill anxiety for developers
Supabase is one of the few platforms that bakes billing safeguards into the product.
Spend Cap Enabled by Default
On the Pro plan, projects won't exceed the $25/month base unless you manually turn off the cap. That means no surprise overages.
Real-Time Usage Tracking
You can monitor MAUs, egress, storage, and function calls directly from the dashboard, with alerts when you approach limits.
Free Projects Auto-Pause
Inactive free projects are paused after 7 days, so you're not unintentionally racking up usage if you upgrade later.
These features give developers control over cost without needing to set up external monitoring or worry about billing blowups.
Why Supabase doesn't offer annual plans
Supabase only offers monthly billing. No discounts for paying yearly, no lock-in contracts. That's by design.
Most developers don't want to commit to a full year when the product, team, or usage might change in three months. Monthly billing gives them room to experiment, pivot, or shut things down, without chasing refunds or getting stuck with credits they won't use.
It also matches the way most infrastructure scales: gradually. You start small, track usage, and decide when to grow. Supabase supports that pace by keeping costs flexible and commitment low.
If you're running long-term production workloads, it's still easy to set up autopay and let things run. But the monthly cycle keeps decision-making in the developer's hands, not tied to finance timelines or annual renewals.
How to choose the right Supabase plan for your project
If you're unsure which Supabase plan fits your needs, start by mapping your current workload, not just your budget.
Choose Free if:
You're building a prototype, hackathon project, or MVP.
You don't need backups or team access.
You're okay with the project being paused after 7 days of inactivity.
Choose Pro ($25/month) if:
You've shipped something to real users.
You want usage caps, backups, custom domains, and more storage.
You need cost controls but also room to grow.
Choose Team ($599/month) if:
You need SSO, SOC 2 or ISO 27001 compliance, or longer backup/log retention.
You're working in a regulated environment or selling to enterprises.
You want shared project access and audit history.
Choose Enterprise (Custom) if:
You need uptime SLAs, 24/7 support, or a BYO cloud setup.
Your organization requires legal reviews and vendor agreements.
If you're still unsure, start with Pro. The spend cap keeps things safe, and you can monitor usage before upgrading anything.
How to clone Supabase's pricing with Flexprice's Prompt to Plan Feature
If Supabase's pricing model resonates with how you want to charge for your own product, you don't have to build the billing infrastructure from scratch.
Flexprice's MCP server lets you replicate this exact structure, fixed plans, included compute credits, usage-based overages on MAUs, egress, and storage, plus modular add-ons like PITR or custom domains, without writing billing logic yourself.
You just have to give a simple prompt, and it’s ready. Let's see how this works.
Step 1:
First, visit our website Flexprice.io, then click on the Try For Free button to sign up
After that, a new window will open where you can fill in your credentials to get started with us
Step 2:
After you're signed up, the Flexprice dashboard will open up. Now, navigate to the product catalog, where you can see plans. Click on that
Step 3:
On the top right corner, you can see a button CREATE WITH AI, so click on that.
Step 4:
Once you click on that, a new window will appear, and there, provide a single prompt to analyze the Supabase pricing page and replicate its entire structure. In the prompt, include the Supabase pricing link : https://supabase.com/pricing.
Step 5:
After the analysis is over, a new window with all the features and plans will come up. Now, click on create and all of your plans will be created.
How to clone Supabase pricing model using Flexprice's MCP server
If the Supabase pricing model resonates with how you want to charge for your own product, you don't have to build the billing infrastructure from scratch. Flexprice's MCP server lets you replicate this exact structure without writing billing logic yourself. Let's see how this works:
Step 1:
First, you need to ensure that you are successfully set up with the Flexprice MCP server. You can check it by going into settings, then into developer options. There, you can see the Flexprice MCP server status.
Step 2:
Access Claude or any other AI tool that integrates with the MCP server.
Step 3:
Provide a single prompt asking the AI tool to analyze the Supabase pricing page and replicate its entire structure through the Flexprice MCP. In the prompt, include Supabase’s pricing page link: https://supabase.com/pricing
Step 4:
Wait a few moments while the AI automatically processes the prompt and generates the necessary billing infrastructure plans
Step 5:
Navigate to your Flexprice dashboard to review the newly created assets. You will find that the AI has used the context from Supabase’s pricing page to automatically pre-fill and create plans.
Wrapping up
Supabase's pricing model is built for how developers actually work: start small, track usage, scale when you need to. The Free tier covers prototyping and MVPs. Pro at $25/month gives you room to grow with spend caps that keep bills predictable. And when you need compliance or enterprise features, the jump to Team makes sense.
What matters most? You're not paying for complexity you don't need, and you won't hit walls when you're ready to grow. Start with Free, monitor your usage, upgrade to Pro when you ship to real users. The pricing scales with your project, not against it.
If you're ready to build your own Supabase pricing, then either you can sign up for the tool or use our open source to create it. If you're tired of solving billing from scratch, you don't have to keep doing it alone.
⭐ Star us on GitHub to follow our progress
🤝 Join our community to share feedback and collaborate
