Pricing for Clerk
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
- Active user growth and needing higher entitlements/support
- Need for B2B org management and advanced access controls
- Need for higher security/compliance assurances and SLAs
- Need to integrate enterprise SSO patterns for larger customers
- Need to standardize auth across multiple apps/products
What gets expensive first
- Auth UI coupling makes switching providers more expensive later
- B2B needs expand: orgs, roles, audit, provisioning expectations
- Custom branding and flows may hit platform boundaries
- Compliance requirements can require extra contractual work
- Operational dependence shifts from your infra team to the vendor
Plans and variants (structural only)
Grouped by type to show structure, not to rank or recommend SKUs.
- Starter - Usage-based - Ship quickly with managed UI and sessions (see pricing page)
- B2B - Org features - Teams/org management drives upgrades (see pricing page)
- Enterprise - Contracted - Compliance, SSO, and support/SLA requirements (see pricing page)
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.