Clerk has no EU region: it hosts user data in the US and transfers EU data under the Data Privacy Framework. European-hosted alternatives include ZITADEL (Swiss-founded; Frankfurt or Zurich), Hanko (Germany), Logto (Netherlands region), Kinde (Dublin region) and self-hosted Keycloak or Better Auth. Our product, tiun, is Swiss and bundles sign-in with merchant-of-record billing.
A European region is only part of the answer. Every managed provider in our table, us included, runs at least partly on a cloud owned by a US company. The table shows who you contract with, the cloud underneath, whether the region can change, and which products also handle billing.
Clerk hosts user data in the US
Clerk's security page (last reviewed 17 August 2026) says Clerk "does not offer regional data residency or region selection". It says data is hosted on US infrastructure (Google Cloud and Cloudflare) with all sub-processors in the USA, and that EU, UK and Swiss personal data is transferred to the US under the Data Privacy Framework (DPF). Clerk's DPA (26 November 2024) keeps Standard Contractual Clauses as a fallback for as long as Clerk cannot rely on the DPF (§11.1).
The DPF is valid today. The EU General Court dismissed Philippe Latombe's challenge (T-553/23) on 3 September 2025, and his appeal (C-703/25 P, lodged 31 October 2025) is pending at the Court of Justice. A second challenge is threatened: after the US Supreme Court ruled in Trump v. Slaughter (29 June 2026) that the President can remove FTC commissioners at will, the privacy group noyb asked the European Commission to withdraw the DPF, which relies on FTC enforcement, and said it would sue. As of late October 2026, noyb had not yet filed.
If the Court invalidates the DPF, as it invalidated Privacy Shield in 2020, providers that rely on it for US transfers will have to switch to another mechanism, such as the SCCs Clerk already names as its fallback. This applies to every provider with DPF-certified US sub-processors, us included, not only to Clerk.
Clerk and 9 alternatives compared
Every managed option in this table with a European region runs on Google Cloud, AWS or Microsoft; Hanko's DPA also lists two German companies, Hetzner and adesso as a service. Within this table, only self-hosting lets you avoid a US-owned cloud entirely.
Provider | Contracting entity (country) | Managed European regions | Cloud underneath (owner) | Region fixed? | Self-host | Billing for your customers | Sources (checked 16 Nov 2026) |
|---|---|---|---|---|---|---|---|
Clerk | Clerk, Inc. (US) | None; US only | Google Cloud + Cloudflare (US) | No region option | No | Clerk Billing: Stripe only, 0.7% on top of Stripe fees, USD only, no tax or VAT, not a merchant of record | security.md (reviewed 17 Aug 2026), billing overview, pricing |
ZITADEL | CAOS AG, St. Gallen (CH), a subsidiary of Zitadel, Inc. (US); US enterprise customers contract with Zitadel, Inc. | Google Cloud europe-west3 (Frankfurt) or europe-west6 (Zurich) | Google Cloud (Google, US) | Yes, set at creation; moving means export and re-import into a new instance | Yes (open source) | No | contracting entities (25 Jun 2026), data location (19 Oct 2026), region change, DPA (8 May 2025) |
Hanko | Hanko GmbH, Kiel (DE) | Germany only: the DPA commits to German data centres; the pricing page says AWS Frankfurt | AWS (Amazon, US); the DPA also lists Hetzner (DE) | Germany only, no choice | Yes (open source) | No | |
Logto | Silverhand Inc. (Delaware, US) | Europe (Netherlands) | Microsoft Azure + Cloudflare (US) | Yes, fixed at tenant creation | Yes (open source) | No | tenant settings, terms, DPA (24 Nov 2025) |
Kinde | Kinde Australia Pty Ltd (AU); Kinde also lists a UK company number | Europe (Dublin); UK (London) | AWS (Amazon, US) | Yes, fixed at signup | No | Kinde billing on Stripe Billing; you set up tax collection yourself | data regions, sub-processors (11 Aug 2025), billing |
Auth0 | Okta, Inc. (US) | Public Cloud: EU region and a separate UK region. Private Cloud (enterprise): dedicated deployments in several European countries, including Switzerland | AWS (Amazon, US); Microsoft Azure (US) for some Private Cloud | Yes, set at tenant creation; Auth0 won't transfer data between tenants | No (Private Cloud is run by Okta) | No | Okta sub-processors (May 2026), data transfer policy |
Supabase Auth | Supabase Pte. Ltd. (Singapore); Supabase, Inc. (Delaware, US) for AWS Marketplace purchases | EU: Frankfurt, Ireland, Paris, Stockholm. Outside the EU: Zurich, London | AWS (Amazon, US) | Yes, bound to the project; moving means a new project | Yes (open source) | No; you add a payment provider yourself | |
Keycloak | Open-source project (CNCF incubating) | Wherever you deploy it | You decide | You decide | Yes; no official managed service | No | |
Better Auth | Open-source TypeScript framework (MIT); the managed add-ons are sold by Better Auth Inc., owned by Vercel Inc. (US) since July 2026 | Wherever your app and database run, unless you use the managed add-ons | You decide | You decide | Yes (runs inside your app) | Better Auth's own Stripe plugin (you are the seller); Polar's plugin (Polar is the merchant of record) | GitHub, pricing, Vercel announcement (7 Jul 2026), Stripe plugin, Polar plugin |
tiun | tiun AG, Zurich (CH) | No region setting; our DPA says we process data primarily in Switzerland and the EEA (§8.1) | Microsoft (via Microsoft Ireland Operations Ltd; owner Microsoft Corp., US) | No region setting | No | Yes: we are the merchant of record, with a built-in customer database | our legal docs (version 2026.9), sub-processor list (2 Sep 2026) |
Every managed provider also bills you for its own service. The billing column covers charging your customers.
Managed EU hosting or self-hosting on EU infrastructure
Keycloak, ZITADEL, Logto, Hanko, Supabase and Better Auth can all run on servers you rent from a European-owned host such as Hetzner (Germany), OVHcloud (France) or Scaleway (France). Hetzner and OVHcloud also have locations outside Europe, so choose a European one.
The price is the operations work. ZITADEL's own service description lists what a self-hosting customer takes on: infrastructure, DDoS and web-application-firewall protection, backups, and external services such as email (SMTP), SMS and domains. Add patching, uptime monitoring and incident response, and auth becomes a system your team runs around the clock.
Email and SMS deserve a second look in either model. Sign-in codes and password resets go through a delivery provider, which sees addresses, phone numbers and the messages themselves. Kinde's sub-processor list, for example, gives Australia as the location of its AWS email service unless you bring your own SMTP provider. The same check applies to us: Stytch, an authentication provider, and Loops, an email provider, are both on our sub-processor list, and both name US locations.
Managed hosting moves the operations work to the provider. What you give up is control over which company and which cloud sit under your user table.
A sovereignty test you can apply to every provider
Apply the same questions to every vendor, us included, and to the European brands as strictly as to the US ones.
Who is the company? Under the US CLOUD Act (18 U.S.C. §2713), a communications or cloud provider subject to US jurisdiction can be ordered to disclose data in its "possession, custody, or control", wherever the data is stored. Clerk and Okta (Auth0) are US companies, and so is Silverhand Inc., the Delaware corporation behind Logto. Better Auth's managed add-ons are sold by Better Auth Inc., which Vercel Inc., a US company, acquired in July 2026; the open-source framework you host yourself puts no vendor between you and your data.
Check the legal pages as well as the About page, and look for a parent company. ZITADEL's self-service cloud customers contract with CAOS AG in St. Gallen under Swiss law, but CAOS AG is owned by Zitadel, Inc. of San Francisco, which contracts with US enterprise customers itself (ZITADEL help centre, 25 June 2026). ZITADEL's DPA (8 May 2025) is between Zitadel, Inc. and its affiliates and the customer, and the same help article says that, because the parent is US-based, ZITADEL follows US regulatory requirements. Supabase's terms name Supabase Pte. Ltd. in Singapore, or Supabase, Inc. in Delaware for AWS Marketplace purchases. We are tiun AG, a Swiss company.
Whose cloud is it on? An EU region on Google Cloud, AWS or Microsoft fixes where the disks are. The company running them is an EU subsidiary of a US parent, and a CLOUD Act order can reach data the parent controls. That applies to every managed provider in the table, and to us: our host is Microsoft Ireland Operations Ltd, a Microsoft subsidiary. GDPR does not forbid US-owned clouds. It does require a processing agreement with each processor, a transfer mechanism for anything that reaches the US (remote support access included), and your own judgement that the provider can meet its GDPR duties. Whether that satisfies your customers is a separate question, and worth answering before you migrate.
Can the region change, and what leaves it? ZITADEL, Logto and Supabase fix the region when you create the instance, tenant or project, and Kinde fixes it when you sign up; moving means a new one plus a migration. Auth0 sets the region when you create a tenant and won't transfer data between tenants. Hanko Cloud runs only in Germany. Then read the exceptions:
ZITADEL says data in transit may travel outside the region if users access the service internationally, and its DPA says customer data may be processed outside Switzerland and the EU, including in the United States.
Okta's sub-processor list for Auth0 puts email (SendGrid), SMS (Twilio), analytics (Datadog) and support ticketing (Salesforce) in the USA, and its CDN (Cloudflare) is global.
Hanko's DPA makes the strongest commitment in the table: storage in German data centres and no access from outside the EEA, apart from access and transmissions the customer initiates or configures.
Supabase's regions page says region selection "is a data-location control, not proof of regulatory compliance", and its general "Europe" option can place a project in London or Zurich, so pick a specific EU region.
If you also need billing
Clerk and Kinde run billing on Stripe, which leaves you as the seller. You owe the VAT and sales tax on each sale: you register where the rules require it (in the EU, sellers based outside the EU owe VAT from the first consumer sale, and one One-Stop-Shop registration usually covers every member state), charge the right rate, issue the invoices and handle chargebacks.
Clerk Billing works only with Stripe, adds 0.7% on top of Stripe's fees and bills in USD only. It does not support tax or VAT, and Clerk is not the merchant of record. Clerk also says payments that need 3D Secure will fail, and that this "is particularly relevant in the UK and EU", where Strong Customer Authentication rules mean many card payments need 3D Secure (billing overview).
Kinde billing runs on Stripe Billing, on a new Stripe account Kinde creates for you; you can't currently connect an existing one. Tax collection is off by default; switching it on turns on Stripe Tax for new subscriptions.
Supabase has no billing product; you add a payment provider yourself.
Better Auth ships its own Stripe plugin, where you are the seller. Polar maintains a Better Auth plugin, and Polar acts as merchant of record.
We built tiun to bundle sign-in, a customer database and merchant-of-record billing in one SDK. For every transaction, tiun is the legal seller (MSA §4.1), and the buyer's contract is with tiun AG (Terms of Sale §1.4, §2.4). We calculate, collect and remit VAT and sales tax wherever we have determined that we must register, and we monitor thresholds and register in new jurisdictions when registration is triggered (MSA §8.1). In jurisdictions we exclude from coverage, we either block the sale or the tax stays with you (MSA §8.3). Your income, corporate and payroll taxes stay with you (MSA §8.4). Before you choose us as a Clerk replacement, know how our model differs from a pure auth provider:
Sign-in has no passwords and no social sign-in with Google or GitHub. Users enter their email address and confirm with a one-time code, sent by SMS to their phone with email as a fallback. New users add a phone number when they first sign in.
Buyer accounts are shared across tiun sellers. A tiun account is created automatically at a buyer's first purchase (MSA §4.7), and users can also create one through your tiun sign-up (Terms of Sale §1.3). It holds saved payment methods, contact details and login, and it works with every seller on tiun, including your competitors. You don't control that account (MSA §4.7).
We are an independent controller, not your processor; Auth0 and Kinde act as processors for your users' data. We control the data in our systems, and you control the data in your own systems, including anything you export from us (DPA §2.2–2.3). As between us, we own the service records: buyer accounts, credentials, transaction records, subscription states and logs (MSA §11.2). You can view them, export them as CSV or through the API, and request deletion, subject to our legal retention duties (MSA §11.3, §11.6). After you leave, export stays available for at least 90 days (MSA §18.2).
We process data primarily in Switzerland and the EEA (DPA §8.1). Seven of the 12 sub-processors on our list (2 September 2026) name a US location, including US backup or clearing for Stripe and PayPal. Transfers to them rely on mechanisms such as adequacy decisions (for certified US companies, the Data Privacy Framework) and Standard Contractual Clauses (Privacy Policy §8).
We built tiun for digital products: SaaS, downloads, courses, digital services, and AI and API tools. Our Terms of Sale say "tiun does not currently offer the Services to businesses in the United States" (Annex C.1), so you can't currently sell through us to US business buyers. Sales to US consumers are covered.
If your product needs workforce identity or enterprise SSO for your own B2B customers, a dedicated identity provider from the table is the better fit. Our post on auth providers with built-in billing compares the bundled options in more detail.
Migrating off Clerk
Clerk's dashboard export covers users and their password hashes. Sessions don't move, and Clerk's export docs don't mention passkeys. The CSV does include a totp_secret column, according to Kinde's and WorkOS's column lists, but whether a new provider imports it varies.
In the Clerk Dashboard, go to Settings, then User exports, then Export users, and download the CSV from the export history. Clerk says the file includes hashed passwords. Only admins, or users in their personal workspace, can export (Clerk docs).
Check the
password_hashercolumn. Clerk uses bcrypt, but users you once imported into Clerk from another system can carry other hash types. Kinde's Clerk guide imports bcrypt hashes with no password reset, and WorkOS also imports Clerk's bcrypt hashes.Active sessions don't transfer. Expect users to sign in again after the switch, or run both systems side by side and move users as they sign in.
Social sign-in has to be set up again in the new provider. Clerk production instances use your own OAuth credentials, so you can usually reuse the client ID and secret and add the new provider's callback URL. Whether a returning user is matched to their imported account by email depends on the new provider's account-linking rules, so test it with a real account.
Clerk's export docs don't mention Organizations. WorkOS's guide pulls organizations and memberships through Clerk's Backend API.
FAQ
Does any provider guarantee that data never leaves the EU?
None of the managed providers we checked promises that without exceptions. Hanko comes closest: its DPA commits to German data centres and no access from outside the EEA, apart from access and transmissions the customer initiates or configures. ZITADEL says data in transit can leave the region, Kinde lists Australia as the location of its AWS email service unless you bring your own SMTP provider, and both Kinde and Okta (for Auth0) list US sub-processors, including support tools. Our DPA says we process data "primarily" in Switzerland, which is outside the EU, and the EEA, and several of our sub-processors, including Stytch and Loops, name US locations. Self-hosting on a European-owned host, with European email and SMS providers, gives you the most control.
Is Switzerland in the EU?
No. Switzerland is in EFTA but not in the EU or the EEA. The EU has treated it as adequate since Decision 2000/518/EC of 26 July 2000, and the European Commission's report of 15 January 2024 confirmed that adequacy. An EU company can send personal data to a Swiss provider without extra safeguards, so no Standard Contractual Clauses are needed for that transfer. Onward transfers, for example to US sub-processors, need their own safeguard.
Is Auth0's EU region enough?
For primary storage, usually yes: Okta lists AWS hosting in the European Union for Public Cloud tenants in the EU region, and Private Cloud adds dedicated European deployments, including Switzerland on Azure. The region is fixed when you create the tenant. Okta's sub-processor list still places email, SMS, analytics and support ticketing with US providers, and Auth0 belongs to Okta, Inc., a US company. If your customers require a provider with no US parent, the EU region does not meet that.
Do I need passkeys?
Not for data residency. Passkeys resist phishing because each one works only on the site it was created for, and the server stores only a public key, so a breach leaks no reusable secret. Synced passkeys are backed up to the cloud of Apple, Google or the user's password manager. Your users' profiles, email addresses and logs still live wherever your auth provider hosts them. Hanko offers passkeys alongside passwords and one-time codes. Our sign-in uses one-time codes, which are simpler for users but, unlike passkeys, can be phished.
Can I move Clerk users without forcing a password reset?
Yes for users with bcrypt hashes, if the new provider imports them. Kinde's Clerk guide says those users keep their existing passwords. Check the password_hasher column first.