Updated

Clerk vs WorkOS

Of the 422 makers' products we know the authentication of, 336 chose Clerk (80%) and 20 WorkOS (5%). Among the 98 launched in 2026, Clerk is in 84% and WorkOS in 8%, against 76% and 3% of those launched in 2024 or earlier. On GitHub, 6 public pull requests moved projects from Clerk to WorkOS, and 4 the other way.

Two hosted service options for authentication. When each fits, what it costs, who moves from one to the other, and what makers who chose it say.

Ask your AI about this, with this page as the source:ChatGPT ↗Claude ↗Perplexity ↗

Which fits you

Choose Clerk if
  • You're on Next.js or React and want sign-in, profiles and teams working today

Use it whenYou want prebuilt components, user profiles and organizations out of the box.

Trade-offPer-user pricing grows with you; users live in Clerk, not your database.

Choose WorkOS if
  • You sell to companies whose IT team will ask for SAML SSO or SCIM

Use it whenYour first big customer asks for SAML or SCIM.

Trade-offIts free tier covers basic sign-in, but enterprise SSO and directory sync are priced per connection — worth it once a customer pays for them.

At a glance

ClerkWorkOS
Used by336 makers' products · 14 open-source projects20 makers' products · 12 open-source projects
Cost at default usagemonthly active users 10k MAU$0/mo Hobby$0/mo AuthKit
Moved to it on GitHubpull requests since Oct 20244 from WorkOS6 from Clerk
Downloads2.3M/wk+53% vs npm2.9M/wk+103% vs npm
PricingFree tier by monthly active users; paid plans add features and seats. · paid from $25/moFree user-management tier; enterprise SSO and directory sync priced per connection. · paid from $125 per connection/mo
Free tierYesYes
Open sourceNoNo
Incidents, 90 daysfrom its status page924 (10 major)

Which makers on your framework pick

Makers' products built with each framework that chose either one, for authentication.

New launches vs older products

A tool that came first has products from every year since, so its total runs ahead. Here is what products launched each year chose, as a share of those that made the authentication decision (by the year they launched on Product Hunt).

LaunchedClerkWorkOSProducts
202476% 683% 389
202579% 833% 3105
202684% 828% 898

Cost as you grow

Both cost $0 up to 50k MAU; from 100k MAU WorkOS costs less ($0 vs $1,025); and still does at 1M MAU ($0 vs $17,225).

$0$500$2,000$5,000$10,0001001k5k10k25k50k100k250k1M
WorkOSClerkx: monthly active users (MAU) · cheapest usable plan at each point, list prices · try your own numbers
The numbers, plan by plan
Monthly active usersClerkWorkOS
100$0 Hobby$0 AuthKit
1,000$0 Hobby$0 AuthKit
5,000$0 Hobby$0 AuthKit
10,000$0 Hobby$0 AuthKit
25,000$0 Hobby$0 AuthKit
50,000$0 Hobby$0 AuthKit
100,000$1,025 Pro$0 AuthKit
250,000$3,725 Pro$0 AuthKit
1,000,000$17,225 Pro$0 AuthKit

From each vendor's pricing page: Clerk, WorkOS.

Who moves from one to the other

Public pull requests on GitHub since Oct 2024 whose title says "Clerk to WorkOS" or the reverse — real code changes, by developers in general rather than makers only.

WorkOS → Clerk4 PRs
All matching pull requests on GitHub ↗
Clerk → WorkOS6 PRs
All matching pull requests on GitHub ↗

What makers say

Makers on using it for authentication, from Product Hunt and Starter Story interviews, each linked to the source. Products with a page of their own and fuller notes first.

On Clerk
I would ship as fast if I wasnt using Clerk. I use it for all my products, has a good free tier and it's customisation is so advanced as you want it to be, su all scenario's are achievable. Su
Indie Hacker Stacks, the makerSep 2026 ↗
I needed sign-in that worked and looked good without me building it from scratch. Clerk gave me Google auth, user management, and a polished UI out of the box. Took maybe an afternoon to integrate
Roll, the makerSep 2026 ↗
Login had to work on the website and in the mobile app with the same account. Clerk just did it. The account deletion webhook was also less painful than I expected.
WaseiGo, the makerSep 2026 ↗
74 more on the Clerk page →
On WorkOS
We chose WorkOS because it's straightforward to integrate and easy to work with. It let us add the features we needed without unnecessary complexity.
Velo, the makerSep 2026 ↗
WorkOS made it extremely easy for us to add auth to our ActionKit playground - we also use them for SSO for our core product as well.
Paragon, the makerSep 2026 ↗
Querri is built for everyone, including the enterprise. WorkOS gives us fast, robust and secure authentication that we love.
Querri, the makerSep 2026 ↗
9 more on the WorkOS page →

Loved and watch-outs

Themes that recur in makers' words and Hacker News comments, each linked to what it summarises.

Clerk
Most loved
  • Sign-up, sign-in, sessions and social login get wired in an afternoon instead of a sprint. PHPH 2
  • Organizations, roles and billing come built in, covering multi-tenant B2B apps without custom identity work. PHPH 2
  • Prebuilt UI components, including profile and settings pages, look polished out of the box. PH
Watch-outs
  • Outsourcing auth means a Clerk outage or account problem locks your users out, and the dependency is hard to reverse. HNHN 2HN 3HN 4
  • Costs climb with SSO, MFA, passkeys and branding removal, and some switched to cheaper open-source options. HNHN 2HN 3HN 4
On Product Hunt: 5.0★, 115 reviews · mentioned most: easy integration, comprehensive solution, free tier
WorkOS
Most loved
  • Enterprise SSO, SAML and SCIM directory sync arrive ready-made, integrated in weeks instead of months, so teams can close enterprise deals. PHHN
  • Organization separation and B2B features come built in alongside standard social login. PH
  • The free tier is permissive, and it works well even for B2C apps that skip enterprise features. HNHN 2HN 3
Watch-outs
  • When WorkOS has an outage, logins fail for every app that depends on it. HNHN 2
  • SCIM integrations have broken for customers, and it withholds SAML and SCIM configs and password hashes, creating hard lock-in. HN
  • Pricing is confusing and gets expensive as enterprise connections grow. HNHN 2
On Product Hunt: 5.0★, 21 reviews · mentioned most: easy authentication integration, quick onboarding, enterprise-level security

Who uses each

What makers pair each with

With Clerk
SupabaseBundled with your backendApps already on Supabase — auth is part of the same project as the database.vs Clerk →vs WorkOS →
FirebaseBundled with your backendMobile and client-heavy apps already using Firebase.
Better AuthLibrary in your appTypeScript apps that want users and sessions in their own database, at no cost.vs Clerk →vs WorkOS →
Auth0Hosted serviceComplex identity needs and enterprise compliance.vs Clerk →vs WorkOS →

Questions

Clerk or WorkOS: which do makers choose?

Of the 422 makers' products we know the authentication of, 336 chose Clerk (80%) and 20 WorkOS (5%). Among the 98 launched in 2026, Clerk is in 84% and WorkOS in 8%, against 76% and 3% of those launched in 2024 or earlier. On GitHub, 6 public pull requests moved projects from Clerk to WorkOS, and 4 the other way. Choose Clerk if you're on Next.js or React and want sign-in, profiles and teams working today; choose WorkOS if you sell to companies whose IT team will ask for SAML SSO or SCIM.

When should I pick Clerk over WorkOS?

Pick Clerk if: You're on Next.js or React and want sign-in, profiles and teams working today.

When should I pick WorkOS over Clerk?

Pick WorkOS if: You sell to companies whose IT team will ask for SAML SSO or SCIM.

Which is cheaper, Clerk or WorkOS?

At monthly active users 10k MAU: Clerk $0/mo (Hobby), WorkOS $0/mo (AuthKit), at list prices.

How do Clerk and WorkOS compare in cost as you grow?

Both cost $0 up to 50k MAU; from 100k MAU WorkOS costs less ($0 vs $1,025); and still does at 1M MAU ($0 vs $17,225). Cheapest usable plan at each scale, at list prices.

Are people switching from Clerk to WorkOS?

Public GitHub pull requests since 2024-10-02: 6 from Clerk to WorkOS, 4 from WorkOS to Clerk.