Our judgment on Clerk vs Auth0: Clerk is a hosted auth service priced per monthly retained user, and its own security page says it has no EU region. Auth0 prices per monthly active user in tiers and lets you create a tenant in Europe. If a customer contract says identity data must stay in the EU, that settles the first round before price comes up.
Prices below are as listed on 15 October 2026, read from each vendor's own pages. Neither pricing page shows a date, so check again before you sign. Auth is one of several stack calls a founder makes early, and Hire developers by tech stack: rates, vetting and interview guides covers the others.
Which one for your situation?
These picks are judgment, not measurements.
| Situation | Pick | Why |
|---|---|---|
| A customer contract requires EU-resident identity data | Auth0, after checking | Clerk says it offers no region selection; Auth0 lets you create a tenant in the EU locality |
| Many enterprise customers, each with their own SSO | Compare at list price | Both charge per extra connection, at different rates and with different included counts |
| B2C app with a large base of free users | Clerk, if retained-user counting suits you | 50,000 monthly retained users on the free plan against Auth0's 25,000 monthly active users, defined by each vendor |
| Small team that wants login working this week | Clerk | Our reading, not from the pages cited: Clerk markets React and Next.js SDKs; check its docs |
| You want to configure auth around OIDC and SAML standards | Auth0 | Our reading, not from the pages cited: Auth0 is oriented around OIDC and SAML; check its docs |
What do the free tiers and base plans cost today?
Clerk's pricing page lists Hobby as free, with 50,000 monthly retained users (MRU) per app. Pro is $25 a month ($20 on annual billing) and includes 50,000 MRU. Business is $300 a month ($250 annual). Enterprise is custom and annual only. Past the included amount, overage is $0.02 per MRU from 50,001 to 100,000, $0.018 up to 1 million, $0.015 up to 10 million and $0.012 above that.
Auth0's pricing page lists a Free plan with up to 25,000 monthly active users (MAU), 1 enterprise connection, 5 Organizations and 1 day of log retention. The B2C plans are Essentials at $35 and Professional at $240 a month, each at a starting price for 500 MAU. The B2B plans are Essentials at $150 and Professional at $800. Yearly billing is priced at 11 times the monthly figure.
The units have different names, monthly retained user and monthly active user, and the pricing pages read don't define them in the text checked. Don't divide a plan price by a user count and compare the two. Read each vendor's definition against your own login pattern first.
A worked example, labelled as arithmetic from Clerk's own tier prices: a Pro app with 80,000 MRU has 30,000 over the included 50,000. At $0.02 each that's $600 of overage, so $625 a month with the $25 base. We won't do the same sum for Auth0, because its tiers depend on the plan and the MAU definition, and we'd be guessing.
Older figures of 10,000 free users for Clerk and 7,500 for Auth0 circulate on some comparison pages; the vendors' pages today show 50,000 MRU and 25,000 MAU.
Where does each store your EU users' data?
Clerk's answer is the plainest one in this comparison. Its security page says: "Clerk does not offer regional data residency or region selection." The page describes hosting on US infrastructure, Google Cloud and Cloudflare, with all subprocessors in the USA.
Clerk's Data Processing Addendum, updated 26 November 2024, fills in the legal side. Clause 4.4 allows processing "anywhere Clerk or its Sub-processors maintain facilities". Transfers out of the EU rely on Clerk's self-certification under the EU-US Data Privacy Framework (clause 11.2), with Standard Contractual Clauses as the fallback (clause 11.1). It names VeraSafe in Ireland as the EU representative.
Auth0 gives you a choice. Its tenant documentation lists localities for AU, CA, EU, JP, UK and US, and says localities "control the assigned tenant domain" and set "the region where your data will be hosted". The endpoints page lists the pattern login.<locality>.auth0.com for AU, CA, EU, JP and UK, so Europe is login.eu.auth0.com. The public-cloud endpoints page names no cloud provider and no data-centre location for the EU, so you'll need to ask Auth0 for that detail. The docs we read don't say whether a tenant's region can be changed after creation, so check before you pick.
Is a Data Privacy Framework transfer good enough? Our judgment: it's a lawful transfer route, not residency. Whether your customers accept it is a question for your data protection officer, and this isn't legal advice. Our guide to GDPR when you outsource software development covers transfers and access in more depth. For the same region question on a database, see Neon against Supabase on EU regions.
What do SSO and SCIM cost once enterprise customers arrive?
This is where the bills diverge, and few comparison pages show it.
Clerk's Pro and Business plans each include 1 SSO connection and 1 Directory Sync connection per app. Extra connections cost $75 a month each from 2 to 15, $60 each from 16 to 100, and you contact sales above 100. The pricing page says Directory Sync billing starts on 1 January 2027.
Auth0's Free plan includes 1 enterprise connection. B2B Essentials includes 3 and Professional includes 5. Extra connections are $100 a month, or $1,100 a year, up to a maximum of 30. Inbound SCIM is listed on every plan. Private Deployment is an Enterprise add-on.
Illustrative arithmetic at list prices, for 10 connections, excluding plan base prices. On Clerk Pro, 1 is included and 9 extra at $75 come to $675 a month. On Auth0 B2B Essentials, 3 are included and 7 extra at $100 come to $700 a month. On Auth0 B2B Professional, 5 are included and 5 extra come to $500 a month. The gap between those figures is smaller than the gap between the base plans, so price your own connection count before you read much into either.
Compliance claims on the vendor pages
Clerk's security page, reviewed 17 August 2026, says it has held SOC 2 Type 2 since 6 May 2022 and offers HIPAA with a Business Associate Agreement on Enterprise. It also says Clerk is "not ISO 27001 certified", though its infrastructure providers are. If a buyer's questionnaire asks for ISO 27001 from every vendor in the chain, that line matters.
Auth0's pricing page says compliance certifications are included on all plans without naming them, and lists HIPAA/BAA and a FAPI-certified security profile as Enterprise add-ons. It does not name SOC 2 or ISO 27001, so get Auth0's current compliance documents from Auth0 directly.
Clerk vs Auth0 at a glance
| Criterion | Clerk | Auth0 |
|---|---|---|
| Pricing unit | Monthly retained user (MRU) | Monthly active user (MAU) |
| Free tier | Hobby, free, 50,000 MRU per app | Free, up to 25,000 MAU, 1 enterprise connection |
| Entry paid plan | Pro, $25 a month ($20 annual), 50,000 MRU | B2C Essentials $35 or B2B Essentials $150 a month |
| Extra SSO connection | $75 a month (2-15), $60 (16-100) | $100 a month ($1,100 a year), max 30 |
| SCIM | 1 Directory Sync connection included on Pro and Business; extras $75 (2-15) / $60 (16-100); Directory Sync billing starts 1 January 2027 | Inbound SCIM on every plan |
| EU data location | No regional residency or region selection; US infrastructure; DPF with SCCs fallback | EU locality available for a tenant; provider and data-centre location not named on Auth0's create-tenants and public-cloud endpoints pages |
| Private or dedicated deployment | Not mentioned on Clerk's pricing and security pages | Private Deployment, Enterprise add-on |
| Compliance on vendor page | SOC 2 Type 2, HIPAA with BAA on Enterprise, not ISO 27001 | Certifications included on all plans, unnamed; HIPAA/BAA and FAPI as Enterprise add-ons (pricing page) |
Lock-in and who owns auth on your team
No market figures here, only judgment.
Auth is one of the stickiest choices in a stack, because users, sessions and credentials live there. On exit you have to move user IDs, active sessions and password hashes without forcing everyone to reset. Ask each vendor in writing what an export contains, in what format, before you build on it. Neither vendor's pricing page, nor the other pages cited here, says what an export contains.
Our judgment, not drawn from the vendor pages read: the products pull your code in different directions. Clerk is led by its front-end SDKs, and the auth logic sits close to your UI. Auth0 is led by protocols: OIDC, SAML, and rules and actions that customise the flow. That suits a team with a backend engineer who wants to shape claims and tokens.
The practical question is who maintains it after the founder who chose it. A front-end-led setup tends to belong to whoever owns the app shell. A protocol-led setup needs someone comfortable with token flows. Name that person before you sign. If you pair a React or Next.js front end with a host, Vercel and Netlify EU regions raises the same data-location question for hosting.
What this means for choosing an auth provider
Make three decisions before you compare features.
First, does any customer contract require EU-resident identity data? If it does, Clerk's own security page rules it out today, and the check becomes Auth0's EU tenant: which provider and data centre sit behind it, and whether the region can be changed later. If nothing requires it, Clerk's Data Privacy Framework route may be acceptable to your DPO, so ask them.
Second, how many enterprise SSO and SCIM connections will you sell in the next two years? Price that count at list rates for both, as in the 10-connection sum above.
Third, who owns auth once the person who set it up moves on?
Enterprise buyers will ask where identity data lives, so rehearse the answer by reading up on answering a customer's security questionnaire about sub-processors and vendors.
Hiring React engineers through HighCircl
The engineers who wire up either provider are React and Node engineers, and React is on our stack list. We send a shortlist of 3-5 vetted candidates within 72 hours, from four vetting stages that about 10% of applicants pass. There's no recruitment fee, our margin is 20% and capped, and a replacement guarantee applies if the engagement isn't working. We work with talent in 7 European countries (6 EU plus Serbia), and GDPR is native for EU member states. See hiring React engineers through HighCircl.
FAQ
Which is better, Clerk or Better Auth?
They're different kinds of product, and we didn't read Better Auth's own pages for this article. As a general frame, our judgment: a hosted service such as Clerk takes on running login for a monthly fee and ties you to its data location and pricing. A self-hosted library puts the code, the database and the upgrades in your hands. Pick the library if you have an engineer who will own auth, and the hosted service if you don't.
Who are Auth0's main competitors?
Clerk is the one this article compares. By category, the others are self-hosted auth libraries and the auth bundled into a database platform. We haven't read other vendors' pages, so we won't compare their prices or features here.
Does Clerk store data in the EU?
No, according to Clerk's security page: it "does not offer regional data residency or region selection". Data is hosted on US infrastructure, and EU transfers rely on the Data Privacy Framework, with Standard Contractual Clauses as the fallback under its DPA. Whether that satisfies a given customer is a question for your DPO.
Is Auth0's free plan enough?
Our judgment: for a prototype, yes. The Free plan covers up to 25,000 monthly active users and 1 enterprise connection, per Auth0's pricing page. It also has 5 Organizations and 1 day of log retention. A second enterprise SSO customer means moving to a paid B2B plan, which includes 3 (Essentials) or 5 (Professional) connections and sells extras at $100 a month each.
What are alternatives to Clerk?
By category: Auth0 as the other hosted option, a self-hosted auth library if you want to own the code and data location, and the auth bundled with a database platform. Judge each on region, pricing unit and per-connection SSO cost, the same three checks used above.