Pricing for Supabase Auth
How pricing changes as you scale: upgrade triggers, cost cliffs, and plan structure (not a live price list).
Freshness & verification
Pricing behavior (not a price list)
These points describe when users typically pay more and what usage patterns trigger upgrades.
Actions that trigger upgrades
- Enterprise customers require SSO and identity governance features
- Need for SCIM provisioning and lifecycle workflows for B2B tenants
- Need stronger auditability and admin controls for large tenants
- Need to standardize identity across multiple products/apps
- Need advanced security and anomaly controls beyond defaults
What gets expensive first
- Auth and data layer coupling increases switching cost later
- B2B identity expands scope beyond login (orgs, roles, audits, provisioning)
- Account recovery and abuse prevention are operational costs at scale
- RLS is powerful but requires discipline to avoid security footguns
- Identity incidents are outages: logs and runbooks still matter
Plans and variants (structural only)
Grouped by type to show structure, not to rank or recommend SKUs.
- Core - Platform-included - Auth integrated with Supabase stack (see docs)
- Scale - Usage-driven - Costs appear with broader platform usage and operations
- Enterprise - Platform shift - SSO/provisioning often requires a CIAM layer
Compare pricing trade-offs head-to-head
Use these comparisons when you are down to two finalists and need a clearer trade-off view.
Next step: constraints + what breaks first
Pricing tells you the cost cliffs; constraints tell you what forces a redesign.
Sources & verification
Pricing and behavioral information comes from public documentation and structured research. When information is incomplete or volatile, we prefer to say so rather than guess.
Something outdated or wrong? Pricing, features, and product scope change. If you spot an error or have a source that updates this page, send us a correction. We prioritize vendor-verified updates and linkable sources.