Clerk Pricing: Plans, Tiers, and Cost Examples (2026)

Pricing overview

Clerk's pricing structure is primarily usage-based, with Monthly Active Users (MAUs) serving as the core billing metric. The platform provides a free tier designed for developers and small projects, offering a substantial allowance of MAUs before any charges apply. As applications scale and user bases grow, users transition to paid plans, which introduce a base monthly fee complemented by a per-MAU charge for usage beyond the included quota. This model is common among identity-as-a-service (IDaaS) providers, aligning costs with the actual number of users interacting with the authentication system each month. Clerk's pricing page details the specific thresholds and costs associated with each plan, enabling developers to estimate expenses based on their projected user activity Clerk's official pricing page.

The MAU definition for Clerk aligns with industry standards, counting any user who performs an authentication-related action (sign-in, sign-up, session refresh) within a given billing cycle. This includes users interacting with pre-built UI components, backend SDKs, or direct API calls. Clerk's focus on developer experience, particularly for Next.js and React applications, means that pricing considerations often involve the ease of integration versus the raw per-user cost when compared to building custom authentication solutions. For instance, a developer opting for Clerk might weigh the operational cost savings of pre-built components against potential higher per-MAU fees if they have a very large, low-engagement user base. This contrasts with services like PayPal's developer documentation, which focuses on transaction-based fees for payment processing rather than user identity management.

Plans and tiers

Clerk offers several plans tailored to different stages of application development and scale. These plans typically include a set number of MAUs, with additional MAUs billed at a per-unit rate. Key features such as multi-tenancy (Organizations), custom roles, and advanced security options are often gated behind higher-tier plans. The structure is designed to support both individual developers building prototypes and large B2B SaaS companies requiring complex user and organization management capabilities.

Plan Comparison Table

Each plan increment typically unlocks additional MAU allowances at a lower per-unit cost for overages, alongside more sophisticated features essential for larger-scale or more secure applications. For example, the ability to manage multiple applications under one account or implement advanced multi-factor authentication (MFA) methods like TOTP and SMS is generally reserved for paid tiers. The Starter plan is the first paid tier, offering significant value by enabling organization features, which are crucial for B2B SaaS products that need to manage distinct customer groups or workspaces Clerk Organizations overview.

Free tier and limits

Clerk's free tier is designed to provide a comprehensive entry point for developers. It includes 10,000 Monthly Active Users (MAUs) and grants access to all standard authentication features, such as email/password, social logins (OAuth), magic links, and basic user profile management. This tier is suitable for testing, developing proofs-of-concept, or running small-scale applications with a limited user base. The primary limitation of the free tier is the absence of Clerk's Organization features, which are essential for applications requiring multi-tenancy or complex team management. Additionally, the free tier typically restricts the number of applications that can be managed under a single account.

The 10,000 MAU limit on the free tier is generous compared to some alternatives, allowing developers to launch and gain initial traction without incurring costs. For instance, if an application has 5,000 users who log in at least once a month, it would comfortably operate within the free tier. However, exceeding this limit would necessitate an upgrade to a paid plan. It's important to monitor MAU usage, which Clerk provides through its dashboard, to anticipate when an upgrade might be required. The free tier also includes full access to Clerk's pre-built UI components and SDKs for various frameworks like Next.js, React, and Remix, ensuring a consistent developer experience from day one Clerk developer documentation.

Real-world cost examples

Understanding Clerk's MAU-based pricing requires looking at specific scenarios. These examples illustrate how the free tier and paid plans translate into actual monthly costs.

• Scenario 1: Small Startup with Initial Growth (5,000 MAUs)
  • Usage: 5,000 MAUs per month.
  • Plan: Free Tier.
  • Cost: $0.00.
  • Explanation: With 5,000 MAUs, the application remains well within the 10,000 MAU limit of the free tier. This allows the startup to focus on product development and user acquisition without incurring authentication costs.
• Scenario 2: Growing SaaS Application (25,000 MAUs)
  • Usage: 25,000 MAUs per month.
  • Plan: Starter Plan.
  • Cost Calculation:
    • Base fee: $25.00
    • Included MAUs: 10,000
    • Overage MAUs: 25,000 - 10,000 = 15,000 MAUs
    • Overage cost: 15,000 MAUs * $0.02/MAU = $300.00
    • Total monthly cost: $25.00 + $300.00 = $325.00
  • Explanation: This application has exceeded the free tier and uses the Starter plan. The base fee covers the first 10,000 MAUs, and the remaining 15,000 MAUs are billed at the Starter plan's overage rate. This scenario is typical for a SaaS product that has achieved product-market fit and is actively scaling its user base.
• Scenario 3: Mid-Market B2B Platform (75,000 MAUs)
  • Usage: 75,000 MAUs per month.
  • Plan: Growth Plan.
  • Cost Calculation:
    • Base fee: $100.00
    • Included MAUs: 50,000
    • Overage MAUs: 75,000 - 50,000 = 25,000 MAUs
    • Overage cost: 25,000 MAUs * $0.015/MAU = $375.00
    • Total monthly cost: $100.00 + $375.00 = $475.00
  • Explanation: At this scale, the Growth plan becomes more cost-effective due to its lower per-MAU overage rate and higher included MAU count. This plan also unlocks advanced features like custom roles and more sophisticated organization management, which are crucial for a B2B platform managing multiple client organizations.
• Scenario 4: Large Enterprise Application (300,000 MAUs)
  • Usage: 300,000 MAUs per month.
  • Plan: Enterprise Plan (custom pricing).
  • Cost: Negotiated custom rate.
  • Explanation: For very large user bases, Clerk typically offers custom Enterprise plans. These plans often include significant volume discounts, dedicated support, and specialized features like SAML/SCIM provisioning and enhanced compliance, which are vital for large organizations. The specific cost would be determined through direct negotiation based on usage, feature requirements, and support needs.

How the pricing compares

Clerk's MAU-based pricing model is a common approach in the identity-as-a-service (IDaaS) market, shared by several competitors. However, the specific MAU thresholds, per-MAU rates, and feature inclusions at each tier can vary significantly. When comparing Clerk to alternatives like Auth0, Stytch, or WorkOS, several factors come into play beyond just the raw MAU cost.

• Auth0: Auth0, a prominent IDaaS provider, also uses an MAU-based model but often has different tier structures and pricing for specific features. Auth0's free tier typically includes fewer MAUs (e.g., 7,000 MAUs) but might offer more advanced features at lower paid tiers compared to Clerk's initial offerings. Auth0's extensive ecosystem and enterprise features often come with a higher price point for comparable scale, particularly for custom branding and B2B capabilities Auth0 pricing details. Developers often weigh Auth0's broader platform capabilities against Clerk's streamlined, React-first developer experience.
• Stytch: Stytch focuses heavily on passwordless authentication methods (magic links, biometrics, TOTP) and also employs an MAU-based pricing model. Stytch's free tier is comparable to Clerk's, often offering a similar MAU allowance. Stytch's per-MAU rates can be competitive, and its emphasis on specific authentication flows might make it a more cost-effective choice for applications prioritizing passwordless experiences. However, Clerk's pre-built UI components might offer quicker time-to-market for a broader range of authentication needs, including traditional email/password flows.
• WorkOS: WorkOS primarily targets enterprise B2B applications, focusing on features like SAML, SCIM, and Directory Sync. Its pricing model is often structured around the number of organizations or enterprises managed, in addition to MAUs. While WorkOS offers a free tier for developers, its core value proposition and pricing become more pronounced for larger B2B clients requiring deep enterprise integrations. For a simple B2C application or a smaller B2B SaaS without complex enterprise requirements, Clerk or Stytch might present a more cost-effective initial entry point.

Beyond direct pricing, developers also consider the total cost of ownership (TCO), which includes development time, maintenance, and the operational overhead of managing authentication. Clerk's pre-built UI components and strong integration with modern frontend frameworks like Next.js can significantly reduce development effort, potentially offsetting higher per-MAU costs compared to building and maintaining custom solutions or integrating with less opinionated platforms. The choice often comes down to the specific feature set required, the target audience (B2C vs. B2B), and the preferred developer experience. For a detailed comparison of IDaaS providers, resources like Google's identity authentication documentation can provide context on various authentication approaches and their complexities, which indirectly influence the value proposition of managed services.