Clerk vs WorkOS
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.
Which fits you
- 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.
- 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
| Used by | 305 makers' products · 11 open-source projects | 19 makers' products · 11 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 2024 | 4 from WorkOS | 6 from Clerk |
| Downloads | 2.1M/wk+50% vs npm | 2.9M/wk+109% vs npm |
| Pricing | Free tier by monthly active users; paid plans add features and seats. · paid from $25/mo | Free user-management tier; enterprise SSO and directory sync priced per connection. · paid from $125 per connection/mo |
| Free tier | Yes | Yes |
| Open source | No | No |
| Incidents, 90 daysfrom its status page | 13 (1 major) | 24 (11 major) |
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).
The numbers, plan by plan
| Monthly active users | Clerk | WorkOS |
|---|---|---|
| 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 |
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.
- Migrate auth from WorkOS to ClerkFRC4392/DeceptiveHours · 2026-07-07
- Migrate auth from WorkOS to Clerkdanielnogueira8/LinkedInViralPostsSwipeFile · 2026-05-20
- feat: Migrate auth from WorkOS to ClerkShimizu-Technology/cornerstone-payroll · 2026-02-24
- Refactor: Migrate from WorkOS to Clerk authflyweightdev/convex-paddle · 2026-02-09
- feat: migrate auth from Clerk to WorkOS AuthKitddelvalfraire/poc-workout-tracker · 2026-08-20
- feat(auth): migrate from Clerk to WorkOS AuthKitthefappybird/gallurio · 2026-06-13
- Migrate auth from Clerk to WorkOS + nav & pricing improvementshimayat-commits/growth-hub · 2026-05-16
- attempt to convert from clerk to workosNathanGrace/barely-my-sveltekit-template · 2026-03-29
- attempt to convert from clerk to workosdavis7dotsh/my-sveltekit-template · 2026-03-29
- feat: Migrate authentication from Clerk to WorkOS AuthKitZapdev-labs/zapdev · 2025-11-28
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.
The team loves Clerk for its intuitive interface, seamless integration, and efficient management of administrative tasks, allowing them to focus on building groundbreaking solutions.
We used Clerk for account management. Building an authentication infrastructure from scratch is challenging, but by using Clerk’s abstracted API, we were able to simplify this process.
Nobody wants to worry about authentication or build their own system. Clerk allowed me to simply integrate them into my project and immediately feel confident in the security of my site.
We use WorkOS for the enterprise identity pieces of Harden, so customers can get the access controls they need without us building that layer from scratch.
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.
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.
Loved and watch-outs
Themes that recur in makers' words and Hacker News comments, each linked to what it summarises.
- 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
- 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

