Clerk or WorkOS?

Clerk bills per retained user and suits React apps; WorkOS is free to a million users and bills per enterprise connection. Here’s what each costs for consumer and B2B apps, how they handle organizations, SSO and SCIM, and how to choose.

By the NestedBit team · Updated

Clerk vs WorkOS in short

Clerk and WorkOS both host sign-in for you, and both sell what business customers ask for: organizations, single sign-on and SCIM. They charge for different things.

  • Clerk is built for React and Next.js teams. You drop its components into your pages and get sign-in, user profiles and organization switching that look like part of your app. It bills per retained user, and its B2B features sit in a paid add-on.
  • WorkOS is built around enterprise customers. Its AuthKit sign-in is free up to a million monthly active users, with organizations and roles included, and you pay for each customer’s SSO or Directory Sync connection. Its SSO and Directory Sync also work as standalone APIs beside the auth you already run.

The prices on this page come from each vendor’s pricing page, checked on 10 Nov 2026, through the same engine as the free Auth Provider Picker. Vendors change plans often, so confirm the plan you pick on their site before you commit.

Clerk vs WorkOS pricing

They count users differently. Clerk bills monthly retained users: people who visit in a month at least a day after signing up. WorkOS counts monthly active users: anyone who signs up, signs in or updates their profile that month. The estimates below treat the two as equal, so Clerk’s figures may run high.

Clerk’s Pro plan is $25 a month with 50,000 retained users included, then $0.02 a user, less in volume. It includes one SSO connection and one Directory Sync connection, then charges $75 a month for each further one, less from the 16th. WorkOS charges nothing per user up to a million monthly active users, then $2,500 for each extra million. Every SSO or Directory Sync connection costs $125 a month, the first one too, less from the 16th; past 100 connections, its sales team sets the price.

Monthly cost, each vendor’s cheapest plan that covers the need:

ExampleClerkWorkOS
Consumer app with authenticator-app MFA
10,000 users $25 Pro $0 Pay as you go
100,000 users $1,025 Pro $0 Pay as you go
B2B SaaS with organizations and SSO
2,000 users, 20 customers, 1 SSO connection $125 Pro $125 Pay as you go
5,000 users, 50 customers, 5 SSO connections $425 Pro $625 Pay as you go
10,000 users, 150 customers, 10 SSO connections, 5 SCIM directories, custom roles $1,150 Pro $1,875 Pay as you go
25,000 users, 400 customers, 25 SSO connections, 10 SCIM directories $2,750 Pro $4,125 Pay as you go
Product-led B2B: many users, few SSO customers
100,000 users, 300 customers, 2 SSO connections $1,400 Pro $250 Pay as you go
200,000 users, 1,000 customers, 3 SSO connections $3,975 Pro $375 Pay as you go

Where the gap comes from: WorkOS includes authenticator-app MFA and passkeys on every account, so a consumer app pays nothing at these sizes. Clerk’s free Hobby plan covers 50,000 retained users without MFA, passkeys or SSO; Pro adds all three for $25, plus $0.02 for each retained user above 50,000. One catch: WorkOS’s hosted sign-in uses authenticator-app codes, not SMS. SMS needs its separate MFA API, which supports US numbers only.

For B2B, the first SSO customer costs the same on both: $125 a month at WorkOS, or Clerk’s $25 Pro plan plus its $100 Enhanced B2B add-on, which you need to link SSO connections to organizations. Each further connection is $75 at Clerk against $125 at WorkOS. But Clerk also charges for each organization above 100 and each retained user above 50,000, and WorkOS charges for neither, so the product-led rows flip.

Clerk starts billing Directory Sync connections beyond the first on 1 January 2027; the rows with SCIM directories include that. None of this includes tax, support plans, SMS charges or yearly discounts, nor WorkOS’s $99 a month custom domain; Clerk includes a custom domain on every plan. Put your own numbers into the picker, which also shows the line items behind each total and 11 other providers.

Sign-in screens and developer experience

  • Clerk gives you components such as <SignIn /> and <UserProfile /> that render inside your own pages, styled to match, or hosted pages if you’d rather redirect. Its quickstarts cover Next.js, React, React Router, TanStack Start, Astro, Nuxt, Vue, Expo, iOS, Android, Chrome extensions and Electron.
  • WorkOS uses AuthKit’s hosted UI: your app redirects to a sign-in page WorkOS hosts, branded with your logo, colors and copy, or you build your own screens on its API. AuthKit libraries cover Next.js, React, React Router, Remix, TanStack Start and Astro, with ten backend SDKs from Node.js to Rust. WorkOS Widgets add React components for managing users, switching organizations and issuing API keys.

Components are quicker to ship inside a framework Clerk supports. A redirect is a little more friction for users, but it keeps passwords off your own pages and works the same for every app you add later.

B2B: organizations, SSO and SCIM

Both handle the things business customers ask for. They package them differently.

  • Organizations. WorkOS sets no limit on organizations and doesn’t charge for them. Each can verify its domains and require SSO or MFA for its members. Clerk’s organizations are free with Admin and Member roles, custom permissions and invitations, up to 20 members each and 100 retained organizations a month. The Enhanced B2B add-on lifts the member limit and adds verified domains, custom roles and SSO linked to organizations.
  • Single sign-on. Both connect to any identity provider that speaks SAML or OIDC, and Clerk adds EASIE for Google and Microsoft accounts. WorkOS’s SSO also works as a standalone API beside an auth system you already run.
  • Self-serve setup. WorkOS’s Admin Portal, included in every account, is a hosted page where the customer’s IT admin verifies their domain and sets up SSO and Directory Sync, with walkthroughs for each identity provider. Clerk’s self-serve SSO puts the same steps in its organization profile component; in production it needs Pro or Business and the add-on.
  • SCIM. Both provision and remove users from the customer’s directory, and both can map directory groups to roles. Clerk’s Directory Sync covers Okta, Microsoft Entra ID, Google Workspace and other SCIM 2.0 providers. WorkOS’s also reads HR systems such as Workday, BambooHR and HiBob.
  • Roles. WorkOS includes roles and permissions on every account, with custom roles per organization, and its Fine-Grained Authorization extends them to resources such as workspaces and projects. Clerk’s custom roles need the add-on, and its docs allow 10 per application, more on request.

Before choosing either, write down the roles your product needs: lay them out in the RBAC Matrix Builder, then check each vendor can carry them.

Customizing logins and tokens

WorkOS Actions call an endpoint you host during sign-in and sign-up, passing the user, organization and IP address, and wait for it to allow or deny the attempt. Clerk works around the login instead: its webhooks arrive in the background after events such as sign-up, and its docs warn against relying on them inside a sign-in flow. WorkOS sends webhooks too.

Clerk’s session tokens last 60 seconds and its SDKs refresh them in the background. WorkOS issues a JWT access token carrying the user, organization, role and permissions, with a lifetime you set, plus a refresh token that may rotate on use. Both let you add your own claims: Clerk to its session token or through JWT templates, WorkOS through a JWT template. Paste either token into the JWT decoder to see exactly what your app receives.

For machine access, both offer API keys your users can create. Clerk’s M2M tokens are meant mainly for calls between your own services, with 2,500 created and 100,000 verifications a month included. WorkOS’s M2M applications use the client credentials flow and can only be set up for third parties, such as your customers’ services; its pricing page lists no price for them.

Clerk vs WorkOS for MCP servers

Both can act as the OAuth authorization server for an MCP server, so the server itself only checks tokens. Both support client ID metadata documents and dynamic client registration: WorkOS through AuthKit, where you switch metadata documents on in the dashboard, and Clerk through MCP servers you add in its dashboard, with a component for the consent screen. Read how MCP OAuth works first, so you know what to ask of whichever vendor you pick.

Data location and compliance

  • Region. Clerk’s security page says it offers no regional data residency and hosts data in the US. WorkOS’s security review says it hosts customer data on AWS in us-east-1, with backups in us-west-2, and we found no option to choose a region.
  • SOC 2. Both hold SOC 2 Type 2. Clerk shares its report on Business and Enterprise; WorkOS points to its Trust Center.
  • HIPAA. Clerk offers a business associate agreement on Enterprise. WorkOS says it can sign one for customers on enterprise plans.

If your customers require data to stay in the EU, neither fits as published. Clerk vs Auth0 covers a provider that lets you pick a region.

Moving between them

WorkOS publishes a guide to migrating from Clerk: Clerk exports users as CSV with their password hashes, and the WorkOS CLI imports them with their organizations and memberships, so people keep their passwords. Going the other way, WorkOS’s dashboard exports profiles only; password hashes come through its support team. Clerk’s open-source migration tool reads JSON or CSV, and its docs describe a gradual “trickle” migration where users move as they sign in.

SSO connections are harder, because each customer’s IT team pointed their identity provider at the old vendor. WorkOS suggests sending each customer its Admin Portal to update their side or, past 15 connections, a proxy on the old service’s custom domain that forwards callbacks so nothing changes for them. So run sign-in on a custom domain you own from the start, and keep your own user ID as the key in your database, with the vendor’s ID as a field you can replace.

Which one to choose

  • Choose Clerk for a React or Next.js product where sign-in should look like part of your app, with a handful of SSO customers and users in the tens of thousands.
  • Choose WorkOS when you expect many users or many small organizations, when you want SSO and SCIM beside the auth you already run, or when your own code must approve each sign-in.
  • Look at both again past 15 connections, where both vendors’ volume prices start, and before you sign a yearly contract with either.

And look beyond the two: Auth0, Supabase Auth, Firebase Authentication, Cognito and self-hosted options such as Keycloak and Better Auth price very differently. The Auth Provider Picker compares 13 providers on the features you tick and your own user numbers, in your browser.

Free tool · No sign-up

Auth0 Alternatives: Auth Provider Picker

Compare Auth0 alternatives on the features you need and see what each would cost a month at your number of users.

Starts with a free 30-minute intro call, or email hello@nestedbit.com.