Nautilus by Verne Software

Nautilus is one product for the backend jobs most applications need and few teams want to build: signing users in and managing them, delivering webhooks, running scheduled jobs, and signing users in with Telegram. You get them from one API host (https://api.vernesoft.com), one dashboard, one account and one plan, and you call them 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, and user management.	Sign-in and users
Webhook delivery	Sending events from your app to your customers' endpoints, with retries, signatures and a delivery log.	Webhook delivery
Cron jobs	Recurring and one-time HTTP calls on a schedule you set, with retries and a run history.	Cron 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 cron 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.
Webhook delivery – publishing events and how they are delivered.
Cron 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.

Engineering Foundations

At Verne Software, we treat Nautilus as an Umbrella SaaS: a single control plane orchestrating multiple specialized data planes.

We follow a strict separation of concerns:

Dumb Pipes, Smart Endpoints – the network is simple; the intelligence lives in well-defined services.
Control Plane vs Data Plane – provisioning, IAM, and billing are isolated from hot-path request processing.
Documentation as a First-Class Surface – every primitive exposed by Nautilus has a clearly versioned, testable contract that you can integrate against with confidence.

From an infrastructure perspective:

Sub-millisecond edge – 100% of public API traffic enters through our Rust edge gateway (Actix + Dragonfly). It authenticates API keys and applies rate limits and plan limits in under a millisecond.
Multi-tenant isolation – every API request is resolved to its tenant at the edge, and the core scopes its queries to that tenant.
Decoupled core – the Core Platform acts as “The Brain”: it owns provisioning, identity, plan limits, and billing by monthly active users, while keeping heavyweight operations off the edge path.

What each API is built on

Each API runs on its own data plane, without direct public internet exposure:

Sign-in and users (Gate API) – identity management and authentication workflows, powered by Ory Kratos. Suited to B2B SaaS tenants and operator consoles.
Webhook delivery (Relay API) – built on Svix and dedicated PostgreSQL queues, for durable event delivery, retries, and observability.
Cron 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.

Infrastructure & Operations

We treat infrastructure as code and optimize for reliability and predictability:

Hosting & Network – Nautilus runs on high-performance VPS environments (NVMe storage, scalable vCores). Traefik is used as the edge reverse proxy for automated subdomain routing and Let’s Encrypt certificate management.
CI/CD Pipeline – GitHub Actions builds Rust binaries and Vue front-ends into compact Docker images (Alpine/Distroless). Deployments run docker compose pull && docker compose up -d, which restarts the services whose images changed.

From a developer’s point of view, this means:

the same container setup in local development and in production,
predictable rollout behavior,
and documented failure modes you can plan for.