Supabase pricing explained: plans, compute and add-ons
Kofi Agyem, Founder and CEO, CloudzyroPublished · 5 min read
On this page
How Supabase's pricing works: the Free, Pro, Team and Enterprise plans, compute sizes and credits, usage charges and add-ons, with worked monthly examples.
1. Supabase's plans at a glance
Supabase charges a plan fee per organization, then a compute price for each project, plus usage beyond what the plan includes. Figures from Supabase's pricing page and docs, checked on November 1, 2026.
- Free: $0. 500 MB database, shared CPU with 500 MB of memory, 50,000 monthly active users, 5 GB of egress, 1 GB of file storage. Up to 2 active projects, paused after a week of inactivity.
- Pro: from $25 a month, with the first project included and $10 a month of compute credits.
- Team: from $599 a month, adding SOC 2, ISO 27001, SSO for the dashboard and longer backups.
- Enterprise: custom pricing.
Every plan includes unlimited API requests and unlimited team members.
2. What the Free plan includes
The Free plan is a real Postgres database with the rest of Supabase around it, not a trial. Each month it includes:
- 500 MB of database per project and 1 GB of file storage, with uploads up to 50 MB
- 50,000 monthly active users for sign-in
- 5 GB of egress and 5 GB of cached egress
- 500,000 Edge Function invocations
- 2 million Realtime messages and 200 connections at once
- 1 day of API and database logs, and community support
There are no automatic backups, point-in-time recovery or branching on Free, and a project pauses after a week without activity.
3. What Pro includes
Pro is where most production apps start. Each month it includes the following, with the price beyond it:
- 100,000 monthly active users, then $0.00325 per user
- 8 GB of disk per project, then $0.125 per GB
- 250 GB of egress, then $0.09 per GB
- 250 GB of cached egress, then $0.03 per GB
- 100 GB of file storage, then $0.0213 per GB
- 2 million Edge Function invocations, then $2 per million
- 5 million Realtime messages, then $2.50 per million
- Daily backups kept for 7 days, and email support
Team includes the same usage, with backups kept for 14 days, 28-day log retention and priority support.
4. How compute is billed
Each project runs its own Postgres server, and you pick its size. Compute is billed by the hour, and you can resize at any time. Paid plans include $10 a month of compute credits, which cover one Micro instance or come off a bigger one. Monthly prices:
- Micro: $10, 1 GB of memory, shared CPU
- Small: $15, 2 GB, shared CPU
- Medium: $60, 4 GB, shared CPU
- Large: $110, 8 GB, 2 dedicated vCPUs
- XL: $210, 16 GB, 4 dedicated vCPUs
- 2XL: $410, 32 GB, 8 dedicated vCPUs
- Up to 16XL: $3,730, 256 GB, 64 dedicated vCPUs
Bigger instances also allow more connections: a Micro takes 60 direct and 200 pooled connections, a Large 160 and 800.
5. Add-ons that change the bill
- IPv4 address: $0.0055 an hour, about $4 a month per database, on Pro and above. Not covered by the spend cap.
- Point-in-time recovery: $100 a month per 7 days of retention.
- Custom domain: $10 per domain a month, per project.
- Branching: $0.01344 per branch, per hour.
- Log drains: $60 per drain a month, plus usage.
6. What Team and Enterprise add
Team keeps Pro's usage allowances and adds SOC 2 and ISO 27001, project-scoped and read-only roles, SSO for the dashboard, platform audit logs, AWS PrivateLink, 14 days of backups, 28 days of logs and priority support with SLAs. HIPAA is a paid add-on.
Enterprise adds uptime SLAs, a technical account manager, 24/7 premium support, a private Slack channel and custom security questionnaires, at a price agreed with Supabase.
7. Worked examples
- A side project: Free, $0, as long as you use it at least once a week so it doesn't pause.
- One production app: Pro at $25, with the Micro instance covered by the compute credits. $25 a month.
- Two production apps: $25 for Pro, plus $10 for the second project's Micro. $35 a month.
- One app on a Small instance: $25 plus $15 of compute, minus the $10 credit. $30 a month.
- A busy month: 400 GB of uncached egress on Pro is 150 GB over the included 250 GB, which adds $13.50, once the spend cap is off.
8. Limits worth knowing
- Free projects pause after a week without activity, and you can only have 2 active.
- With the spend cap on, going past Pro's included usage limits your project instead of charging you. Check that's what you want for a live app.
- Supabase's direct database connection uses IPv6. Networks that only speak IPv4 need the shared pooler, the client libraries or the paid IPv4 add-on.
9. How to keep your Supabase bill down
- Start on Micro and resize only when the dashboard shows you need to. The credit covers it.
- Serve files through the cache where you can: cached egress is a third of the price of uncached.
- Use the shared pooler instead of the IPv4 add-on if your host can't reach IPv6.
- Delete branches and projects you aren't using, since compute is billed by the hour.
10. Where Cloudzyro fits
Supabase runs your database; Cloudzyro hosts the site or app that uses it. On your site's Database tab, Connect Supabase links a project in one click and fills in the settings your code expects. Cloudzyro sites connect over IPv4, so they use Supabase's pooler, and a pasted direct connection string is switched to it for you. You don't need the IPv4 add-on for that. Hosting is a flat price per site: Launch is free, Boost is $20 a month. See Connect Supabase.