Supabase Auth pricing: what the MAU tiers actually cost

Supabase Auth is one of the few identity services where the headline price is genuinely generous: 50,000 monthly active users on the free plan, and 100,000 included in Pro. The catch is that Auth is part of a platform, not a standalone product, so the number on the pricing page is only one line of the bill.

This page breaks down what Supabase Auth actually costs in 2026: the MAU tiers, the SAML SSO charge, and the database and compute costs that arrive with it.

The plans

The Free plan is fine for prototypes and small products. Pro is the first plan most production apps use. Team adds organization features, more support and higher limits for the rest of the platform; the Auth MAU allowance is the same as Pro.

How the MAU meter works

Supabase counts monthly active users for Auth. The exact definition matters because a user who signs in once and never returns can still count for the month. Check the current definition in the Supabase dashboard before you model a bill on it.

Two practical consequences:

• Anonymous and guest users can affect the count depending on how the app creates them. If you create a user record for every visitor, you are paying for visitors, not customers.
• MAU is counted per project. If you run separate Supabase projects for production, staging and a customer tenant, each project has its own count.

What SAML SSO costs

SAML 2.0 single sign-on is a separate meter. On paid plans, 50 SSO MAU are included, then $0.015 per SSO MAU. The Free plan does not include SAML SSO.

That pricing matters for B2B products. If 500 of your users sign in through a customer's identity provider, the SSO charge alone is about $6.75 per month after the included 50, on top of the regular MAU charge. It is not a large number at that scale, but it is a separate line to forecast, and it grows with enterprise adoption rather than with revenue.

Example bills

Here is what the Auth portion looks like at different sizes, before the rest of the Supabase platform:

The MAU overage is linear. There is no volume discount built into the self-serve tiers, so the bill scales with user growth in a way that a flat-price dedicated instance does not.

The rest of the Supabase bill

Auth does not run on its own. The project also pays for:

• Database compute. The Pro plan includes a compute credit, but larger instances cost more. Auth users live in Postgres, so the database is part of the identity workload.
• Storage and egress. Profile images, backups and API traffic are billed separately.
• Email. Supabase's built-in email service has rate limits and is not intended for high-volume production mail. Most production apps connect a custom SMTP provider, which is another bill and another deliverability problem.
• Add-ons. Point-in-time recovery, read replicas, log drains and other features are priced separately.

For a small app, these costs are modest. For a product with a large user table and high traffic, the database line can be larger than the Auth line.

When Supabase Auth is the right call

• You are already on Supabase. Auth is included, users live in Postgres, and row-level security policies use the signed-in user directly.
• You want one platform for database, storage and auth. One bill and one dashboard are real operational savings.
• Your app is one product, not a portfolio. Supabase Auth is designed around a Supabase project, not around being a central IdP for many unrelated applications.
• You do not need LDAP, CAS or a full admin console. Supabase Auth is a modern OIDC/OAuth provider, not a replacement for every enterprise directory protocol.

When a dedicated identity provider is better

• Several apps in different languages need one set of users and one login.
• Customers ask for SAML SSO, SCIM provisioning or custom domains as a standard feature rather than a per-MAU add-on.
• You need LDAP, CAS or RADIUS for older applications and network devices.
• You want flat pricing that does not grow with every new user.
• You want an admin console for support staff to inspect users, sessions and roles.

Casdoor covers those cases: OIDC, SAML, CAS, LDAP, RADIUS and SCIM, an admin console, organizations, and Casbin-based authorization. Casdoor Cloud is a dedicated instance from $6.67/month billed yearly ($9 month to month), with no per-user or per-connection fees. You can also self-host it for free.

FAQ

Is Supabase Auth free? Up to 50,000 MAU on the Free plan, yes, with the platform's other limits. Production apps usually move to Pro for the higher limits and the support.

What counts as a monthly active user? Supabase counts Auth users active in the billing month. The exact definition is in the Supabase documentation and dashboard; model a bill with your own sign-in data rather than assuming every registered user counts.

Is SAML SSO included in Pro? SAML SSO is available on paid plans with 50 SSO MAU included, then $0.015 per SSO MAU. It is not part of the Free plan.

Can I self-host Supabase Auth? Yes. Supabase is open source and can be self-hosted, but you run the whole stack, including Postgres, the API gateway and the Auth service. If you only need identity, a standalone IdP is usually less to operate.

Is Supabase Auth cheaper than Casdoor Cloud? At small user counts, Supabase's free tier is hard to beat. At scale, Casdoor Cloud's flat price is easier to predict: $6.67/month billed yearly for a dedicated instance with no per-MAU charge. Compare the two against your own MAU and SSO numbers.