An EU-hosted Auth0 alternative, with the gaps stated

Pick Auth0 if your customers' IT departments ask for SAML or SCIM; you want a login page you can theme without writing screens; you need a wide choice of second factors (push, SMS, voice, hardware keys); you want a tenant in Australia, Canada, Japan, the UK or the US; or you want the name your customers' security teams already know. Up to 25,000 monthly users are free on their pricing page, which is more than our 1,000.

Pick Nautilus if you build a SaaS for European customers and want their data on servers in France; you want organizations, roles, two-factor and an audit log without a four-figure monthly bill; you want unused accounts deleted for you after a warning; and you are happy to draw your own login screens. We also send webhooks and run scheduled jobs under the same account, which Auth0 does not sell.

If you only need password and social login for a few thousand users, Auth0's free plan is a fair choice and we are not cheaper than it.

Sources for the Auth0 column are in the table at the end. Checked 2026-10-15. "Ahead" says who is ahead on that row.

Source: https://auth0.com/pricing, checked 2026-10-15. Monthly base price at the selector step shown. The page bills annual plans at 11 times the monthly price. Above 30,000 users the selector shows no price (B2C Essentials stops at $2,100 for 30,000), and Enterprise at any size says "Contact us"; we did not see a calculator. Our column: https://vernesoft.com/pricing.

How to read it

• Auth0 and we count different things: its monthly active users against our active users, each defined by its own vendor. Do not treat the rows as exact twins.
• The B2C plans cap organizations at 10. For a product organized around customer accounts, the B2B columns are the like-for-like ones for us.
• Free tiers: Auth0 gives up to 25,000 users, 5 organizations and one enterprise connection at $0. We give 1,000 users. If the Free plan covers what you need, it is the cheaper option.

• Auth0 (checked 2026-10-15, https://auth0.com/docs/get-started/auth0-overview/create-tenants): a public-cloud tenant is created in one of Australia, Canada, Europe, Japan, the United Kingdom or the United States; the locality sets where the data is hosted. Within Europe the docs name two sub-localities, EU and EU-2, and say the sub-locality is assigned, not chosen. The docs we read do not say whether the region can be changed afterwards. A thread on Auth0's community forum, attributed there to Auth0 staff, names Frankfurt and Dublin; it is not in the official docs and we do not rely on it. Auth0 is part of Okta.
• Nautilus: the API, the databases and the engines run on our own servers in France, at OVHcloud. That is where they run, not a compliance badge. One region, no choice. A data processing agreement based on the Standard Contractual Clauses comes with Pro.
• Verne Software is registered in Serbia; the servers are in France.
• If you need your data in Australia, Japan or Canada, or in a named EU city, Auth0 is the one to look at.

Moving off Auth0 to us is one move. The fair question is whether we are a second one you cannot undo.

• What is open: sign-in runs on Ory Kratos and webhooks on Svix, both open source, so you can read how they work and run them yourself. That is the way out of the engine.
• What is ours and does not leave with you: the layer on top. Projects, API keys, organizations and roles, the deletion rules, the audit log, the dashboard. Our scheduler is our own code, not an open engine. Every job and run stays readable through the API, so you can recreate them elsewhere.
• Users: you can read and list your end users through the API. For all of them with their password hashes, ask support from your account address and you get one file within 7 days, encrypted to your own key, with social links, metadata, organizations and roles as well. It is in the format our own import accepts and that maps onto Ory Kratos (how it works). A person on our side runs it; there is no button and no API call for it. Auth0 also hands hashes over through a support case, on conditions of its own.
• Auth0 itself is a closed product. Open engines are the one thing we can offer that it cannot, and we do not claim the exit is free.

Here is the arithmetic, so you can check it, with the cases where it does not work. Scenario: 10,000 active users; organizations, roles and two-factor. The line that decides is sign-in against sign-in. Prices as of 2026-10-15.

Not in the sum: webhooks you send to your own customers and scheduled jobs. Nautilus Pro includes both (1,000,000 webhook messages and 1,000 recurring jobs a month). Elsewhere they are services of their own: for example Svix Professional (DPA and SOC 2, 50,000 messages included) from $490 a month, and a scheduler such as cron-job.org, which is free, donation-funded, and does not state where it is hosted or whether it has a DPA. We leave them out of the sum because the comparison that decides is sign-in against sign-in.

What the arithmetic does and does not show

• Against Auth0's B2B plans the difference is large, because those plans are priced for a different buyer. This is the one pairing where Nautilus is clearly cheaper.
• It is not a fair comparison with Auth0's Free plan, which covers 25,000 users at $0 but, on the pricing page, no Pro-level second factors and no role management. A product that needs none of that can run on Auth0 Free for $0, and the free tiers of a webhook service and a scheduler are $0 too. Taken one by one, the free tiers are cheaper than we are.
• The webhook and scheduler volumes are left out on purpose. The honest case for the other side is sign-in on its own, at a small volume.