Supabase Pricing (2026): $25 Covers One Micro Project

Supabase Pro costs $25 a month only when one Micro project stays inside the included quotas. At 150,000 monthly active users the same plan reaches $187.50 before any egress, storage, add-on, or tax, while Team jumps to $599 without raising the core usage allowances.

Supabase is a backend-as-a-service, which bundles a Postgres database, authentication, file storage, Realtime, and Edge Functions behind one account. Its price is not one meter. Your invoice combines an organization plan, compute for every project, usage beyond pooled allowances, optional add-ons, and any applicable tax.

The best default is simple: use Free for an idle-tolerant prototype, Pro for a small production app, and Team only when governance or compliance is worth a $574 monthly premium. Enterprise is a contract, not a self-serve capacity tier.

These numbers were verified against Supabase's live pricing page and billing documentation on August 4, 2026.

Supabase pricing at a glance

Supabase has four plans: Free at $0, Pro from $25 a month, Team from $599 a month, and Enterprise at a custom price. The table is current as of August 4, 2026.

The phrase from $25 matters. Supabase bills once per organization, but every project has its own dedicated Postgres compute instance. Paid plans supply one $10 monthly compute credit, enough to offset one Micro instance. That makes one Pro organization with one Micro project $25 when all other usage stays included.

A second Micro project adds about $10. A Small instance costs about $15 before the credit. The plan and its pooled usage quotas cover every project in the organization, while database disk allowances apply per project.

You cannot mix Free and paid projects inside one organization. A separate Free organization can hold a prototype while a paid organization holds production, but each organization gets its own plan, billing cycle, and invoice.

Who can stay on Supabase Free forever

Supabase Free is enough indefinitely for a low-traffic personal project that fits the limits and can tolerate going to sleep. You never need to pay if the app stays below 50,000 monthly active users, 500 MB of database data per project, 1 GB of stored files, 5 GB of uncached egress, and 5 GB of cached egress.

The project must also fit within 200 peak Realtime connections, 2 million Realtime messages per month, and 500,000 Edge Function invocations per month. Realtime messages can be at most 256 KB, file uploads can be at most 50 MB, and API and database logs remain available for one day. API requests themselves are unlimited.

The Free account limit is two active projects across organizations where you are an Owner or Administrator. A project pauses after one week without activity. Paused projects do not count toward the two-project allowance, but a paused demo is unavailable until it is restored.

Free also omits automatic backups, Point-in-Time Recovery, advanced disk configuration, image transformations, and email support. That is the operational cutoff. A portfolio app with occasional use can live there. A client app, paid product, webhook receiver, or public demo that must always answer should not.

The Free-to-Pro break-even is therefore not a traffic number. Free remains $0 right up to its limit, while Pro starts at $25. The choice flips when inactivity pauses, missing backups, short logs, or support risk cost more than $25 a month.

Self-hosting is another route, but it is not a free managed plan. Supabase says a self-hosted operator owns server provisioning, security hardening, service configuration, Postgres maintenance, high availability, scaling, backups, disaster recovery, monitoring, and uptime. Managed-only features such as branching, managed backups, PITR, analytics, and the platform management API are unavailable in the self-hosted configuration.

Choose self-hosting for control, isolation, or an existing infrastructure team. Do not choose it because the software invoice says $0 while the operating work stays invisible.

What Supabase Pro really costs

Supabase Pro stays at $25 only with one Micro project and included usage. The first cost decision is project compute, not user count.

The monthly compute ladder shown on the live pricing page is Micro $10, Small $15, Medium $60, Large $110, XL $210, 2XL $410, 4XL $960, 8XL $1,870, 12XL $2,800, and 16XL $3,730. Compute is billed hourly, with any partial hour rounded up. The documentation's hourly rate makes Large about $111 over a 730-hour month, while the pricing page displays $110, so treat monthly compute figures as estimates.

Here is how the base arithmetic lands:

• One Micro project: $25 plan + $10 compute - $10 credit = $25/month.
• One Small project: $25 + $15 compute - $10 credit = $30/month.
• Three Micro projects: $25 + $30 compute - $10 credit = $45/month.
• One Medium project: $25 + $60 compute - $10 credit = $75/month.
• One Large project: about $25 + $110 compute - $10 credit = about $125/month using the displayed monthly estimate.

The credit belongs to the organization, not each project. It resets each month and does not accumulate. Five Micro projects do not each receive a free $10 offset.

The MAU cliff

The sharpest Pro cost jump begins after 100,000 monthly active users. Each additional MAU costs $0.00325.

At 150,000 MAU, the bill is $25 + 50,000 x $0.00325 = $187.50 before other overages. That is $1.25 per 1,000 active users across the full audience. At exactly 100,000 MAU, the $25 base is only $0.25 per 1,000. Adding the next 50,000 users increases the total by $162.50.

At 200,000 MAU, Auth alone takes the total to $350. This is why a product expecting consumer-scale login volume should model Auth before launch. The first 100,000 are generous; the marginal 100,000 are not.

Egress, storage, and database growth

Pro includes 250 GB of uncached egress and another 250 GB of cached egress. At 500 GB of uncached egress, the bill is $47.50: $25 plus 250 GB at $0.09. The same 500 GB served as cached egress would total $32.50, because the overage rate is $0.03 per GB.

File storage is cheaper to exceed. Pro includes 100 GB, then charges $0.0213 per GB. A 200 GB storage footprint makes the bill $27.13 before egress. Database disk includes 8 GB per project, then costs $0.125 per GB. A 20 GB database adds $1.50, taking a one-Micro Pro setup to $26.50.

The billing unit decides which line dominates. A photo product can fit comfortably in storage and still pay for delivery. A consumer app can use little disk and generate a large MAU charge. A data-heavy B2B app may stay under Auth and egress limits while compute becomes the expensive line.

Team and Enterprise are governance purchases

Supabase Team costs $599 a month because it adds controls, not because it includes more MAU, storage, egress, or database disk. Those quantitative allowances and their overage rates match Pro.

The $574 gap buys SOC 2 and ISO 27001 access, project-scoped and read-only roles, Dashboard SSO, priority email support and SLAs, 14-day daily-backup retention, and 28-day log retention. HIPAA is available as a paid add-on. Pro gives seven days of backups and logs but does not include those Team governance controls.

There is no usage break-even between Pro and Team. If a Pro app needs more compute, storage, egress, or Auth capacity, buying those meters is generally cheaper than adding $574 for the same allowances. Team wins only when access control, assurance evidence, support response, or retention closes a business requirement.

Team is not billed per seat, and organization members are unlimited on every plan. A useful internal normalization is the governance premium across the people who benefit from it: $599 is $59.90 per person at 10 people, $23.96 at 25, and $11.98 at 50. Those are analytical seat-month figures, not Supabase prices.

Enterprise is quote-only. It adds a designated support manager, uptime SLAs, BYO Cloud support, 24x7x365 premium support, a private Slack channel, and custom security questionnaires. Choose it when the contract, infrastructure arrangement, or support obligation itself is part of the product you are buying.

Every overage and add-on that can move the bill

The Supabase Spend Cap does not cap the whole invoice. With the Pro Spend Cap on, covered usage stops or becomes restricted after the included quota instead of creating an overage. Compute and several explicitly provisioned resources can still bill.

Usage meters

Auth includes 100,000 MAU and 100,000 third-party MAU on Pro and Team, then charges $0.00325 for each additional active user in either category. SAML includes 50 MAU, then charges $0.015 each. Advanced MFA Phone costs $75 a month for the first project and $10 a month for each additional project.

Database disk includes 8 GB per project, then costs $0.125 per GB. Uncached egress includes 250 GB per organization, then costs $0.09 per GB. Cached egress has its own 250 GB allowance and costs $0.03 per GB after it. File storage includes 100 GB, then costs $0.0213 per GB.

Image transformations include 100 origin images, then cost $5 per 1,000. Realtime includes 500 peak concurrent connections, then costs $10 per 1,000, and 5 million messages per month, then $2.50 per million. Edge Functions include 2 million invocations, then cost $2 per million.

Unlimited API requests do not mean an unlimited free application. An API call has no request meter, but it can consume database compute, egress, function invocations, storage transformations, Realtime messages, or Auth allowance. The API price and the workload price are different layers.

Project and platform add-ons

Database branches cost $0.01344 per branch-hour. Pipelines cost $0.053 per hour, plus $3.00 per GB processed during ongoing replication and $0.60 per GB during initial sync.

A custom domain costs $10 per project per month. Point-in-Time Recovery costs $100 a month for each seven days of retention. Pro plus PITR is therefore $125 before other usage. Add one custom domain and the same setup becomes $135.

Log Drains cost $60 per drain per project per month, plus $0.20 per million events and $0.09 per GB of egress. This is three meters for one add-on, which matters when a compliance requirement sends high-volume logs elsewhere.

Advanced disk

General Purpose disk can scale to 16 TB. It includes 8 GB, 3,000 IOPS, and 125 MB/s throughput; overage costs $0.125 per GB, $0.024 per IOPS, and $0.095 per MB/s. Its stated durability is 99.9%.

High Performance disk can scale to 60 TB and charges from the first unit: $0.195 per GB and $0.119 per IOPS, with throughput scaling alongside IOPS. Its stated durability is 99.999%.

What the Spend Cap excludes

Supabase lists compute, branching compute, read-replica compute, custom domains, added disk IOPS and throughput, IPv4, Log Drain hours and events, Advanced MFA Phone, and PITR outside the Spend Cap. These are predictable or explicitly enabled resources, so the platform lets them bill even when covered usage is capped.

The current Spend Cap also lacks per-item budgets. You cannot set one ceiling for Auth and another for egress. The safe sequence is to leave it on, measure the usage mix, calculate each marginal rate, and turn it off only when restricting the service would be worse than paying the forecast overage.

Billing traps: credits, annual plans, refunds, and tax

Supabase has two kinds of credit with opposite expiry behavior. The $10 compute credit included with a paid plan resets monthly and never accumulates. Purchased account credits do not expire, but they are non-refundable.

Self-serve credit top-ups can be as large as $2,000. They apply to future invoices and cannot settle an already outstanding invoice. A larger package requires contacting Supabase.

There is no official annual plan and no published annual discount. Supabase suggests topping up credits if you want fewer monthly card payments. That avoids a formal 12-month subscription, but the prepaid balance is non-refundable. Paying ahead changes cash flow, not the plan rate.

The subscription fee is charged upfront at the beginning of the monthly billing cycle. Compute and usage charges are billed in arrears. A plan change can therefore produce both a new subscription treatment and a final charge for usage already incurred.

Cancellation does not normally return cash. Supabase converts unused subscription time into credits that do not expire and can be used later. It may still charge unbilled excess usage from the previous cycle. If the wrong organization was upgraded, support can transfer the amount as credit to another organization.

Tax is now another possible line. Supabase says sales tax, VAT, GST, and other indirect taxes may be added according to the billing address and local rules. Its international tax rollout ran from May 1 through June 30, 2026. A $25 plan can therefore charge more than $25 even with no metered overage or add-on.

No separate student discount is advertised on the live pricing or billing pages as of August 4, 2026. Students use the same Free plan. An old 2021 pricing post discussed supporting students and schools with Free projects and possible credits, but that page is now marked out of date and is not a current public discount program.

Supabase vs Firebase, Neon, and Appwrite on price

The cheapest alternative depends on which part of Supabase you need. Firebase meters database operations, Neon meters Postgres compute and storage, and Appwrite sells another bundled backend. Their prices become comparable only after defining a workload.

Firebase: cheaper for light operations, harder to forecast

Firebase has a $0 Spark plan and a Blaze plan with no fixed subscription price. Blaze is pay as you go and keeps the no-cost allowances.

Firestore Standard includes 1 GiB stored, 50,000 document reads per day, 20,000 writes per day, 20,000 deletes per day, and 10 GiB of outbound transfer per month. The displayed default rates after those quotas are $0.03 per 100,000 reads, $0.09 per 100,000 writes, and $0.01 per 100,000 deletes.

At 1 million reads and 100,000 writes every day for a 30-day month, reads cost $8.55 and writes cost $2.16 after their daily free quotas. That is $10.71, before storage, egress, Auth, Functions, or another Google Cloud product.

Reads alone reach the Supabase $25 base at about 84.83 million reads per 30-day month, including Firestore's 1.5 million free monthly reads. That is not a database-performance equivalence. It is the billing point where one Firebase meter matches the entire Supabase Pro base.

Choose Firebase when the workload is light, its document model fits, and per-operation cost is easy to control. Skip it when many small reads make the bill hard to forecast or when you want one flat backend floor. The deeper product decision is covered in Supabase vs Firebase.

Neon: cheaper for an intermittent database

Neon is a serverless Postgres platform whose paid plans have no monthly minimum. Launch charges $0.106 per CU-hour, where a Compute Unit represents roughly one vCPU and 4 GB of RAM, plus $0.35 per GB-month of storage.

An intermittent database using 140 CU-hours and 1 GB costs $15.19 on Launch. A low-load, always-on database using 187.5 CU-hours and 5 GB costs $21.62. At 5 GB, Neon reaches the $25 Supabase base around 219.34 CU-hours.

Neon Free is also broad for database-only work: 100 projects, 100 CU-hours per project each month, and 0.5 GB storage per project. Paid plans meter from zero, so those free allowances do not carry over after upgrading.

Choose Neon when you mainly need Postgres and scale-to-zero economics. Supabase earns its higher floor when the bundled Auth, Storage, Realtime, Functions, and one steady Micro instance replace services you would otherwise assemble. Neon now lists backend features including managed Auth, Object Storage, and Functions, but some are in beta, so compare production maturity and scope alongside the database bill.

Appwrite: the strongest $25 allowance for high MAU and bandwidth

Appwrite Pro also starts at $25 a month, but its current included allowances are larger on two expensive axes: 200,000 MAU and 2 TB of bandwidth. It also includes 150 GB storage, 3.5 million function executions, unlimited organization members, and seven days of daily backups.

At 150,000 MAU, Appwrite remains $25 if other usage stays included, while Supabase reaches $187.50 from Auth overage alone. At 250,000 MAU, Appwrite is $175: $25 plus 50 blocks of 1,000 extra users at $3. Supabase would be $512.50 at the same MAU before other usage.

Appwrite charges $15 for each additional project, $15 per 100 GB of extra bandwidth, $2.80 per 100 GB of extra storage, and $2 per million extra function executions. Its Free plan pauses after one inactive week and limits an account to two projects, much like Supabase Free.

Choose Appwrite for a bundled backend when MAU or bandwidth dominates and its platform model fits the app. Choose Supabase when Postgres compatibility, its ecosystem, or its specific database and security model is the priority. The cost difference is large enough that a consumer app should price both before selecting the backend.

The alternative decision rule is direct:

• Pick Firebase for a light operation-metered app where the free quotas absorb most traffic.
• Pick Neon for database-first workloads that idle enough to benefit from scale to zero.
• Pick Appwrite when a $25 bundled backend needs 200,000 MAU or heavy included bandwidth.
• Pick Supabase when one predictable Postgres-backed production project and the bundled services matter more than the lowest single meter.

Builders that generate application code around these backends are compared in the best AI app builders. The backend bill should be modeled separately from the builder subscription.

Which Supabase plan should you choose?

Choose Free when the app is a prototype, learning project, or personal tool that can pause and can be recreated without managed backups. A quiet public demo with an uptime expectation already fails this test.

Choose Pro for production when one Micro or Small project is enough, 100,000 MAU and 250 GB egress leave headroom, and seven-day backups and logs are sufficient. Keep the Spend Cap on until the first traffic model is complete.

Choose Team when a buyer, auditor, or internal security policy requires its roles, certifications, Dashboard SSO, longer retention, or support SLA. Do not upgrade for traffic alone.

Choose Enterprise when uptime commitments, BYO Cloud, dedicated support, private coordination, or custom security review must be written into a contract.

1. 1

   Model the base and every active project

   Start with the organization plan. Add the hourly compute for every project, then subtract only one $10 monthly compute credit.

2. 2

   Price the first threshold you expect to cross

   Calculate MAU, uncached egress, cached egress, database disk, file storage, Realtime, and Function usage against their separate allowances. Do not average them into one vague growth estimate.

3. 3

   List add-ons outside the Spend Cap

   Add PITR, custom domains, extra IOPS, Log Drains, MFA Phone, branches, replicas, and any larger compute. These can bill even while covered overage is capped.

4. 4

   Choose restriction or overage deliberately

   Leave the Pro Spend Cap on during early production. Disable it only when the cost model is approved and service continuity is worth the marginal rates.

Supabase pricing FAQ

How much is Supabase per month?

Supabase Free is $0, Pro starts at $25 a month, Team starts at $599, and Enterprise is custom. One Pro organization with one Micro project can remain $25 because the paid plan includes a $10 compute credit. More projects, larger compute, overages, add-ons, and applicable tax increase the total.

Is Supabase 100% free?

Managed Supabase is free inside the Free limits: two active projects, 50,000 MAU, 500 MB database per project, 1 GB storage, and 5 GB egress, with projects paused after one inactive week. Self-hosted Supabase removes the managed subscription but makes you responsible for servers, security, Postgres operations, backups, monitoring, scaling, and recovery.

Is Supabase cheaper than AWS?

There is no universal answer because Supabase bundles several backend services while AWS prices separate infrastructure and managed products. Supabase is easier to budget for one small production app at $25. AWS can win when a team already operates the stack efficiently or needs a narrower resource, but labor, backups, networking, and support must be included for a fair comparison.

Can I self-host Supabase?

Yes. Supabase recommends Docker for self-hosting, but the self-hosted configuration represents one project and omits managed-platform features such as branching, managed backups, PITR, analytics, and the platform management API. It is a control decision, not a free equivalent of the hosted platform.

Does Supabase offer annual pricing?

No official annual plan is available as of August 4, 2026. You can top up account credits to reduce payment frequency, but that does not create an annual discount and purchased credits are non-refundable.

Does Supabase have a student discount?

Supabase does not advertise a separate student discount on its current pricing or billing pages. Students can use the same $0 Free plan. An older 2021 post discussed student support and possible credits, but Supabase now marks that page out of date.

What is the Supabase refund policy?

When you cancel, unused subscription time becomes account credit that does not expire, and previous unbilled usage can still be charged. Supabase says unused credits are not refundable. A mistaken upgrade can be handled through support as a credit transfer to another organization.

Did Supabase pricing change?

Yes. Supabase launched Pro at $25 per project in 2021. It announced organization-based billing on August 31, 2023 and began rolling it out on September 4, 2023. Pro is now $25 per organization, with one Micro instance offset by the compute credit and additional project compute billed separately.

Get the AI Business Workflow Audit Checklist and the operator newsletter.