Supabase pricing in 2026: Free and Pro plans and what it really costs

1. Supabase plans at a glance#

Supabase offers managed PostgreSQL with authentication, file storage and functions in one service. The prices in this guide are in US dollars and come from its official pricing page, read on October 17, 2026. Taxes and payment-method fees are added on top.

The table summarizes the essentials. The Free plan is an environment to get started, not for production: 500 MB of database per project, two active projects and a pause after a week of inactivity. The Pro plan starts at $25 a month, removes the pause for inactivity and adds daily backups with seven days of retention. Team, from $599 a month, extends backup retention to 14 days. Point-in-time recovery is a separate add-on: $100 a month per 7 days of retention.

Documentation: Supabase: pricing and plans ↗

2. What Pro includes and what is billed separately#

The Pro plan's $25 a month includes $10 a month in compute credits, which cover one Micro instance. If your project needs more compute, you pay the difference between the instance price and those $10. Compute is billed per project, regardless of how much your database is used; if you have several projects, check the billing documentation for how the credits apply. The table shows the compute sizes and their monthly price.

Three line items grow with your usage. Disk includes 8 GB per project and each additional GB costs $0.125. Egress includes 250 GB and the excess costs $0.09 per GB. File storage includes 100 GB and the excess costs $0.0213 per GB. In addition, monthly active users included are 100,000 and each extra one costs $0.00325.

Documentation: Supabase: pricing and plans ↗ · Supabase: compute and billing ↗

3. Worked example: three application sizes#

To see what it really costs, let's calculate three applications with a single project on the Pro plan. The function adds the $25 base, the compute difference above the $10 credit, disk above 8 GB and egress above 250 GB. It does not include files, extra active users or taxes.

COMPUTE = {"micro": 10, "small": 15, "medium": 60, "large": 110}  # USD per month

def supabase_pro_cost(db_gb: float, egress_gb: float, compute: str = "micro") -> float:
    base = 25.0                                  # Pro plan
    credit = 10.0                                # included compute credits
    extra_compute = max(0.0, COMPUTE[compute] - credit)
    extra_disk = max(0.0, db_gb - 8) * 0.125     # 8 GB included per project
    extra_egress = max(0.0, egress_gb - 250) * 0.09   # 250 GB included
    return base + extra_compute + extra_disk + extra_egress

for compute, db_gb, egress_gb in [("micro", 5, 100), ("small", 20, 300), ("medium", 60, 1200)]:
    print(compute, db_gb, egress_gb, f"{supabase_pro_cost(db_gb, egress_gb, compute):,.2f}")

The first application pays nothing above the $25. The second adds $5 of compute, $1.50 of disk and $4.50 of egress and ends at $36. In the third, a Medium compute adds $50 and the 1.2 TB of egress adds $85.50: the total reaches $167, almost seven times the front-page figure. The lesson is that compute and egress drive the bill as you grow, not the plan.

Go deeperPostgreSQL: Find the Right Index with EXPLAIN

4. When the Free plan falls short#

Free works for prototypes, tests and personal projects. It falls short for four concrete reasons, all visible in the plan table.

• Pause for inactivity: a Free project pauses after a week without activity, which breaks any product with sporadic visits.
• Size: 500 MB of database per project is reached quickly with records, vectors or analytics data.
• Projects: the plan allows two active projects, so one production and one test environment already exhaust it.
• Backups: Free does not include the daily backups Pro offers; if you lose data, there is no provider backup to go back to.

If your application has real users, moving to Pro is reasonable from day one: it removes the pause and adds backups. The base cost is $25 a month, plus any compute and usage above what is included.

Go deeperSupabase Free vs Pro: differences, limits and when to upgrade

Documentation: Supabase: pricing and plans ↗

5. Alternatives: Turso and other entry plans#

Turso is a SQLite-compatible database designed for many small databases and reads close to the user; it is not PostgreSQL, so the comparison is about billing model more than an identical product. Its plans charge for rows read and written and for storage, not per instance.

Turso plans, also in dollars and per its official pricing page:

If your application needs PostgreSQL with extensions, advanced SQL features or a tooling ecosystem, Supabase is the natural choice. If your pattern is many small databases per customer or a very high read volume, Turso's per-row billing can come out cheaper. Compare the Supabase and Turso plans side by side in Codifly's database comparator.

Go deeperManaged database prices in 2026: Neon, Supabase, PlanetScale, Turso and Cloudflare D1

Documentation: Turso: pricing ↗

6. Keep your numbers current#

Managed database plans change their limits and billing often. The figures in this guide are those on the official page on October 17, 2026; confirm the conditions before committing to an annual budget.

• Check real disk, egress and compute usage in the Supabase dashboard for a month before deciding the instance size.
• Set up spend alerts to catch the egress spike, which is the line item that surprises most.
• Compare against other entry plans with the database comparator before choosing, and do it again when your volume changes.

Go deeperEnvironment variables and DATABASE_URL in production: a full guide

Documentation: PostgreSQL: official documentation ↗