Supabase Pricing for SaaS: A Cost Worksheet for Your App

Supabase Pro starts at $25 per month per organization. Your bill also accounts for project compute, usage beyond included allowances, and any add-ons you enable. Supabase pricing.

This worksheet focuses on Pro, with prices checked on October 20, 2026. All amounts are in US dollars before taxes. The examples use explicitly chosen workloads and published rates; they are calculations, not customer bills or promises about what a given server can handle.

Start with your projects

Supabase bills at the organization level. Projects in the same organization share its subscription plan, and most included usage allowances apply across the organization. Each project still has its own database compute cost. An extra staging project therefore belongs in your budget even if nobody is using it. How Supabase billing works.

List production, staging and any other always-running projects before entering a user count. If you create a separate Supabase project for every customer, calculate the compute for every one of them. A workspace in your SaaS does not inherently need its own Supabase project; that is an architecture decision you make based on isolation requirements and operating costs.

For a standard Pro organization, the worksheet is:

Monthly subtotal =
  $25 plan fee
  + max(0, eligible project compute - $10 compute credit)
  + usage overages
  + other compute and add-ons

The $10 credit applies once per organization each month. It does not become an extra discount on storage or other charges when you use less compute.

Use hourly rates for compute

Supabase charges for running compute by the hour and rounds a partial hour up. These are the published rates for three common sizes:

Multiply each project's running hours by its rate, add those amounts, then apply the organization's credit. Supabase compute pricing.

Choose the size through measurement. Two applications with the same number of active users can have very different query patterns, connection counts and memory requirements. User count alone cannot tell you which instance you need.

Fill in the usage worksheet

Copy this table into your planning document. For an existing app, fill the input column from the Supabase usage dashboard. For a new app, label the inputs as assumptions and replace them with measurements after launch.

Rates and measurement rules: MAUs, egress, file storage, database disk, Edge Functions and Realtime messages.

Use the following formulas for a full Pro billing cycle. max(0, x) prevents a negative charge. ceil(x) rounds up to the next whole number.

MAU overage       = max(0, MAU - 100000) × 0.00325
Uncached egress   = max(0, uncached_GB - 250) × 0.09
Cached egress     = max(0, cached_GB - 250) × 0.03
File storage     = max(0, storage_GB_hours - 74400) × 0.00002919
Database disk    = excess_provisioned_gp3_GB_hours × 0.000171
Edge Functions   = ceil(max(0, invocations - 2000000) / 1000000) × 2
Realtime         = ceil(max(0, messages - 5000000) / 1000000) × 2.50

For database disk, calculate the provisioned space above 8 GB separately for each primary database, for each hour it is provisioned, and add the results. Read replicas and high-performance disks use different billing rules. File storage also accrues by the hour; the amount stored on the last day of the month is not enough to calculate the bill. Use the allowance shown for your billing cycle if your plan or subscription period changes. Disk billing, storage billing.

An active user is a distinct user who signs in or refreshes a token during the billing cycle. It is not simply every account ever registered in your database. How Supabase counts MAUs.

Three worked examples

These examples use a 31-day month, or 744 hours, with no instance changes. Each uses one Pro organization. All unlisted usage stays within its included allowance, and there are no add-ons, replicas or branches. The third example assumes the spend cap is off so the listed overages can be billed.

For the last column, uncached egress costs (600 - 250) × $0.09 = $31.50. Cached egress adds (1,000 - 250) × $0.03 = $22.50. The two allowances are independent. Egress pricing rules.

A file can be downloaded repeatedly without increasing the amount stored. This is why a file-sharing feature can change your bill even when storage size barely moves. Measure delivery traffic before using stored gigabytes as a proxy for operating cost.

Add the features your app actually uses

The table covers common charges, not every Supabase billing item. Add a separate row for any feature you enable outside it. Realtime peak connections, image transformations, SSO, log services, read replicas and branching deserve attention if your app uses them. The full billing catalog lists their measurement rules. Supabase usage items.

Failed Edge Function calls still count as invocations, although preflight OPTIONS requests do not. Realtime message counts can grow with the number of subscribers receiving an event. Use the billed message count when planning a collaborative feature. Function metering, Realtime metering.

Keep your wider SaaS budget beside this worksheet. Application hosting, transactional email, payment processing and AI-provider usage may arrive on separate invoices. Record any starter-kit purchase separately as well.

Understand what the spend cap covers

Supabase's Pro spend cap controls whether covered usage can exceed the included quotas. It covers items such as egress, storage, MAUs and function invocations. Exceeding allowances can lead to service restrictions under Supabase's fair-use policy.

Compute, branching compute, read replica compute and several add-ons are outside the cap. It also is not a configurable dollar budget for each billing item. Review the coverage before treating it as protection against every possible charge. Supabase cost controls.

For production, decide who reviews usage and who can respond when a quota is close. A cap that protects the budget can also interrupt a customer-facing feature. That tradeoff belongs in the launch plan.

Use the worksheet with your Nextbase app

If you are starting with a Nextbase Next.js and Supabase starter, keep this worksheet alongside your deployment notes. Add the projects you will run, then record the features that consume storage, database resources and traffic. A starter kit supplies application code; the Supabase bill still follows the resources your deployment uses.

During development, measure a few representative flows: signing in, loading a busy dashboard, uploading a file and downloading it repeatedly. Use those measurements to improve the assumptions in your budget. If an input is unknown, leave it marked unknown until you have evidence.

Review the worksheet after launch and whenever you add a feature with a different workload, such as file exports, live collaboration or AI-generated assets.