# Supabase pricing in 2026: Free, Pro and compute costs > Supabase Free is 2 projects with a 500 MB database each. Pro is $25 a month on Micro compute; bigger databases cost $10 to $960 more. Calculator inside. Published 2026-10-02, updated 2026-11-14, by Nick Potts. For agents: [llms.txt](https://ployz.dev/llms.txt) indexes the Ployz docs as Markdown. **TL;DR:** Supabase is free for 2 small projects, then **$25 a month** on Pro for one project on the 1 GB Micro compute. Past Micro, the compute add-on is the bill: a dedicated 8 GB database is about $160 a month with typical disk and egress, and a 32 GB one with 2 TB of egress is about $757. - **Free:** $0 for 2 active projects, each with a 500 MB database and unlimited API requests. File storage is a separate 1 GB, and you get 5 GB of egress and 50,000 monthly active users. Projects pause after a week without activity, and there are no backups. - **Pro:** $25 a month, including $10 of compute credit, 8 GB of disk per project, 100 GB of file storage, 250 GB of egress and 100,000 monthly active users. - **Compute:** billed hourly per project, from $0.01344 an hour for Micro (about $10 a month) to $1.32 for 4XL (about $960). Small to Medium is 4x the price for 2x the RAM. - **Overages:** disk at $0.125 per GB, egress at $0.09 per GB, $0.00325 per user past 100,000, and point-in-time recovery at $100 a month. - **Stay on Supabase if** you use Auth, Storage or Realtime heavily, or you fit on Micro or Small. **Move Postgres to your own server if** you use Supabase mostly as a database on Medium compute or bigger: the same RAM costs $51 instead of $160. - **Pick Ployz if** your coding agent runs that server and you want one-click Postgres next to your app, with a restore point and approval for anything risky. Supabase is a hosted backend built on Postgres: a managed database plus Auth, Storage, Realtime, Edge Functions and an auto-generated REST API. You pay a plan fee per organization, then compute per project, plus disk, egress and monthly active users beyond what the plan includes. ## How much does Supabase cost per month? Supabase has four plans: Free at $0, Pro from $25 a month, Team from $599 a month and Enterprise at a custom price ([Supabase pricing](https://supabase.com/pricing)). The plan fee is per organization. Compute is per project, and for a database-heavy app it is where the money goes. | | Free | Pro | Team | |---|---|---|---| | Price | $0 | from $25/mo | from $599/mo | | Projects | 2 active | each pays its own compute | each pays its own compute | | Compute | Nano (shared CPU, 0.5 GB RAM) | $10 credit, one Micro | $10 credit, one Micro | | Database | 500 MB per project | 8 GB disk per project, then $0.125/GB | same as Pro | | File storage | 1 GB | 100 GB, then $0.0213/GB | same as Pro | | Egress | 5 GB | 250 GB, then $0.09/GB | same as Pro | | Monthly active users | 50,000 | 100,000, then $0.00325 each | same as Pro | | Daily backups | none | 7 days | 14 days | | Log retention | 1 day | 7 days | 28 days | | Pauses when idle | after 1 week | never | never | Enterprise is custom on every line. Sources: [pricing page](https://supabase.com/pricing), [billing docs](https://supabase.com/docs/guides/platform/billing-on-supabase), [compute and disk](https://supabase.com/docs/guides/platform/compute-and-disk), [backups](https://supabase.com/docs/guides/platform/backups). Which plan you need: Free for a project you don't mind pausing, Pro for anything people rely on, and Team only when a customer's security review asks for SOC 2 or SSO. ## What would your Supabase bill be? Pick the app closest to yours for a Supabase Pro bill, a Free plan check and the same database on a Hetzner server. Customize sets compute, database size, egress, users and point-in-time recovery. If your database is too big for the compute you pick, the bill moves up to the smallest size Supabase recommends for it. *The interactive calculator is on the web page: https://ployz.dev/blog/supabase-pricing* ## What do you get on the Supabase free plan? The Free plan gives you 2 active projects, and each one gets a **500 MB database** on Nano compute (shared CPU, 0.5 GB RAM). File storage is separate: 1 GB for the plan, for things like uploads and images in Supabase Storage, which don't count against the 500 MB ([pricing page](https://supabase.com/pricing)). - **Database over 500 MB:** the project goes read-only until you delete data or upgrade ([database size docs](https://supabase.com/docs/guides/platform/database-size)). The 500 MB counts tables, indexes and Supabase's own `auth` schema. - **Two projects per person.** The limit counts every organization where you're an owner or admin, so a second organization doesn't buy a third project. Paused projects don't count ([billing docs](https://supabase.com/docs/guides/platform/billing-on-supabase)). - **Pausing:** a project with too little database activity for a week pauses, and your API stops answering until you restore it from the dashboard ([pausing docs](https://supabase.com/docs/guides/platform/free-project-pausing)). - **No backups.** Supabase tells Free projects to export their own data with `supabase db dump` ([backup docs](https://supabase.com/docs/guides/platform/backups)). I cover the limits, the pause and how to stay under them in [Is Supabase free?](https://ployz.dev/blog/is-supabase-free). ## What does Supabase cost for a small, medium and large app? The three presets above, line by line. Small is a side project on Micro. Medium is a busy SaaS on a dedicated 8 GB database. Large is a 100 GB database on 2XL with real traffic. Supabase wins the small one. From medium up, a Hetzner server with the same RAM costs a third or less, before counting the work you take on. **Small: 5 GB database, Micro, 50 GB egress, 10,000 MAU** | Line | Supabase Pro | Hetzner CX23 (2 vCPU, 4 GB, 40 GB) | |---|---|---| | Plan or server | $25.00 | $6.49 | | Compute (Micro $10 minus $10 credit) | $0.00 | included | | Disk, egress, MAU | $0.00 (inside quotas) | included | | IPv4 | n/a | $0.60 | | **Total** | **$25.00** | **$7.09** | **Medium: 40 GB database, Large, 600 GB egress, 80,000 MAU** | Line | Supabase Pro | Hetzner CCX13 (2 dedicated vCPU, 8 GB, 80 GB) | |---|---|---| | Plan or server | $25.00 | $50.49 | | Compute (Large $110 minus $10 credit) | $100.00 | included | | Disk (32 GB over at $0.125) | $4.00 | included | | Egress (350 GB over at $0.09) | $31.50 | included | | IPv4 | n/a | $0.60 | | **Total** | **$160.50** | **$51.09** | | With 7-day PITR | $260.50 | n/a (see backups below) | **Large: 100 GB database, 2XL, 2,000 GB egress, 150,000 MAU** | Line | Supabase Pro | Hetzner CCX33 (8 dedicated vCPU, 32 GB, 240 GB) | |---|---|---| | Plan or server | $25.00 | $162.99 | | Compute (2XL $410 minus $10 credit) | $400.00 | included | | Disk (92 GB over at $0.125) | $11.50 | included | | Egress (1,750 GB over at $0.09) | $157.50 | included | | MAU (50,000 over at $0.00325) | $162.50 | $0 (auth in your app) | | IPv4 | n/a | $0.60 | | **Total** | **$756.50** | **$163.59** | | With 7-day PITR | $856.50 | n/a | Hetzner prices are from the [15 June 2026 price adjustment](https://docs.hetzner.com/general/infrastructure-and-availability/price-adjustment/) (Germany and Finland, USD, excluding VAT) plus [IPv4 pricing](https://docs.hetzner.com/cloud/servers/primary-ips/overview/). Included traffic is 20 TB on CCX13 and 30 TB on CCX33 in the EU ([Hetzner General Purpose](https://www.hetzner.com/cloud/general-purpose)). I matched RAM and dedicated cores, which is generous to Supabase. A shared Hetzner CX43 with 16 GB of RAM is $18.49 and would run the medium database fine for most apps. For the large one, a dedicated server like the €80 box I run everything on beats any cloud server. Netcup is often the better deal for the small case, and it has a US datacenter in Manassas: | Server | Specs | Price/month | Source | |---|---|---|---| | Netcup VPS 500 | 2 vCPU, 4 GB RAM, 64 GB SSD, traffic included | €8.26 incl. VAT, 12-month term | [netcup VPS plans](https://www.netcup.com/en/server/vps) | ## What does the Supabase Pro plan include? Pro is $25 a month and includes $10 of compute credits, which pays for one project on Micro (1 GB RAM, shared CPU). Projects on Pro never pause ([Supabase pricing](https://supabase.com/pricing)). | Pro plan item | Included | Then | |---|---|---| | Compute | $10 credit (one Micro) | see the compute table | | Disk | 8 GB per project | $0.125 per GB | | Egress | 250 GB | $0.09 per GB | | Cached egress | 250 GB | $0.03 per GB | | Monthly active users | 100,000 | $0.00325 per MAU | | File storage | 100 GB | $0.0213 per GB | | Edge Function invocations | 2 million | $2 per million | | Realtime messages | 5 million | $2.50 per million | | Realtime peak connections | 500 | $10 per 1,000 | | Log ingestion | 20 GB | $0.50 per GB | | Daily backups | 7 days | n/a | | Point-in-time recovery | not included | $100/mo per 7 days of retention | | Custom domain | not included | $10/mo per domain, per project | | Branching | not included | $0.01344 per branch per hour | Sources: [pricing page](https://supabase.com/pricing), [disk](https://supabase.com/docs/guides/platform/manage-your-usage/disk-size), [egress](https://supabase.com/docs/guides/platform/manage-your-usage/egress), [MAU](https://supabase.com/docs/guides/platform/manage-your-usage/monthly-active-users). Spend caps are on by default on Pro. With the cap on, you can't go past the included quotas. Turn it off and every overage above starts billing. Point-in-time recovery is billed even with the cap on ([PITR docs](https://supabase.com/docs/guides/platform/manage-your-usage/point-in-time-recovery)). Logs are the newest line. Supabase moved logs to metered pricing in mid-2026, and on 25 September 2026 it said usage is visible but limits aren't enforced until "early 2027" ([changelog](https://supabase.com/changelog/logs-usage-based-pricing)). The pricing page now lists 1 GB of ingestion on Free and 20 GB on Pro, which is more than the 5 GB the [June update](https://supabase.com/changelog/46689-developer-update-june-2026) announced. ## What do the Supabase Team and Enterprise plans add? Team starts at **$599 a month** and has Pro's quotas and overage prices. What the extra money buys is compliance and access control for the organization ([Supabase pricing](https://supabase.com/pricing)). | | Team | Enterprise | |---|---|---| | Price | from $599/mo | custom | | SOC 2 and ISO 27001 | included | included | | HIPAA | paid add-on | paid add-on | | SSO for the dashboard | listed in the plan, "Contact Us" in the comparison table | contact sales | | Uptime SLA | not included | included | | Support | priority email | 24/7, with a designated support manager and a private Slack channel | | Daily backups | 14 days | custom | | Log retention | 28 days | 90 days | | Roles | Owner, Admin, Developer, Read-only, project-scoped | custom project-scoped roles | | AWS PrivateLink | "Included" in the comparison table | included | Some summaries say Team comes with a 99.9% uptime SLA. Supabase's pricing page lists uptime SLAs as not included on Team and doesn't give a percentage for Enterprise. Team makes sense when a customer's security review asks for SOC 2 or SSO, not because your app outgrew Pro. ## How much do Supabase compute add-ons cost? Compute runs from **$0.01344 an hour** for Micro, about $10 a month, to $5.12 an hour for 16XL, about $3,730 ([compute and disk docs](https://supabase.com/docs/guides/platform/compute-and-disk)). It's billed for every hour a project runs, and a partial hour counts as a full one ([compute billing](https://supabase.com/docs/guides/platform/manage-your-usage/compute)). The $10 credit comes off the compute total, so on Pro a Small costs $5 extra and a Large $100 extra. | Size | CPU | RAM | Max DB size | Per hour | Per month | |---|---|---|---|---|---| | Nano (Free only) | shared | 0.5 GB | 500 MB | $0 | $0 | | Micro | shared | 1 GB | 10 GB | $0.01344 | ~$10 | | Small | shared | 2 GB | 50 GB | $0.0206 | ~$15 | | Medium | shared | 4 GB | 100 GB | $0.0822 | ~$60 | | Large | 2 dedicated vCPUs | 8 GB | 200 GB | $0.1517 | ~$110 | | XL | 4 dedicated vCPUs | 16 GB | 500 GB | $0.2877 | ~$210 | | 2XL | 8 dedicated vCPUs | 32 GB | 1 TB | $0.562 | ~$410 | | 4XL | 16 dedicated vCPUs | 64 GB | 2 TB | $1.32 | ~$960 | | 8XL | 32 dedicated vCPUs | 128 GB | 4 TB | $2.562 | ~$1,870 | | 12XL | 48 dedicated vCPUs | 192 GB | 6 TB | $3.836 | ~$2,800 | | 16XL | 64 dedicated vCPUs | 256 GB | 10 TB | $5.12 | ~$3,730 | Every size has a recommended maximum database size, so a growing database pushes you up the table even if your traffic doesn't. The jump from Small to Medium hurts most: four times the price ($15 to $60) for twice the RAM, still on a shared CPU. Large is the first size with dedicated cores. Each extra project gets its own compute, so a staging project on Micro adds $10 a month. Supabase's own example is three Small projects for a month: $25 plus $45 of compute minus the $10 credit, **$60** ([compute billing](https://supabase.com/docs/guides/platform/manage-your-usage/compute)). A paused project costs nothing. ## Why is my Supabase bill higher than $25? Usually one of five things: - **You moved off Micro.** Any bigger compute size is billed on top of the $25. - **Your disk grew past 8 GB.** Disk is billed on provisioned size, not used size ([disk docs](https://supabase.com/docs/guides/platform/manage-your-usage/disk-size)). On Pro it grows by 50% automatically when it hits 90% full ([database size docs](https://supabase.com/docs/guides/platform/database-size)), so you pay for headroom. - **Egress passed 250 GB.** Every row your API returns counts, alongside auth, storage, realtime, Edge Functions and the connection pooler ([egress docs](https://supabase.com/docs/guides/platform/manage-your-usage/egress)). A chatty API with big JSON payloads burns through 250 GB fast. - **You have more than one project.** Each one pays its own compute. - **You turned on point-in-time recovery.** It costs $100 a month for 7 days, $200 for 14 and $400 for 28, and needs at least Small compute ([PITR docs](https://supabase.com/docs/guides/platform/manage-your-usage/point-in-time-recovery), [backup docs](https://supabase.com/docs/guides/platform/backups)). ## What do you give up by moving Postgres off Supabase? Everything Supabase runs around Postgres. Auth, Storage, Realtime, Edge Functions and the REST API all live next to your database, and Auth keeps its users in the same Postgres. The list I'd check before moving: - **Auth.** If you use Supabase Auth, you need a replacement such as Better Auth or Auth.js in your app, and a migration for existing users. Row Level Security policies that call `auth.uid()` need rewriting. - **Data access through supabase-js.** Calls like `supabase.from("posts").select()` go through Supabase's REST API. Without it, you query Postgres from your server with an ORM or SQL. - **Storage and Realtime.** Files move to S3-compatible object storage. Realtime needs its own replacement, or polling. - **Backups.** Supabase takes daily backups for you. On your own server, a copy off the box is your job. See below. - **Upgrades and disk.** You decide when to upgrade Postgres, and Ployz charts disk use for every server. A full disk stops writes on your server the same way it does on Supabase. If you use Supabase only as a Postgres URL with an ORM in front, most of this list doesn't apply. ## How do you back up Postgres on your own server? Keep a copy off the server, so a dead server doesn't take the database and its backup together. A nightly `pg_dump` copied to a second cheap server or to object storage is enough for most small apps. With Ployz, the database also gets a restore point on its own server, for the bad migration or the table your coding agent dropped, and deleting the database volume waits for you. Keep the nightly dump for the dead server. A server disk snapshot (Hetzner charges 20% of the server price, per its [billing FAQ](https://docs.hetzner.com/cloud/billing/faq/)) is a nice extra, but a snapshot of a running Postgres isn't a clean copy of the database. ## How do you move a database from Supabase to your own server? 1. Take a `pg_dump` from Supabase using the direct connection string in the dashboard. If you only use the `public` schema, dump only that one with `--schema=public`. The `auth` and `storage` schemas belong to Supabase's services and won't do anything on a plain Postgres. 2. Restore it into Postgres on your server with `pg_restore`. 3. Point your app at the new URL. 4. Keep the Supabase project for a week before deleting it. For a small database that's minutes. For a busy one, plan a short maintenance window so no writes land on Supabase after the dump. ## Which should you pick? **Stay on Supabase if:** - Your project fits Pro on Micro or Small and the bill is $25 to $40. - You use Supabase Auth, Storage or Realtime heavily and don't want to replace them. - Nobody on the team wants to own Postgres upgrades. - You need point-in-time recovery. **Move Postgres to your own server if:** - You're on Medium compute or bigger and use Supabase mostly as a database. - Egress or MAU overages are a big line on the bill. - You already run your app on a server, so the database can sit next to it on a private network. I think Supabase is worth it while you use what it bundles and fit on Micro or Small. It stops being worth it when the compute add-on is most of the bill, because then you pay $100 to $400 a month for RAM that costs $50 to $160 on a server you rent. ## Where Ployz fits I learned this on Railway, where I paid over $500 a month, mostly for one busy database. Today one €80 dedicated server runs everything I have, and I build Ployz to make that move easy. Your coding agent runs it. Paste one line into Claude Code, Codex or Cursor and it [deploys your app](https://ployz.dev/blog/claude-code-deploy) to your server. ```sh ployz up --server root@your-server ``` Postgres is one click next to your app, with a restore point. Restore your Supabase dump into it and point your app at the new URL. Every deploy, restart or delete your agent asks for waits for you to approve. Ployz is free on any number of servers. [Deploy to your own server](https://ployz.dev/auth/github). ## FAQ ### Is Supabase 100% free? The Free plan is $0, but it is limited: 2 active projects, a 500 MB database each, 1 GB of file storage, 5 GB of egress and 50,000 monthly active users. Projects pause after a week idle and have no backups, so most production apps end up on Pro at $25. ### What is the Supabase free plan storage limit? 500 MB of database per project and 1 GB of file storage. They are separate quotas: rows and indexes count against the 500 MB, and files in Supabase Storage count against the 1 GB. ### What is $0.00325 on Supabase's pricing page? It's the price per monthly active user past the 100,000 included on Pro and Team. 10,000 extra users cost $32.50 a month. It isn't a compute rate: Micro compute is $0.01344 an hour. ### Is Supabase expensive? Not at the start: $25 a month covers a small production app. It gets expensive when your database outgrows Small compute, because Medium is $60 and Large $110 per project on top of the plan, and egress past 250 GB adds $90 per extra TB. ### What are the downsides of Supabase pricing? Compute steps up in big jumps, every project pays its own compute, egress counts API responses as well as files, and point-in-time recovery costs $100 a month or more. On Free, the weekly pause and the lack of backups rule it out for anything people rely on. ### What are the pros and cons of Supabase? The main pro is that one $25 plan bundles Postgres, Auth, Storage, Realtime, Edge Functions and an API that you'd otherwise build or buy separately. The main cons are price jumps on compute, egress that counts every API response, and lock-in once your app depends on Supabase Auth and supabase-js. ### Is Supabase cheaper than AWS? For a small database they land close, and Supabase includes Auth, Storage and an API that AWS bills separately. I compare it with RDS, Neon and others line by line in Postgres hosting. ### Which is better than Supabase? It depends on what you use. For serverless Postgres that scales to zero, see [Neon vs Supabase](https://ployz.dev/blog/neon-vs-supabase). If you use it mostly as a Postgres database, Postgres on your own server costs a third or less from Medium compute up. ### Does Supabase charge per project? The plan fee is per organization, but compute is per project. A second project on Micro adds $10 a month on Pro. ### Is Supabase cheaper than running Postgres myself? On Micro, about the same once you count your time: $25 against a $7 server. From Medium compute up, a server with the same RAM costs a third or less. ### How much is Supabase point-in-time recovery? $100 a month for 7 days of retention, $200 for 14 and $400 for 28. It needs at least Small compute. ## How I checked I checked every Supabase price on 5 October 2026, and the Team and Enterprise features on 7 October 2026, on Supabase's own pricing page and docs, linked next to each number. Hetzner server prices come from its 15 June 2026 price adjustment, checked the same day, and Netcup's from its own plan page. I couldn't confirm Hetzner's object storage price, so the calculator leaves file storage out of the server column. The three bills are my own examples, not real customer bills. Have your coding agent run Postgres next to your app on your own server with Ployz. [Get started](https://ployz.dev/auth/github).