Supabase pricing in 2026: free plan limits and what a SaaS really pays

Supabase pricing starts at $0. The Free plan includes a 500 MB database, 1 GB of file storage, 5 GB of egress and 50,000 monthly active users, but pauses quiet projects after a week. Pro costs $25 a month and covers a typical early SaaS with room to spare; you pay extra only for usage beyond its quotas.

Every figure below comes from Supabase's pricing page and billing docs as of October 2026, in US dollars. One note before the numbers: this blog belongs to shipanysaas, a starter kit built on Supabase, so we have a stake in Supabase being affordable. The worked examples show every assumption, so you can redo them with your own.

How much does Supabase cost?

Supabase has four plans: Free at $0, Pro from $25 a month, Team from $599 a month, and Enterprise at a custom price. The plan fee is charged once per organization. Most quotas, such as egress and monthly active users, are shared by every project in it; database size is per project.

Team adds SOC 2 and ISO 27001, SSO for the Supabase dashboard, and read-only and project-scoped roles, with HIPAA as a paid add-on. Those cover Supabase's side of a vendor review; they don't make your own app compliant.

What does the Supabase free tier include?

The Supabase free tier gives you two active projects, each with a 500 MB database on a shared Nano instance, plus 1 GB of file storage, 5 GB of egress, 50,000 monthly active users, 500,000 Edge Function invocations and 2 million Realtime messages a month. Nothing is billed on Free.

It is a real plan for building and testing. Here is where it stops:

• Quiet projects pause. Supabase may pause a Free project that gets little database activity over 7 days, and emails a warning about a week before. According to the project pausing docs, a few requests a day are usually enough to avoid it. A paused project keeps its data and can be restored within a year.
• The database turns read-only at 500 MB. Past that, writes stop until you upgrade or shrink the data.
• There are no automatic backups. Daily backups start on Pro. On Free, any backup is one you take yourself.
• Two projects in total. The limit counts every organization where you are an owner or admin. Paused projects don't count.
• The built-in email server is for testing. It sends 2 messages an hour, only to members of your project's team, and Supabase's SMTP guide says it "is not meant for production use". Custom SMTP is included on every plan, Free too, so set it up before real users sign up.
• Logs last one day, and Nano is a shared CPU with up to 0.5 GB of memory. Supabase notes that Free compute may change.

The free plan is enough to build a whole product on. shipanysaas runs on it during development, and because the kit's Next.js web app and Expo phone app share one Supabase project, going live means paying for one project's compute, not two.

What does Supabase charge beyond the included usage?

On Pro and Team, usage past the included amounts is billed per unit at the rates below. On Free nothing is billed: going over gets you a warning and a grace period, and the database turns read-only past 500 MB.

A few details change the arithmetic:

• Disk is billed on its provisioned size, not on the data in it. When the database reaches 90% of the disk, Pro grows the disk by 50%, so 8 GB becomes 12 GB. That only happens with the spend cap off.
• Storage is averaged over the month. It's measured in GB-hours, so 20 GB kept for half the month bills as 10 GB.
• A monthly active user is anyone who signs in or refreshes a token during the billing cycle, counted once however often they come back.
• Add-ons are separate: point-in-time recovery is $100 a month per 7 days of retention, a custom domain $10 a month per project, phone MFA $75 a month for the first project and $10 for each one after, and branching $0.01344 per branch per hour.

How do Supabase compute add-ons work?

Every Supabase project runs on its own Postgres server, and you pay for that server's size by the hour, separately from the plan fee. Pro and Team include $10 a month of compute credits, which covers one Micro instance.

The compute and disk docs list sizes up to 16XL, with 64 dedicated vCPUs and 256 GB of memory for about $3,730 a month. Beyond that you talk to Supabase.

Two rules shape the bill:

• Credits apply once per organization, compute applies per project. Supabase's own example: a Pro organization with two Micro projects pays $25 + $10 + $10 - $10 = $35 a month. A hosted staging project is a second compute bill.
• Paid plans start at Micro. Nano isn't available on Pro, so the smallest paid project uses $10 of compute, which the credit covers.

What does the Supabase spend cap do?

The spend cap, on by default for Pro, stops usage at the quota instead of billing for it: further use of that item is disallowed until the next billing cycle. It covers usage you can't predict, not the things you chose.

According to the cost control docs, the cap covers disk size, egress, Edge Function invocations, monthly active users (including SSO and third-party), Realtime, storage, image transformations and logs. It does not cover compute, custom domains, point-in-time recovery, phone MFA, IPv4 addresses, extra disk IOPS or throughput, log drains, branching or read replicas.

Leave it on while you build. Once customers pay you, an outage usually costs more than a few dollars of egress, which is the case for turning it off. It also has to be off for the disk to grow past 8 GB.

What does a SaaS really pay for Supabase?

For a B2B SaaS, our estimates come to $0 on Free at 100 users, $25 on Pro at 1,000 users and about $82 on Pro at 10,000 users. They are estimates: your database size and egress depend on what your product does, so swap in your own numbers.

The assumptions:

Also assumed: one production project, staging run locally with the Supabase CLI (so it costs nothing), no add-ons, prices before tax, and the spend cap off at 10,000 users so the disk and egress can grow.

100 users: $0 on Free, $25 on Pro

Everything fits the free plan: 50 MB of 500 MB, 0.3 GB of 1 GB storage, 3 GB of 5 GB egress, and 100 of 50,000 monthly active users. The bill is $0.

Once someone pays you, though, the gaps matter more than the price: no backups, a project that can pause in a quiet week, and only two projects. On Pro:

Pro plan             $25.00
Micro compute        $10.00
Compute credits     -$10.00
Total                $25.00

1,000 users: $25 on Pro

Free no longer fits. A 1 GB database is past the 500 MB read-only line, and 30 GB of egress is six times the free 5 GB. Pro fits with room to spare: 1 GB of an 8 GB disk, 5 GB of 100 GB storage, 30 GB of 250 GB egress, and 1,000 of 100,000 monthly active users.

Pro plan             $25.00
Micro compute        $10.00
Compute credits     -$10.00
Usage over quota      $0.00
Total                $25.00

If queries slow down on Micro's 1 GB of memory, Small costs $15 instead: $25 + $15 - $10 = $30.

10,000 users: about $82 on Pro

Here we assume Medium compute (4 GB of memory) for headroom. With 12 GB of data, the 8 GB disk has grown twice: to 12 GB when the data reached 7.2 GB, then to 18 GB at 10.8 GB. You pay for the 18 GB provisioned.

Pro plan                                    $25.00
Medium compute                              $60.00
Compute credits                            -$10.00
Disk: (18 GB - 8 GB) x $0.125                $1.25
Storage: (150 GB - 100 GB) x $0.0213         $1.07
Egress: (300 GB - 250 GB) x $0.09            $4.50
Users: 10,000 is under 100,000               $0.00
Total                                       $81.82

Compute is the biggest line, not usage. On Small instead of Medium, the same month costs $36.82.

What moves the bill

• Users past 100,000. A consumer app with 250,000 monthly active users pays (250,000 - 100,000) x $0.00325 = $487.50 a month for sign-ins alone.
• More projects. Each one adds its own compute; the $10 credit applies once.
• Point-in-time recovery, at $100 a month per 7 days of retention.
• The Team plan at $599 a month, when your customers' security reviews ask about SOC 2 or you need SSO for the dashboard.
• Phone sign-in and phone MFA. Phone MFA is $75 a month for the first project, and SMS goes through your own provider, which bills per message.

What are the downsides of Supabase?

The main downsides are operational: free projects pause and have no backups, compute is billed per project, the built-in email is for testing only, and your data is only as safe as your row-level security policies.

1. The free plan isn't for production. Pausing, no backups and a two-project limit are fine for building and risky with customers.
2. Environments multiply compute. A hosted staging project costs its own compute, and preview branches cost $0.01344 per branch per hour.
3. Auth email needs your own SMTP. At 2 messages an hour to team members only, the built-in server can't send real users their confirmation, reset or magic link emails.
4. Security is your job. Your publishable key ships in every browser and phone app, and Supabase's own docs warn that a table in an exposed schema without RLS is readable and writable by any role with a grant on it. Every table needs policies, and every policy needs a test. Supabase RLS explained shows how, and Supabase anon key vs service role key covers which key goes where. shipanysaas turns RLS on for all 13 of its tables and tests them with pgTAP; see Row-level security. The tables you add still need their own.
5. One primary database per project. You scale it up by compute size, and each size caps connections (Micro allows 60 direct and 200 through the pooler). Read replicas help with reads, not writes.

Can Supabase handle millions of users?

Supabase publishes no user limit; what limits you is one Postgres database per project and how well your queries and policies use it. Sign-ins scale by price: at 1,000,000 monthly active users, the Pro line for them is (1,000,000 - 100,000) x $0.00325 = $2,925 a month.

The rest is the same work any large Postgres app needs:

• Compute. Sizes run up to 16XL, and larger by arrangement.
• Read replicas. These are extra databases kept in sync with the primary to take read load off it. Each runs at the primary's compute size and is billed for it, with 1.25 times the primary's disk.
• Connections. Serverless and edge functions should use the shared pooler in transaction mode; paid plans also get a dedicated pooler.
• Policies and indexes. Index the columns your policies filter on, which in a multi-tenant app is nearly always account_id, and wrap auth.uid() in a select so it runs once per query.
• Load testing. Supabase's production checklist says to load test, preferably on staging, before you count on it.

So the honest answer: millions of users is a capacity and cost question, not a plan ceiling. Plan the compute, replicas and indexes, and test with data shaped like yours.

FAQ

Is Supabase free?

Yes. The Free plan costs $0 and includes two active projects, a 500 MB database for each, 1 GB of storage, 5 GB of egress and 50,000 monthly active users. The catches: a quiet project can pause after 7 days, and there are no backups, so most products move to Pro at $25 a month before launch.

Is Supabase Auth free?

Yes, up to 50,000 monthly active users on Free and 100,000 on Pro, then $0.00325 per user. Social logins, custom SMTP and basic multi-factor auth are included on every plan. SAML SSO is not on Free (Pro includes 50 users, then $0.015 each), phone MFA is $75 a month, and SMS goes through your own provider. Users from a third-party auth provider count as third-party monthly active users at the same rates; Clerk vs Supabase Auth compares the two setups.

Why not use Supabase?

Pick something else if your app must work offline first, if your data is document-shaped rather than relational, or if your team already runs everything on another cloud's database. Firestore, for example, has offline persistence built in, while Supabase relies on partner sync layers. Supabase vs Firebase goes through the trade-offs.

Does Supabase charge per API request?

No. Every plan includes unlimited API requests. You pay for what the requests move (egress) and the compute that serves them.

How much does Supabase cost for a small SaaS?

Usually $25 a month: the Pro plan, with Micro compute covered by the $10 credit and usage inside the quotas. Our 1,000-user estimate lands exactly there. If you'd rather start from a Next.js and Expo codebase with the Supabase side already built, see what the kit includes and pricing.