Insights / October 24, 2026

Supabase pricing explained, from real production bills

A Supabase bill has three parts: a plan fee for your organization (Free, Pro from $25 a month, Team from $599, Enterprise on contract), compute billed by the hour for every project you run, and usage beyond the quotas your plan includes. Pro and Team include $10 a month of compute credits, so one Micro project on Pro costs $25 as long as usage stays within the quotas. For a growing app, the usage lines, especially Realtime messages and egress, are what make the bill move.

The numbers below are the ones on Supabase’s pricing page and billing docs. Prices change, so check those pages before you budget.

The plans

The plan belongs to the organization, not the project. Every project in an organization is on the same plan, and most usage quotas are shared across all of them. Database disk is the exception: paid plans include 8 GB per project.

Plan Price Daily backups Spend cap What else
Free $0 None N/A Two active projects, 500 MB database, 5 GB egress, 50,000 monthly active users. Pauses after a week idle
Pro From $25/mo 7 days On by default The usage quotas below
Team From $599/mo 14 days Not available Pro’s quotas, SOC 2 and ISO 27001 reports, dashboard SSO, 28-day logs
Enterprise Custom Up to 30 days Custom Custom quotas and pricing

On Team, usage over quota is always billed.

Compute: an hourly charge for every project

Each project is its own Postgres server, and you pay for that server by the hour whether anyone uses it or not. A partial hour is billed as a full hour. Paused projects cost nothing.

Compute size CPU Memory Approx. per month
Micro Shared 1 GB $10
Small Shared 2 GB $15
Medium Shared 4 GB $60
Large 2 dedicated vCPUs 8 GB $110
XL 4 dedicated vCPUs 16 GB $210
2XL 8 dedicated vCPUs 32 GB $410

The sizes go up to 16XL at about $3,730 a month. The $10 of monthly compute credits covers one Micro project, or takes $10 off a bigger one. Credits reset each month, don’t roll over, and don’t apply to preview branches or read replicas. Changing size restarts the database, usually with under two minutes of downtime.

What a small setup costs, before any usage over quota: one Micro project on Pro is about $25 a month, two Micro projects about $35, and one Medium project about $75. The $10 credit applies once per organization, not per project.

Compute is not covered by the spend cap. Neither are branches, read replicas, custom domains, IPv4 addresses or point-in-time recovery.

The usage lines and what’s included

On Pro and Team, these quotas cover the whole organization each billing cycle, except database disk, which is per project. You pay only for usage above them.

Usage item Included on Pro/Team Over the quota
Egress (data sent out) 250 GB, plus 250 GB cached $0.09 per GB, $0.03 per GB cached
Database disk 8 GB per project $0.125 per GB per month
Monthly active users 100,000 $0.00325 per user
File storage 100 GB $0.0213 per GB per month
Edge Function invocations 2 million $2 per million
Realtime messages 5 million $2.50 per million
Realtime peak connections 500 $10 per 1,000
Preview branches None Each branch’s compute and usage, from $0.01344 per hour

A few billing rules catch people out:

  • Realtime messages count once per receiver. A database change that 5 open tabs listen to is 5 messages. A Broadcast to 4 listeners is 5: one sent, four received. Your cost is what you send multiplied by who is listening.
  • Egress includes everything. Database queries, auth, file downloads, Edge Function responses and Realtime pushes all draw from the same quota. Files served from Supabase’s CDN cache count as cached egress at a third of the price.
  • Disk is billed on provisioned size. On paid plans the disk grows by 50% when it reaches 90% full, and it doesn’t shrink by itself when you delete data.
  • Usage is billed after the fact. Each invoice charges the plan fee for the coming month and usage for the month just ended, so a bad month shows up on the next invoice.
  • Every branch is a full project. With the GitHub integration, every pull request can get its own environment, billed hourly until the pull request is merged or closed.

What actually drove two real Supabase bills

A real-time trading platform

This app pushes live prices and order books to browsers and trading bots. In one billing cycle it sent over 2.5 billion Realtime messages, and they made up about three quarters of the Supabase bill. Egress was second, at about a sixth, and most of it was those same Realtime messages going out. Peak connections came to just two $10 packages.

The cause was fan-out. On one measured day, the app sent about 4.3 million messages and Supabase billed about 316 million, roughly 74 billed messages for every one sent. Bots subscribed to every market at once, and every market update carried its full order book.

During the most expensive week, the daily Supabase bill split like this:

Line Share of the daily Supabase bill
Realtime messages 79%
Egress 18%
Fixed charges 2%
Preview branches 1%

Launch load took the database from Medium to XL in two days. Past that point, more compute wasn’t the answer: the fix was the queries and design overloading it. Separately, the GitHub integration had been creating a preview branch for every pull request, adding about $10 a day until per-PR branching was turned off.

Realtime is open source, so we ran our own Realtime server side by side with Supabase’s, compared delivery, then switched over. Supabase’s daily cost fell by about 95%, to a small fixed amount plus ordinary egress. The new server’s bandwidth costs around a dollar per terabyte at its host, against $90 per terabyte for Supabase egress over the quota. The full story is in our article on Supabase Realtime pricing.

A media delivery app on Lovable Cloud

Lovable Cloud runs on Supabase, so the same lines drive its costs. For a media delivery app, where creators upload photos and video for their clients, two weeks of running costs split like this: Realtime 45%, network (egress) 41%, database 11%, storage 2%, AI under 1%. Every open dashboard was listening to every change to every file its creator owned, while background jobs updated those files around the clock. Polling where instant didn’t matter, and narrowing the subscriptions where it did, cut the Realtime line by about 90%.

Neither app’s bill was driven by the database itself. In both, the largest lines were live updates and the data they sent.

How to keep your Supabase bill under control

  1. Open the organization’s usage page and find the biggest line before changing anything. Select a project, then a branch, to see per-branch usage.
  2. Decide on the spend cap deliberately. With it on, Pro blocks overage on usage items like egress and Realtime messages, but after a grace period Supabase can restrict your projects, including switching databases to read-only. For a live product that can be worse than the bill. With it off, nothing stops the bill, so watch the Upcoming Invoice estimate on the billing page.
  3. Size compute from metrics, not panic. Check CPU and memory in the dashboard’s reports before upgrading. Medium and below share CPU, and Large is the first size with dedicated cores. If the database is pinned, find the query or job that’s pinning it first.
  4. Audit every Realtime subscription. Search your code for .channel( and postgres_changes. Ask whether each one needs to be instant, whether it listens to more than the screen shows, and whether it keeps running in background tabs.
  5. Cut egress at the source. Select only the columns you need, stop insert and update calls returning whole rows, and serve files from storage and its CDN instead of through Edge Functions.
  6. Check your branching settings. If you use the GitHub integration, turn on “Supabase changes only” so branches are created only when database files change, or turn automatic branching off. Delete branches nobody is using.
  7. Delete projects you don’t need. Each running project bills compute every hour, and paid projects can’t be paused. To pause one, move it to a Free organization first.

When Supabase stops being cheap

For a database, sign-in and file storage, Supabase is good value at most sizes. It gets expensive when a usage line grows with users multiplied by activity: live updates fanned out to many listeners, video and large files served without a cache, or a pile of projects and branches each billing by the hour. Those are design problems first. A smaller query or a narrower subscription costs nothing, a bigger compute size costs every hour, and for the one component that won’t fit the pricing, you can run that piece yourself and keep the rest on Supabase.

If your Supabase bill is growing faster than your users, our vibe coding rescue starts by finding which line is driving it.

LET’S TALK.

Book a free 30-minute call with Virgil

Pick a time that suits you. You’ll get a straight answer on what you need, what it should cost and the fastest path to launch.

Loading available times…

Open the calendar in a new tab

Send us your project

Virgil replies personally within one business day.

Book a free strategy call