Supabase Pricing Explained: Free, Pro, Team & Enterprise Plans

TL;DR #

• Free: $0/month — 500 MB database, 50K MAUs, 2 active projects, pauses after 7 days idle. Good for MVPs and prototypes.
• Pro: $25/month + usage overages — 8 GB database, 100K MAUs, 100 GB storage. The right plan for most production apps.
• Team: $599/month — SOC2/ISO 27001, SSO, SAML, 14-day backups, HIPAA add-on. For regulated industries and B2B SaaS.
• Enterprise: Custom — dedicated support, BYO cloud, uptime SLAs.
• Compute is billed separately on top of every paid plan. The $10/month compute credit covers one Micro instance (1 GB RAM). More projects or larger instances = higher bills.
• Real-world Pro plan cost: most small-to-medium apps land at $35–$75/month once usage fees are counted.
• **The Supabase MCP Server is free to use: **it connects AI tools like Cursor, Claude, and VS Code Copilot.
• No annual billing is available for self-service plans. Team and Enterprise can negotiate annual contracts via AWS Marketplace.

Why Supabase Is Winning the Backend Market in 2026 #

Before unpacking every line item, it’s worth understanding why so many development teams and founders are asking about Supabase pricing at all.

Supabase hit $170M in ARR in May 2026, up from ~$101M at the end of 2025. That growth isn’t happening in a vacuum. Database launches on Supabase grew 600% in the year leading up to June 2026, with more than 60% of new databases launched by AI tools. Vibe coding platforms like Bolt.new, Lovable, Cursor, Claude Code — have made Supabase the default backend for AI-generated apps.

Supabase reported 15.1 million databases created in 2025 alone, more than all prior years combined, and $70M in annual revenue, up from $16M in 2024. Active domains running Supabase jumped 20x in two years, from 252 in July 2023 to 5,171 by July 2025.

The user base has a clear shape: 81% of websites using Supabase belong to companies with 10 or fewer employees, and over 1,000 Y Combinator companies use the platform.

A few structural reasons that are important for pricing decisions #

1. Open-source, no vendor lock-in. Your data lives in a standard PostgreSQL database. If you leave, run pg_dump and take your data anywhere — AWS RDS, Neon, a VPS, or your own server. Firebase cannot say the same.
2. Cost advantage at scale. Teams report 35% cost savings migrating from Firebase to Supabase—around $22K/year for a mid-sized SaaS. Supabase Postgres delivers 42% higher read throughput than Firebase Firestore at 10,000 concurrent connections.
3. AI-native tooling. Supabase raised a $500M Series F at a $10.5B post-money valuation in June 2026, with the round intended to accelerate open-source and Postgres tooling development. The MCP Server—which lets AI coding tools interact with your Supabase project directly—is a central part of that strategy.

For developers evaluating whether Supabase is the right backend choice, the pricing model is both the entry point and a long-term cost variable.

What Is Supabase? (For Those New to the Platform) #

Supabase is an open-source Backend-as-a-Service (BaaS) built on PostgreSQL. Often described as the “open-source Firebase alternative,” it bundles everything a backend needs into a single managed platform:

• PostgreSQL database with instant REST and GraphQL APIs generated from your schema
• Authentication (email/password, OAuth, magic links, phone) with Row Level Security
• Supabase Storage for file uploads, CDN delivery, and access control
• Edge Functions (Deno-based) for serverless logic and scheduled tasks
• Realtime subscriptions for syncing data via WebSockets
• Vector database via pgvector — included free, no separate service needed
• Supabase MCP Server for AI-native development with Cursor, Claude, Windsurf, and VS Code

The key differentiator from Firebase is the SQL foundation. You get standard relational queries, joins, CTEs, window functions, full-text search, and Postgres extensions — none of which Firestore supports. You can also self-host using Docker Compose if you need full infrastructure control or data residency compliance.

How Supabase Pricing Works: The Model Explained #

Supabase uses a hybrid pricing model: a fixed monthly base fee per plan tier, plus usage-based charges for anything exceeding plan quotas.

Each subscription plan includes a built-in quota for selected usage items such as egress, storage size, and Edge Function invocations. This quota represents your free usage allowance. Only usage beyond the quota is billed as overage. For usage items without a quota, such as compute or custom domains, you are charged for your entire usage.

A few structural points that affect your bill:

Billing is per organization, not per project. Supabase bills separately for each organization. Each organization has its subscription, including a unique plan, payment method, billing cycle, and usage quota. The quota is applied to the entire organization, independent of how many projects you launch within it. For billing purposes, Supabase sums the usage across all projects in a monthly invoice.

Compute is always extra. Every project on the Supabase platform comes with its own dedicated Postgres instance. Paid plans come with $10/month in compute credits to cover one micro instance or offset the cost of any other instance. If you run multiple projects or need more than 1 GB of RAM, compute costs stack up fast.

Spend caps protect you by default on Pro. The Pro plan has a spend cap enabled by default to keep costs under control. If you want to scale beyond the plan’s included quota, simply switch off the spend cap to pay for additional resources.

No annual billing for self-service. Annual plans are not officially supported for self-service plans, though Team and Enterprise can use AWS Marketplace with annual contracts with no published discount percentage.

Supabase Plans in 2026: Every Tier Broken Down #

Free Plan — $0/month #

The Free plan is a genuine free tier, not a trial. You can run real projects on it indefinitely.

What you get per organization:

• 2 active projects (paused projects don’t count toward the limit)
• 500 MB database storage
• 50,000 monthly active users (MAUs)
• 1 GB file storage
• 5 GB database egress
• 5 GB cached egress
• 500,000 Edge Function invocations/month
• 200 concurrent realtime connections
• 2 million realtime messages/month (256 KB max message size)
• Unlimited API requests

What it doesn’t include: custom domains, daily backups, SLAs, SSO, HIPAA compliance, or priority support.

The catch: Free plan projects are paused automatically after 7 days of inactivity. Your data is retained, but the project goes offline until you manually resume it. For anything user-facing, this is a dealbreaker. Fine for dev and staging.

Right for: prototypes, hackathon projects, MVPs in early validation, staging environments alongside a paid production instance, students learning SQL and Postgres for the first time.

Pro Plan: $25/month + usage #

Pro is the default plan for solo developers, indie makers, and early-stage startups shipping to real users.

What’s included per organization:

• 8 GB database storage
• 100,000 MAUs
• 100 GB file storage
• 250 GB database egress
• 250 GB cached egress
• 2 million Edge Function invocations/month
• 500 concurrent realtime connections
• 5 million realtime messages/month
• Daily automated backups (7-day retention)
• $10/month compute credit (covers one Micro instance)
• Email support

Projects beyond the first: Additional projects are available from $10/month each — this is a common source of billing surprise. A staging environment and production environment on Pro runs $35/month before any usage overages, not $25.

Real-world costs: Most small-to-medium production apps pay $35–$75/month once usage fees are included. High-traffic apps with 200K+ MAUs typically run $100–$200/month.

Right for: any app that has shipped to real users, SaaS products in early growth, indie tools, apps needing daily backups and no inactivity pauses.

Team Plan: $599/month + usage #

The Team plan is the compliance and collaboration tier. Most solo builders and early-stage startups don’t need Team. It’s for regulated industries, enterprise clients, or companies where SOC2 certification is a hard requirement from customers.

What Team adds on top of Pro:

• SOC2 Type II and ISO 27001 certifications
• HIPAA compliance (available as a paid add-on)
• SSO / SAML for the Supabase Dashboard
• 14-day backup retention (vs. 7 days on Pro)
• 28-day log retention (vs. 7 days on Pro)
• AWS PrivateLink
• Priority support with SLAs
• Project-scoped access controls
• Audit logging
• Advanced MFA options

The $574 jump from Pro to Team is intentional: it’s not a compute upgrade, it’s a compliance and governance upgrade. If your customers are demanding SOC2 audit reports or your sales process requires security questionnaires, Team is when the math starts to work.

An important clarification on MAU limits: Auth MAUs exceeding 100,000 on Pro cost $0.00325 per additional user. At 500,000 MAUs, that’s $1,300/month in overages alone. The Team plan includes 500,000 MAUs for $599, so at that user scale, Team can actually be cheaper than Pro with overages.

Right for: B2B SaaS companies selling to enterprises, healthtech and fintech apps handling regulated data, agencies managing multiple client projects with team access controls, and companies where an enterprise customer has asked for a compliance report.

Enterprise Plan: Custom Pricing #

Enterprise is for organizations with non-negotiable requirements around uptime, support, data sovereignty, and security.

What Enterprise adds:

• Custom uptime SLAs and incident response
• 24/7 dedicated support with a private Slack channel
• Designated support manager
• BYO cloud (bring your own cloud) deployment
• Custom project-scoped roles
• 90-day log retention
• Security questionnaires and legal reviews
• Custom data residency guarantees

If you’re asking about enterprise pricing, contact Supabase sales directly. The spend is justified when legal or procurement requirements would otherwise block a deal.

Supabase Price Calculator: How to Estimate Your Real Monthly Bill #

The official Supabase pricing page includes an interactive cost estimator. Here’s how to model it manually.

Overage rates on Pro #

MAU overages are billed at $0.00325 per MAU above the plan quota. The count resets at the start of each billing cycle.

Worked examples #

Scenario 1: Early SaaS, 20K MAUs, minimal storage

• Pro plan: $25
• Compute (1 Micro, covered by credit): $0
• Usage: all within limits
• Total: $25/month

Scenario 2: Growing app, 150K MAUs, 300 GB egress

• Pro plan: $25
• Compute: $0 (credit applied)
• MAU overage: 50,000 × $0.00325 = $162.50
• Egress overage: 50 GB × $0.09 = $4.50
• Total: ~$192/month

Scenario 3: Multi-project setup, production + staging

• Pro plan: $25 (first project)
• Second project: $10
• Two micro compute instances: $10 credit offset one, second is $10
• Total: ~$45/month before any usage overages

Scenario 4: B2B SaaS at 300K MAUs, SAML login required

• Pro plan with overages: $25 + (200K × $0.00325) = $675
• SSO MAU costs: $0.015 per SSO MAU above the included quota
• At this point, Team ($599) including 500K MAUs likely costs less
• Decision point: evaluate Team at ~200K–300K MAUs

The biggest hidden cost most developers don’t model upfront is multi-project compute. One SaaS client running four Pro projects — production, staging, and two regional replicas — paid compute on every instance beyond the single Micro that the $10 monthly credit covers, so the bill landed near $130, not the $25 the team had pencilled in.

Supabase Compute Pricing: The Layer That Surprises Most Teams #

Every Supabase project runs on a dedicated Postgres compute instance. The $10/month credit covers exactly one micro instance. Everything else is billed on top.

Compute instances are billed hourly, and you can scale up or down at any time. Start at Micro and upgrade only when your Supabase dashboard shows consistent CPU or memory pressure.

Disk options #

Supabase defaults to General Purpose disks. High performance is available for latency-sensitive workloads.

General Purpose: $0.125/GB after the first 8 GB, 3,000 IOPS included, max 16 TB, 99.9% durability.

High Performance: $0.195/GB, higher IOPS, max 60 TB, 99.999% durability. Add this only when query latency is measurably affecting your product.

Supabase Auth Pricing: What MAUs Actually Mean #

Supabase charges for authentication via Monthly Active Users (MAUs)

You are charged for the number of distinct users who log in or refresh their token during the billing cycle, including social login. Each unique user is counted only once per billing cycle, regardless of how many times they authenticate.

This is more forgiving than it sounds. A user who logs in 30 times in a month counts as 1 MAU, not 30.

SSO / SAML pricing: SAML 2.0 SSO MAUs are billed at $0.015 per SSO MAU above the plan’s included quota. For apps where enterprise customers log in via their identity provider (Google Workspace, Microsoft Active Directory), this is a separate meter from standard MAUs.

Third-party auth providers (Clerk, Auth0, Firebase Auth, Cognito): Third-party MAUs are billed at $0.00325 per MAU above the plan quota—the same rate as standard MAUs.

Practical MAU threshold for plan decisions:

• Under 100K MAUs: stay on Pro
• 100K–300K MAUs: model overages carefully; the team plan may be cheaper
• 300K+ MAUs: Team likely cheaper than Pro with overages, assuming SSO is needed

Supabase Edge Functions Pricing #

Edge Functions run on Deno at edge locations globally. They’re best for authentication logic, webhooks, scheduled jobs, and lightweight processing, but it’s not ok for full backend workloads.

Included per plan:

• Free: 500,000 invocations/month
• Pro: 2 million invocations/month
• Team: 2 million invocations/month

Overage rate: $2 per additional million invocations.

For most apps, Edge Function costs stay within the included quota until you’re running heavy AI inference, aggressive cron jobs, or processing large event streams. Monitor your invocation count in the dashboard before assuming it’ll be an issue.

Supabase Custom Domain Pricing #

A custom domain for your Supabase project (so your auth and API URLs reflect your brand rather than your-project.supabase.co) costs $10/month per domain per project.

This is not included in the Pro plan base. If you have three projects, each with a custom domain, that’s $30/month in custom domain charges on top of your plan fee.

Supabase Add-Ons Pricing Reference #

Most teams won’t need these day one. Point-in-time recovery matters when you’re running financial or medical data where you need sub-minute rollback capability. Log drains are useful when you’re integrating with external observability platforms like Datadog or Splunk.

Supabase Student Pricing #

There is no official public student discount program for Supabase as of June 2026. Supabase is not listed in the GitHub Student Developer Pack.

In a 2021 GitHub discussion, co-founder Paul Copplestone explicitly confirmed that university students would be eligible for 2 years of base tier (now Pro) usage.

However, the current application process for this is not documented publicly, and the program’s active status is unclear.

How students/educators and other non-profits can use Supabase:

• Use the free plan:
• Reach out directly to Supabase support to inquire about credits for educational projects (the beta pricing post confirmed they support code schools and students where possible)
• For larger classroom deployments, contact Supabase directly with documentation of educational use

For most student projects building a portfolio app, learning PostgreSQL, shipping an MVP to validate an idea, the free tier is sufficient. 50K MAUs and 500 MB of storage will carry most academic projects without any billing.

Supabase Alternatives: How Pricing Compares #

Supabase is not the only option in the managed Postgres/BaaS space. Here’s an honest comparison for teams weighing alternatives.

Supabase vs. Firebase #

Firebase uses operation-based billing (reads, writes, document deletes), which is harder to predict and can spike under load. Firebase cannot be self-hosted — your data always lives on Google servers. Teams report an average of 35% cost savings migrating from Firebase to Supabase.

Firebase wins for mobile-first apps needing offline sync, push notifications (FCM), and the Google ecosystem. Firebase had major free tier changes in early 2026: Cloud Storage was removed from the Spark (free) plan in February 2026.

Supabase wins for relational data, SQL complexity, lower cost at scale, open-source flexibility.

Supabase vs. Neon #

Neon is pure serverless PostgreSQL — no auth, no storage, no APIs. Neon is better for pure Postgres needs — scale-to-zero, branching, and 0.5 GB storage per project with up to 100 projects. Neon’s scale-to-zero means you pay zero compute when your database is idle, which can be cheaper than Supabase’s always-on model for low-traffic or development databases.

Supabase wins for: teams that need the full backend bundle (auth + storage + realtime + functions) without assembling separate services.

Supabase vs. Appwrite #

Appwrite is an open-source BaaS with a self-hosted option and a managed cloud at $25/month Pro. Appwrite’s self-hosted Docker image is 40% smaller than Supabase’s and uses 30% less RAM at idle, making it ideal for edge or resource-constrained environments.

Appwrite uses a document database internally (not SQL) which limits join complexity. Supabase is a strong choice for relational data and AI workloads (pgvector). Appwrite has the most generous free tier at 75K MAU and is fully open-source.

Supabase MCP Pricing: What It Costs to Use the MCP Server #

The Supabase MCP (Model Context Protocol) Server is a free feature available on any Supabase plan, including Free.

The MCP Server bridges the gap between AI tools and Supabase projects, enabling natural language commands and agent-like experiences for database management. It standardizes how Large Language Models communicate with platforms like Supabase, allowing AI tools such as Cursor, Claude, and Windsurf to spin up projects, design tables, query data, and manage configurations — all through a unified protocol.

There is no additional subscription or API cost to use the MCP Server itself. Your Supabase plan’s existing compute and usage quotas apply — any queries run through the MCP Server consume from your normal database compute and egress quotas, exactly as direct queries would.

The MCP Server now uses OAuth by default via dynamic client registration, so your AI tool authenticates through a browser-based flow. A PAT (personal access token) is only needed for CI/CD or non-interactive scenarios.

What the MCP Server can do for your development workflow:

• Create and manage Supabase projects directly from your AI tool
• Design tables, generate migrations, and manage schema with natural language
• Query data and run SQL reports
• Manage branches, configurations, and generate TypeScript types
• Retrieve logs for debugging
• Automate repetitive schema and configuration tasks

Important security guidance: The MCP Server connects with elevated permissions. Always use read-only mode by appending ?read_only=true when connecting to production databases, scope the server to a specific project, and never expose it to customers or end users, it operates under your developer permissions.

In terms of pricing, the MCP Server is a developer productivity tool, not a billable feature. If you’re using it to spin up databases via Cursor or Claude Code during development, those databases consume from your plan’s project and compute quotas as normal.

How to Choose the Right Supabase Plan #

Use this as a decision tree before signing up or upgrading.

Choose Free if:

• You’re building a prototype, hackathon project, or learning Postgres for the first time
• You can tolerate 7-day inactivity pausing (staging environments, portfolio projects)
• You have 2 or fewer active projects
• You don’t need daily backups or email support

Choose Pro ($25/month) if:

• You have real users; any live production app should be on Pro
• You need daily backups and no inactivity pauses
• Your MAUs are under 100k and you have under 8GB of storage
• You want the spend cap for billing predictability while you grow
• You’re building a SaaS product pre-Series A

Choose Team ($599/month) if:

• A customer has asked for a security questionnaire
• You’re in healthcare, fintech, or another regulated industry
• You need SSO/SAML for your dashboard or for your end users
• Your MAU count is approaching 200K–300K (the team may be cheaper than Pro with overages).
• You need 14-day backup retention or 28-day log retention

Choose Enterprise if:

• You need uptime SLAs, 24/7 support, or BYO cloud
• Your organization has legal or procurement blockers that standard plans don’t satisfy
• You’re running at a huge scale and need custom resource limits

Frequently Asked Questions #

How much does Supabase cost per month on average? #

Most small-to-medium production apps on the Pro plan pay $35–$75/month once usage fees are included. High-traffic apps with 200K+ MAUs typically run $100–$200/month. The $25 base is accurate for early-stage apps staying within plan quotas.

Is Supabase’s free tier good enough for a real app? #

For an MVP or a tool with low user counts, yes. The Free tier provides 500 MB database storage, 50K MAUs, and 1 GB of file storage. The catch is automatic pausing after 7 days of inactivity; that is fine for dev work.

Does Supabase charge for the number of projects? #

Yes. The first project is included. Additional projects cost from $10/month each. Each project also requires its own compute instance, with only one micro instance covered by the included $10 compute credit.

What’s the difference between Pro and Team? #

Pro is for production apps with predictable usage. Team adds compliance certifications (SOC2, ISO 27001), SSO/SAML, longer backup and log retention, AWS PrivateLink, and HIPAA as an add-on. The jump from $25 to $599 is a compliance buy, not a raw performance upgrade.

Is there a Supabase annual plan? #

Annual plans are not officially supported for self-service, though Team and Enterprise can access annual contracts via AWS Marketplace with no published discount percentage. Self-service billing is monthly only.

Does Supabase offer a student discount? #

There is no publicly listed student discount program as of June 2026. Supabase has historically been open to providing credits for educational projects—contacting support directly with proof of academic use is the recommended path. The Free plan is designed to cover most student needs without billing.

How does Supabase Auth pricing work? #

You’re charged for distinct users who log in or refresh their token during the billing cycle. Each unique user counts once regardless of login frequency. The overage rate above the plan quota is $0.00325 per MAU. SSO/SAML users are metered separately at $0.015/MAU.

Can I self-host Supabase for free? #

Yes. Supabase is fully open source and self-hostable via Docker. You pay your server costs instead of Supabase cloud fees. Self-hosting makes sense for teams with DevOps capacity who need full infrastructure control, but you take on maintenance, backups, and upgrades yourself.

Is Supabase cheaper than Firebase? #

Teams report an average of 35% cost savings migrating from Firebase to Supabase, approximately $22K/year for a mid-sized SaaS. Firebase’s per-operation model (reads, writes, deletes) can produce unpredictable bills at scale. Supabase’s resource-based model (database size, egress, MAUs) is easier to forecast. That said, Firebase has no fixed monthly base fee on its Blaze plan, which makes it cheaper for very low-traffic apps at idle.

Does Supabase charge for the MCP Server? #

No. The Supabase MCP Server is free to use on any plan. It does not add to your plan tier or introduce separate API charges. Any database queries made through the MCP Server consume from your normal compute and egress quotas.

What are the hidden costs of Supabase? #

The most common billing surprises are (1) per-project compute charges above the first micro instance, (2) MAU overages once you pass 100K users on Pro, (3) custom domain fees at $10/domain/project, (4) egress on media-heavy apps, (5) PITR if you turn it on without tracking the $100/month cost. Running a second project always adds at least $10/month plus compute.

How does Supabase pricing compare to building on AWS directly? #

At $25/month, Pro is one of the best-value backend platforms available—cheaper than running your Postgres server on AWS once you factor in managed backups and connection pooling. The bundled auth, storage, and real-time at no extra base cost makes the comparison even more favorable for teams that would otherwise pay for those services separately.

Final Verdict: Is Supabase Worth It in 2026? #

For the vast majority of development teams: solo builders, early-stage startups, and agencies building client products—yes.

The free tier is a genuine way to ship an MVP without paying. The Pro plan at $25/month bundles database, auth, storage, real-time, and edge functions at a price point that would cost significantly more than assembling the equivalent services individually. The MCP Server integration with AI tools is a free accelerant for developer productivity.

The places where Supabase requires careful cost modeling: multi-project setups (compute stacks), media-heavy apps (egress), and rapid MAU growth (auth overages). None of these are Supabase-specific problems—they’re infrastructure economics—but they’re worth forecasting before you’re surprised by a bill.

Start on Free. Monitor your usage dashboard. Upgrade to Pro when you need more users. Upgrade compute only when you see some limitations/pressure. And if a customer starts asking for SOC2 reports, that’s the signal to evaluate the team.