Users, organizations, and login. EU residency today, not on a roadmap.
$ thoryn login ✓ Signed in as maarten@acme.eu $ thoryn org create acme ✓ Organization "acme" created $ thoryn app register --org acme --name web ✓ App "web" registered client_id acme_web_7Ht9 redirect_uri https://acme.eu/callback $ thoryn user invite jane@acme.eu --org acme ✓ Invite sent
EU company. EU hosting on T Cloud. EU keys, EU admins, EU email and CDN. No US CLOUD Act exposure.
Who controls the identities, the keys, and admin access? With Thoryn, the answer is European.
Backed by Deutsche Telekom TechBoost, incubated at YES!Delft and built by the team behind login at bol.com.
Not weeks to first login. Guided or DIY. Migrate from any OIDC provider. Set up from the CLI today.
EU-owned and hosted. Data stays in the EU, including emails and CDN. No Cloud Act. GDPR built in.
Keycloak-grade identity without running Keycloak. Auth0-level ease without the US jurisdiction.
Most people are not starting from scratch. They are stuck partway through, with a concrete problem.
A client or employer needs the data in the EU. WorkOS and the usual providers cannot do that.
You are on Hetzner or Scaleway. Auth is the missing piece. You need the Auth0 of Europe.
Cognito docs, Clerk roles and sync, Auth0 pricing, or Better Auth after the Vercel move. You are switching anyway.
You chose Keycloak for control. Now you deal with crashes, scaling, and a clunky UI. You want managed, EU-hosted.
GDPR is built in. Privacy is built in. Hosted in Germany on T Cloud (Deutsche Telekom).
Data minimisation, DSAR, clear sub-processors.
No US parent in the chain.
Deutsche Telekom, Germany.
IoT on request.