Registration, login, recovery and two-factor for your customers' accounts, plus outgoing webhooks and scheduled jobs. All on one account.
No credit card required · Free tier included
(What You Get)
Nautilus is one product from Verne Software: one account, one dashboard and one API for your customers' sign-in, the webhooks you send them and the jobs you run on a schedule. Official SDKs for Node, Python, PHP and Rust. It goes on top of the code you already have, and your application database stays where it is.
(AUTH)
PATCH /v1/gate/identities/:id/metadataRegistration, login by password or through Google, GitHub and other providers, password recovery, email verification and two-factor. An admin API to look up, change and delete your users.
(TELEGRAM)
POST /v1/passepartout/login/startYour customers sign up and log in with their Telegram account: no password, no email flow, no SMS bill. You connect your own bot from the dashboard.
(WEBHOOKS)
POST /v1/relay/messagesSend events from your product to your customers' endpoints. Failed deliveries are retried automatically, every message is signed, and every attempt is logged with the response it got.
(CRON)
POST /v1/clockwork/jobsSchedule recurring jobs with a cron expression, or one-off tasks for a set time. Nautilus calls your URL, retries on failure and keeps a log of every run. Schedules run in UTC.
(Rust + Go)
The gateway is written in Rust and checks your API key from memory: no Postgres query and no cold start in between. We do not print a latency promise here; measured response times are on the status page.
(How It Works)
Create your free Nautilus account. No credit card needed.
Create a key in the dashboard for what you are adding first: sign-in, webhooks or cron jobs. Each key is scoped to one of them.
Call the HTTP API from your backend, or use the Node, Python, PHP or Rust SDK. We run the servers and the upgrades.
(Why Nautilus)
Your API keys, users, webhook endpoints and cron jobs are scoped to your account: a key can act only on your own users, and the platform enforces that — the control lives in Nautilus, not in integration code you have to write and keep correct. One limit: a social login (a given Google or GitHub identity) can be a user of only one account on the service.
Sign-in runs on Ory Kratos and webhooks on Svix, both open source, so you can read how they work and, if you ever need to, run them yourself. Scheduling is our own code, so that part does not come with you, but every job and run stays readable through the API.
The API, the databases and the engines run on servers in France, at OVHcloud. That makes Nautilus EU-hosted: a fact about where it runs, not a compliance badge. A data processing agreement based on the EU Standard Contractual Clauses is available on request.
We aim for 99.9% availability and publish how we are doing: uptime history for each component, 90 days back, on the public status page. It is a target, not a contract. There is no SLA and no service credit behind it.
You can, and if you already have the people for it, it is a fair choice. Sign-in, webhook delivery and scheduled jobs on AWS means Cognito, SQS, Lambda and EventBridge, wired together, monitored and kept up to date by your team. Nautilus is the same three jobs behind one account, free for up to 1,000 active users a month: 10,000 webhook messages, plus scheduled jobs, up to 10 recurring and 100 delayed at a time. What you give up is control over the internals: you depend on us, and the open engines are your way out.
Our servers are in France. A data processing agreement based on the European Commission's Standard Contractual Clauses is available on request. Our API lets you delete a user's identity and sessions at any time, so you can act on a deletion request. You can also have Nautilus delete accounts that were never confirmed and, on Pro, accounts that have gone unused for a period you choose, each after a warning email and only if you switch it on.
Sign-in, webhooks and cron jobs run as separate services, so a stalled cron worker leaves sign-in and webhook delivery untouched, and the status page shows each part on its own. The one shared piece is the thin gateway that checks API keys and counts usage. It is still one vendor, and that is a real trade-off: the way out is that sign-in and webhooks run on open-source engines, Ory Kratos and Svix, which you can host yourself.
Nautilus has a free tier as well: up to 1,000 active users a month, 10,000 webhook messages, and cron jobs on top, up to 10 recurring and 100 delayed at a time. The difference shows up later. Supabase and Firebase expect your data to live inside them, so the moment webhooks or sign-in have to work against a database you already run, you are rebuilding your backend around theirs. Nautilus goes on top of the code you already have: your application database stays where it is, and you call an HTTP API from whatever stack you run. Paid plans start at €99 a month and are counted in monthly active users, not in requests.
Both are possible, and a page like this cannot rule either out. The plans on the pricing page are the ones in force today. What protects you if either happens is the engines: sign-in runs on Ory Kratos and webhooks on Svix, both open source, so you can run them yourselves, and every cron job and run stays readable through the API.
(Get Started)
Create an account, make a key for the part you need first, and your first 1,000 active users every month are free. Official SDKs for Node, Python, PHP and Rust, and a tagged release behind every fix.
