Nautilus by Verne Software
Nautilus is sign-in and user management for European SaaS teams. Your end users register and sign in with a password, a social account or a one-time email code; you add two-factor authentication, group them into organizations with roles, read an audit log of who did what, and have accounts that were never confirmed or have gone unused deleted automatically, after a warning email, on the retention periods you choose for the GDPR. It runs on servers in France and is sold as one plan, priced by active users.
The product also includes webhooks (sign-in and user events, and your own events, delivered to your endpoints), scheduled jobs (HTTP calls on a cron schedule or at a set time; the same scheduler runs the automatic deletion), and Telegram sign-in as one more way for your users to sign in. You get all of it from one API host (https://api.vernesoft.com), one dashboard, one account and one plan, and you call it from your own server with the official SDKs or plain HTTP.
What you can do with it
| Task | What it covers | Start here |
|---|---|---|
| Sign-in and users | Registration and login for your end-users, social login, two-factor authentication, sessions, organizations and roles, an audit log, and automatic deletion of inactive accounts. | Sign-in and users |
| Webhooks | Sending events from your app to your customers' endpoints, with retries, signatures and a delivery log. | Webhooks |
| Scheduled jobs | Recurring and one-time HTTP calls on a schedule you set, with retries and a run history. | Scheduled jobs |
| Telegram sign-in | Passwordless login for your end-users through a Telegram bot of your own. | Telegram sign-in |
Each task is served by its own API, and the API keeps its own name: the Gate API (/v1/gate/*) for sign-in and users, the Relay API (/v1/relay/*) for webhooks, the Clockwork API (/v1/clockwork/*) for scheduled jobs, and the Passepartout API (/v1/passepartout/*) for Telegram sign-in. Those names and paths are the contract your code is written against, so they appear in the reference pages even though the sections are named after the task. An API key is vrn_ followed by random characters, and it carries a set of scopes, one per API (gate, relay, clockwork, passepartout) that you tick when you create it; see API Keys.
How these docs are organised
The sidebar follows the order in which most teams adopt the product:
- Product overview – this page, how to install the SDKs, and one table of every endpoint.
- Sign-in and users – users, login flows, social login, two-factor authentication, sessions, metadata, webhooks for identity events, and automatic deletion of inactive accounts.
- Webhooks – publishing events and how they are delivered.
- Scheduled jobs – recurring and delayed jobs, and their execution history.
- Telegram sign-in – passwordless login through Telegram.
- API keys and plans – how API keys work, what each plan includes, and what your code receives at a limit.
Each task section has an introduction and an API reference with concrete endpoints, parameters and response schemas, with curl examples and, where useful, SDK usage.
How it runs
- Servers in France. The API, the databases and the engines run on servers in France, at OVHcloud, so Nautilus is EU-hosted.
- Each customer kept apart. Every API request is tied to its account at the gateway, from the API key or the session, and everything behind it is read and written for that account only. The same email address can be an end user of two accounts; they are two separate people.
- Open engines. Sign-in runs on Ory Kratos and webhooks on Svix, both open source; scheduled jobs and Telegram sign-in are our own Rust services. You can export your users with their password hashes and run the same engine yourself.
- Who you deal with. Verne Software, the company behind Nautilus, is registered in Serbia; the servers are in France.
What each API is built on
Each API runs as its own service behind the gateway, with no direct exposure to the public internet:
- Sign-in and users (Gate API) – identity management and authentication workflows, powered by Ory Kratos. Suited to B2B SaaS tenants and operator consoles.
- Webhooks (Relay API) – built on Svix and dedicated PostgreSQL queues, for durable event delivery, retries, and observability.
- Scheduled jobs (Clockwork API) – a first-party Rust scheduler for delayed and recurring jobs, with retry semantics and execution history.
- Telegram sign-in (Passepartout API) – lets your end-users sign in with Telegram: passwordless login, tenant-scoped identities in Ory Kratos, and encrypted per-tenant bot tokens.