Clerk Alternatives
Seven Clerk alternatives for sign-in, user management and enterprise SSO, compared on what 100,000 users really cost, who holds your user table and how hard the move is.
Clerk is free up to 50,000 monthly retained users per app, then Pro costs $25 a month plus $0.02 per extra user, and each SSO connection after the first adds $75 a month. Our picks: Better Auth if you want the user table in your own database under an MIT license; WorkOS AuthKit if you sell to companies and need free user management up to 1 million users; Supabase Auth if your app already runs on Postgres. Auth0, Firebase Authentication, Amazon Cognito and Keycloak cover enterprise depth, Google and AWS stacks, and full self-hosting.
The ranking is editorial: a sponsored placement is always flagged on its card, and no affiliate link changes a score.
Why teams leave Clerk
Clerk is very good at what made it popular: drop-in sign-in components for React and Next.js, a user dashboard and organizations that work on day one. Teams rarely leave because it breaks. They leave because the bill grows with users and SSO connections, because the user table lives on Clerk's US servers, or because they want auth to be a library they own instead of a service they rent. Here are the reasons we found on Clerk's own pricing, security and migration pages, and in developer threads from 2026.
The bill follows your retained users
MFA and your own branding need Pro
Each extra SSO connection is $75 a month
Organizations stop at 20 members without an add-on
No region choice for user data
Compliance paperwork sits on the top plans
The SDK goes deep into your app
Better Auth
Better Auth is an authentication framework for TypeScript, released under the MIT license. It is not a hosted service: you install it in your app, point it at your own database, and it creates the user, session and account tables there. It covers 2FA, passkeys, multi-tenancy, multi-session support and enterprise SSO, and an Organization plugin handles teams. Because the code runs inside your app, there is no monthly user meter: 100,000 users cost what your database costs.
Why it ranks first: it removes the two things people leave Clerk for, the per-user bill and the user table on someone else's servers. It also ships an official Clerk migration guide that reads Clerk's CSV export, keeps user IDs and bcrypt passwords and carries TOTP secrets over. A paid layer exists for teams that want it: Pro at $20 a month adds unlimited dashboard seats, 20,000 audit logs a month instead of 10,000, abuse protection, and self-service SSO and Directory Sync with one connection included, then $50 a month per connection.
The limit: you run auth yourself. Email delivery, security patches, session storage and tuning the built-in rate limiter are your job, and the hosted dashboard is a separate infrastructure plan (Starter free with one seat, Pro $20 a month).
- MIT license, user data in your own database
- No per-user pricing on the library
- Official Clerk migration guide
- ✓Teams that want zero per-user cost
- ✓Apps that need data in a chosen region
- ✓Developers comfortable owning auth code
- ✗You maintain security updates and email sending
- ✗Sign-in screens are yours to build
- ✗Organizations are not covered by the Clerk migration script
| Criterion | Better Auth | Clerk |
|---|---|---|
| Pricing unit | None (your database) | Monthly retained users |
| Extra SSO connection | $50/mo on Pro infrastructure | $75/mo |
| Where users live | Your database | Clerk's US cloud |
Pick Better Auth if owning the user table matters more than drop-in screens. If you need hosted pages and enterprise SSO without running anything, take WorkOS AuthKit.
WorkOS AuthKit
WorkOS started as an API for enterprise SSO and directory sync, and AuthKit is its user management layer: branded hosted sign-in pages, passwords, passkeys, MFA, social login, organizations with per-organization sign-in rules and role-based access control. Its setup installer detects and wires up Next.js, Laravel, TanStack Start, SvelteKit, Django and ten more frameworks.
Why it ranks here: user management is free up to 1 million monthly active users, then $2,500 a month per extra million. At 100,000 users the bill is $0, against $1,025 a month on Clerk Pro. WorkOS also publishes a Clerk migration guide and an MIT-licensed import tool, archived as read-only in 2026, that brings Clerk users in with their bcrypt password hashes, so nobody has to reset a password. If you are weighing WorkOS itself against similar B2B tools, our WorkOS alternatives page ranks Stytch, Kinde and Descope.
The limit: enterprise connections are what you pay for, and they cost more than Clerk's. Each SSO or Directory Sync connection is $125 a month from the first one up to 15, against $75 at Clerk with one included. Ten enterprise customers on SSO cost $1,250 a month at WorkOS and $700 at Clerk Pro. A custom domain for the hosted pages is $99 a month.
- Free user management up to 1 million users
- SAML SSO, SCIM and an admin portal for your customers' IT teams
- Clerk import tool that keeps passwords
- ✓B2B products moving upmarket
- ✓Apps with many free users and few enterprise accounts
- ✓Teams that want hosted, branded login pages
- ✗$125 a month per SSO connection, none included
- ✗Custom domain for AuthKit is $99 a month
- ✗SSO and Directory Sync both billed per connection
| Criterion | WorkOS AuthKit | Clerk |
|---|---|---|
| 100,000 users | $0 | $1,025/mo on Pro |
| SSO connection | $125/mo each | 1 included, then $75/mo |
| Hosted login pages | Yes, branded | Yes, components |
The best fit when users are many and enterprise customers are few. If most of your revenue comes from SSO accounts, compare the connection bill with Clerk before moving.
Supabase Auth
Supabase Auth is the authentication part of Supabase, the open-source Postgres platform. It handles passwords, magic links, one-time codes, social sign-in, phone sign-in through Twilio, MessageBird or Vonage, and SAML 2.0 SSO. Users live in a dedicated schema of your project's Postgres database, and the auth token scopes database access row by row through Row Level Security policies.
Why it ranks here: among the hosted services here that bill per user, it is the cheapest at scale (WorkOS stays free to 1 million users but bills every enterprise connection). Pro starts at $25 a month and includes 100,000 monthly active users, so 100,000 users cost $25 a month, and 1 million cost about $2,950. You pick the project region, including Frankfurt, Paris, Ireland or Stockholm, which answers the data residency question Clerk cannot. Teams new to the platform can start with our Supabase training, and teams outgrowing it can read our Supabase alternatives.
The limit: SAML SSO is billed per user, 50 included then $0.015 each, and not available on the Free plan, and Clerk's drop-in profile and organization screens have no direct equivalent to copy. Free projects pause after one week of inactivity, and SOC 2 and HIPAA need the Team plan, from $599 a month.
- 100,000 MAU included in the $25 Pro plan
- Users stored in your own Postgres
- Region choice, six in Europe
- ✓Apps already on Supabase
- ✓Teams that use row-level security
- ✓Budget-conscious consumer apps
- ✗Free projects pause after a week idle
- ✗SOC 2 and HIPAA from $599 a month
- ✗Enterprise SSO billed per SSO user
| Criterion | Supabase Auth | Clerk |
|---|---|---|
| 100,000 users | $25/mo | $1,025/mo |
| Data region | You choose | US only |
| Enterprise SSO | $0.015 per SSO user after 50 | $75/mo per connection |
The obvious move if your data is already in Supabase. For a B2B app with many enterprise SSO customers, WorkOS prices connections more predictably.
Auth0
Auth0, part of Okta, is the identity platform most security teams already know. It covers social, passwordless and enterprise logins, MFA and B2B organizations, on separate B2C and B2B price grids. Its free plan covers up to 25,000 monthly active users, five organizations and one custom domain.
Why it is here: when a buyer's security questionnaire asks for a mature identity vendor, Auth0 ends the discussion. Auth0 also runs a startup plan with 100,000 monthly external active users and enterprise identity providers. Yearly billing costs eleven times the monthly price, one month free.
The limit is price. Paid plans are sized by monthly active users: B2C Essentials starts at $35 a month and Professional at $240 a month for 500 users, B2B Essentials at $150 a month and B2B Professional at $800 a month for the same 500, and every step up in users moves you to a higher price. A Clerk team leaving because of cost rarely saves money here; teams already on Auth0 and looking for the exit will find options in our guide to switching from Auth0, and workforce identity on Okta is covered in switching from Okta.
- 25,000 MAU and 5 organizations free
- Self-service SSO and SCIM on the free plan
- Okta's security and compliance track record
- ✓Teams facing enterprise security reviews
- ✓Apps with custom login logic (Actions)
- ✓Startups eligible for the startup plan
- ✗Paid plans start at 500 users
- ✗B2B Essentials from $150 a month
- ✗Pricing climbs steeply with MAU
| Criterion | Auth0 | Clerk |
|---|---|---|
| Free plan | 25,000 MAU | 50,000 MRU |
| Entry paid plan | $35/mo for 500 MAU | $25/mo for 50,000 MRU |
| B2B entry | $150/mo | $25/mo + $100 add-on |
Choose Auth0 for enterprise requirements, not to cut the auth bill. If price drove you away from Clerk, WorkOS or Supabase will cost less.
Firebase Authentication
Firebase Authentication is Google's sign-in service for apps built on Firebase. It supports email and password, social providers, phone numbers, anonymous users and, once upgraded to Identity Platform, SAML and OpenID Connect. Its client SDKs cover iOS, Android, Flutter and the web.
Why it is here: price per user. The first 50,000 monthly active users are free, then $0.0055 each up to 100,000 and $0.0046 up to 1 million. At 100,000 users the bill is $275 a month; at 1 million, about $4,415. Anonymous users are not counted if automatic clean-up is enabled.
The limit: SAML and OIDC sign-ins are free for 50 users only, then $0.015 each, so B2B SSO gets expensive. Phone sign-in bills every SMS at the country's rate, after ten free a day. Members, roles and an admin portal for your customers' IT teams are yours to build, and the user table stays in Google's cloud. Moving the rest of a Firebase app is covered in our guide to switching from Firebase.
- 50,000 MAU free
- Strong mobile SDKs
- Anonymous sign-in for guest users
- ✓Mobile-first consumer apps
- ✓Teams already on Firebase or Google Cloud
- ✓Apps with guest-to-account flows
- ✗B2B member and role logic is yours to build
- ✗SAML/OIDC $0.015 per user after 50
- ✗SMS cost varies by country
| Criterion | Firebase Authentication | Clerk |
|---|---|---|
| 100,000 users | $275/mo | $1,025/mo |
| Enterprise SSO | $0.015 per user after 50 | $75/mo per connection after the first |
| Free tier | 50,000 MAU | 50,000 MRU |
Good value for a consumer or mobile app on Google's stack. For B2B organizations and SSO, look at WorkOS or Auth0 instead.
Amazon Cognito
Amazon Cognito is the user directory and sign-in service of AWS. User pools handle sign-up, sign-in, social and SAML or OIDC federation, and issue tokens your API Gateway routes can check. It sells three tiers: Lite, Essentials with managed login, passkeys and email one-time codes, and Plus with risk-based adaptive authentication and compromised credentials detection.
Why it is here: low cost and AWS integration. The Lite and Essentials tiers include 10,000 monthly active users free per account; above that Lite costs $0.0055 per user up to 100,000, and Essentials $0.015. At 100,000 users Lite comes to $495 a month and Essentials to $1,350. The user pool lives in the AWS region you pick, which solves residency for European teams.
The limit: developers describe Cognito as complex, with configuration spread across user pools, app clients and IAM. Plus has no free tier at $0.02 per user, and federated SAML users are free for 50 only. Managed login is customizable, but it is a hosted page, not React components.
- 10,000 MAU free per account
- Region of your choice
- Passkeys and email codes on Essentials
- ✓AWS-native backends
- ✓Teams billing everything through AWS
- ✓Apps needing a specific AWS region
- ✗Steep setup and configuration
- ✗Plus tier has no free allowance
- ✗Configuration spread across pools, clients and IAM
| Criterion | Amazon Cognito | Clerk |
|---|---|---|
| 100,000 users | $495/mo (Lite) | $1,025/mo |
| Data region | Any AWS region | US only |
| Setup effort | High | Low |
Sensible when your backend already lives on AWS and cost matters most. For a polished front-end experience, Supabase Auth or WorkOS are easier.
Keycloak
Keycloak is an open-source identity and access management server, licensed under Apache 2.0 and an incubating project of the Cloud Native Computing Foundation. It provides single sign-on, identity brokering with OpenID Connect and SAML 2.0 providers, user federation with LDAP and Active Directory, and an admin console. You run it yourself, on a VM, in Docker or on Kubernetes.
Why it is here: it is the reference when identity must stay on your own infrastructure. There is no license fee and no user meter, so a million users cost only the servers that run it. It speaks SAML and OIDC to your customers' identity providers with no per-connection fee.
The limit: Keycloak is an identity server, not a set of React components. Theming the login pages, upgrades, high availability and backups are on your team, and support comes from the community unless you buy a commercial distribution. For a small product team leaving Clerk for price reasons, the operations cost usually outweighs the savings. Lighter self-hosted servers such as authentik and Zitadel are ranked in our Keycloak alternatives.
- Apache 2.0, no user or connection fees
- SAML, OIDC, LDAP and Active Directory built in
- Runs anywhere you host it
- ✓Regulated organizations
- ✓Teams with existing ops capacity
- ✓Apps that must federate with corporate directories
- ✗You run, scale and patch it
- ✗Login theming is work
- ✗Community support unless you buy a commercial build
| Criterion | Keycloak | Clerk |
|---|---|---|
| License | Apache 2.0 | Proprietary service (MIT SDKs) |
| SSO connection | No fee | $75/mo after the first |
| Hosting | Yours | Clerk's US cloud |
The right answer when identity cannot leave your servers. If you only want to own your user data, Better Auth gets you there with far less operations work.
Clerk alternatives compared
The seven alternatives side by side. The distinctive column is the monthly bill for 100,000 active users on each vendor's published grid, before SSO connections and add-ons; Clerk Pro comes to $1,025 for the same volume.
| Best for | Cost at 100,000 users | Free plan | Team size | Visit | ||||
|---|---|---|---|---|---|---|---|---|
| 1 | Better Auth | Best to own your user table | $0 (your database) | 4.3/5 | Free (MIT) | ✓ | TypeScript teams | Visit → |
| 2 | WorkOS AuthKit | Best for B2B SaaS | $0 | 4.3/5 | Free to 1M MAU | ✓ | B2B SaaS | Visit → |
| 3 | Supabase Auth | Best on Postgres | $25 | 4.3/5 | Free; Pro $25/mo | ✓ | Startups | Visit → |
| 4 | Auth0 | Best for enterprise depth | Sized by MAU, enterprise quote | 4.0/5 | Free; from $35/mo | ✓ | Mid-market, enterprise | Visit → |
| 5 | Firebase Authentication | Best for mobile on Google Cloud | $275 | 3.9/5 | Free to 50K MAU | ✓ | Mobile apps | Visit → |
| 6 | Amazon Cognito | Best on AWS | $495 (Lite) | 3.9/5 | Free to 10K MAU | ✓ | AWS backends | Visit → |
| 7 | Keycloak | Best for self-hosting | $0 plus your servers | 3.6/5 | Free (Apache 2.0) | ✓ | Regulated orgs | Visit → |
Is your tool missing from this page? Email us: hello@hackceleration.com
Which Clerk alternative for which case
No user meter: the library is MIT and free.
You sell to enterprises that ask for SAML and SCIMWorkOS AuthKitFree to 1 million users, $125 per connection.
Your data already lives in PostgresSupabase Auth100,000 MAU in the $25 Pro plan.
A security review demands an established vendorAuth0Okta's platform, free to 25,000 MAU.
You ship a mobile app on FirebaseFirebase Authentication50,000 MAU free, strong mobile SDKs.
Your backend runs on AWSAmazon Cognito10,000 MAU free, any AWS region.
Identity must stay on your own serversKeycloakApache 2.0, SAML, OIDC and LDAP.
How to choose a Clerk alternative
Clerk belongs to the authentication and user management category, sometimes called CIAM (customer identity and access management). A tool in this category does four jobs. It signs users in, with passwords, magic links, one-time codes, passkeys or social accounts. It keeps a session alive, usually with a short-lived token your backend checks on each request. It stores the user table: emails, password hashes, MFA secrets, profile fields. And for B2B apps it groups users into organizations and connects them to their employer's identity provider through SAML or OIDC single sign-on, with SCIM directory sync to add and remove employees automatically.
Alternatives come in three shapes. Hosted services (WorkOS, Auth0, Firebase, Cognito, Supabase) run everything and bill you per user or per connection. Libraries (Better Auth) run inside your own app and write to your own database. Identity servers (Keycloak) you deploy and operate yourself. The shape decides who is on call when sign-in breaks.
Before comparing prices, learn the meter. A monthly active user (MAU) is anyone who signed in or refreshed a session that month; Auth0, Firebase, Cognito, Supabase and WorkOS count MAU. Clerk counts monthly retained users instead, which skips people who never come back after their first day. A connection is one customer's identity provider linked for SSO or SCIM; Clerk, WorkOS and Better Auth's infrastructure plan bill connections, Supabase, Firebase and Cognito bill each SSO user. Price your app on both meters: active users per month, and enterprise customers on SSO.
Then check five things. Who holds the user table and in which region. Whether you can export password hashes, so users keep their passwords after the move. Which plan carries MFA, SOC 2 reports and a HIPAA BAA. What the prebuilt UI covers for your framework. And what the vendor charges for SMS, because phone codes are billed per message almost everywhere. For workforce SSO across your own company's tools, our SSO and IAM ranking is the better starting point; for a full backend with auth included, see the backend-as-a-service ranking.
Other names come up in Clerk comparisons, and we left them off the ranking because each overlaps a tool above. Stytch is a hosted B2B rival to WorkOS: 10,000 monthly active users free, 5 SSO or SCIM connections included, then $125 per connection. Descope sells its Flows builder with a free tier of 7,500 users and Pro from $249 a month billed annually. SuperTokens charges $0.02 per user on its cloud, free under 5,000, and can be self-hosted like Better Auth. Ory publishes open-source servers and sells its hosted Network from $770 a year on the Production plan.
Five pricing traps the other guides miss
Some guides still quote Clerk's old grid
A comparison published in 2026 still says Clerk is free for 10,000 users and bills per MAU. The current grid is 50,000 monthly retained users free per app, then $0.02 each on Pro. Redo any cost comparison on today's numbers: at 30,000 users, Clerk Hobby costs $0, while Auth0 Free stops at 25,000 MAU.
SSO is cheap at Clerk and dear at WorkOS
WorkOS gives away users and charges connections: $125 a month each from the first. Clerk does the opposite: one connection included, then $75. With three enterprise customers, Clerk Pro costs $175 a month and WorkOS $375; with 100,000 users and no SSO, Clerk costs $1,025 and WorkOS $0. Count both before choosing.
Per-user SSO billing at Supabase, Firebase and Cognito
These three bill each user who signs in through SAML or OIDC: $0.015 a month after 50 free. One enterprise customer with 2,000 employees signing in costs about $29 a month at Supabase or Firebase, against a flat $125 connection at WorkOS. Large customers flip the math.
Cognito's Plus tier has no free allowance
Lite and Essentials include 10,000 monthly active users per account; Plus, which adds threat protection, bills from the first user at $0.02. Switching a pool to Plus for one security feature turns a $0 test project into a real bill.
Supabase's free projects fall asleep
A free project is paused after one week of inactivity, and only two free projects can be active. Fine for a prototype; for a production app, budget the $25 Pro plan from launch, which still includes 100,000 monthly active users.
How to move off Clerk without resetting passwords
Export users from the Dashboard, not the API
Only the Clerk Dashboard export contains password digests and TOTP secrets; the Backend API never returns password hashes. A workspace admin downloads it as a CSV from the instance settings. No export includes MFA backup codes, so plan to issue new ones.
Check that the target accepts bcrypt
Clerk hashes passwords with bcrypt. WorkOS's import tool creates users with their bcrypt hash. Better Auth uses scrypt by default, so you enable bcrypt verification before importing. Without this step, every user gets a password reset email.
Map organizations separately
User import scripts rarely carry organizations, roles and memberships, and Better Auth's Clerk migration script leaves them out. Export organizations through Clerk's Backend API and recreate them with their member roles before switching sign-in.
Run both systems for a short overlap
One team that moved from Clerk to Better Auth in 2026 accepted both session cookies on every endpoint for two weeks; users switched over when they next signed in. It avoids a single day where everyone is logged out.
Replace components and middleware last
Swap Clerk's sign-in components, middleware and user hooks route by route, and keep Clerk installed until the last route has moved. Check webhooks too: anything that listened to Clerk's user events must listen to the new provider, including automations built on Clerk with Zapier.
Clerk alternatives · FAQ
Is Clerk open source?
Partly: Clerk's JavaScript SDKs are published on GitHub under the MIT license, but the authentication service they call is Clerk's hosted, proprietary backend. You can read and fork the client code, not run Clerk yourself. If you want the server side open too, Better Auth (MIT) and Keycloak (Apache 2.0) are the open-source options in this comparison.
What happens when I pass 50,000 users on Clerk's free plan?
You must move to Pro, and Clerk gives a one-month grace period so the app keeps working while you upgrade. Past 100 retained organizations, you also need the B2B add-on. Only users who come back at least one day after signing up count, so a launch spike of one-time visitors rarely triggers the limit.
How does Clerk bill organizations?
By monthly retained organization: an organization with at least two members, at least one of them a retained user that month. 100 are included per app, then $1 each up to 1,000, $0.90 up to 10,000 and $0.75 up to 100,000. Single-member workspaces are never billed, which suits apps where most accounts are solo.
Is Clerk HIPAA compliant?
Clerk says it has been HIPAA certified since 2022, but the Business Associate Agreement a covered entity needs is only available on the Enterprise plan, on a quote. Among the alternatives, Supabase sells HIPAA as a paid add-on on its Team plan, from $599 a month, and self-hosted Keycloak leaves compliance to your own infrastructure.
Does Clerk have a startup discount?
Yes, through partners such as Stripe Atlas, Y Combinator, South Park Commons and OnDeck, for companies up to one year after launch and with up to $5 million in venture funding. Auth0 runs its own startup plan with 100,000 monthly external active users, worth comparing if enterprise SSO is on your roadmap.
Which Clerk alternative keeps user data in the EU?
Supabase and Amazon Cognito let you pick the region: Supabase offers Frankfurt, Paris, Ireland and Stockholm inside the EU, plus London and Zurich outside it, and a Cognito user pool lives in the AWS region you create it in. Better Auth and Keycloak store users wherever your own database or servers run.
Will my users be logged out when I leave Clerk?
Usually yes, once: sessions do not carry over, and Better Auth warns that moving from Clerk invalidates all active sessions. Passwords can survive if you import the Dashboard export's bcrypt hashes. Accepting both providers' cookies for a short overlap lets users switch at their next sign-in instead of all at once.
How much does SMS sign-in cost with Clerk and its alternatives?
Clerk charges $0.01 per SMS in the US and Canada and the market rate elsewhere. Firebase and Google Identity Platform bill each SMS at the destination country's rate after ten free a day, and Better Auth's infrastructure plan charges $0.09 per SMS. Passkeys or email codes avoid the per-message cost entirely.
Get the next breakdown in your inbox
New software comparisons with checked pricing, once in a while.