Developer Infrastructure Simplified

Webhooks, Authentication, Telegram login, and Cron Jobs - production-ready APIs you can integrate in minutes, not months.

No credit card required · Free tier included · SOC 2 roadmap

  • WEBHOOKS
  • AUTH
  • CRON JOBS
  • TELEGRAM LOGIN
  • API KEYS
  • RATE LIMITING
  • HMAC SIGNATURES
  • IDEMPOTENCY
  • RETRIES & BACKOFF
  • OIDC
  • TOTP MFA
  • AUDIT LOGS
  • TENANT ISOLATION
  • USAGE METERING

(Nautilus Products)

One Platform, Every Backend Primitive

Nautilus is Verne Software's unified control plane: one API across every engine running today and every one added later, one dashboard to manage them all, and official SDKs for Node, Python, PHP and Rust. A single infrastructure, hosted in the EU, for European companies and independent developers.

(WEBHOOKS)

Live

POST /v1/relay/events

Relay

Webhooks-as-a-Service

Reliable webhook delivery with automatic retries, signature verification, and a full management portal. Powered by Svix.

(AUTH)

Live

PATCH /v1/gate/identities/:id/metadata

Gate

Auth-as-a-Service

Complete identity management for your B2B users - registration, login, recovery, and admin APIs. Powered by Ory Kratos.

(CRON)

Live

POST /v1/clockwork/jobs

Clockwork

Cron-as-a-Service

Schedule recurring jobs and delayed tasks with a simple API. Reliable execution backed by Faktory.

(TELEGRAM)

Live

POST /v1/passepartout/login/start

Passepartout

Telegram Auth-as-a-Service

Let your tenant's end-users sign up and log in via Telegram — no passwords, no email flows. Drop-in bot integration with full tenant isolation.

(Rust + Go)

API key validation
< 1ms
Platform SLA target
> 99.9%
Battle-tested engines
Svix + Ory

Engineered with memory-safe Rust and high-concurrency Golang engines, our architecture strips away traditional overhead. This bare-metal approach guarantees sub-millisecond latency and enterprise-grade reliability for your most critical workflows.

(How It Works)

Integrate in Three Steps

Sign Up

Create your free Nautilus account. No credit card needed.

Get Your API Key

Generate a scoped key from the dashboard (e.g., vrn_relay_...).

Start Building

Hit our API from your backend. We handle the rest.

(Why Nautilus)

Built Different

Microsecond Auth

On the hot path your API key never touches Postgres: the edge gateway checks its hash and decrements your quota in a single in-memory lookup. Auth, rate limiting and metering share that one hop, so validation stays under a millisecond even during traffic spikes.

Tenant Isolation

Tenant scope travels from the edge gateway all the way down to the database. API keys, webhook endpoints, cron jobs and Telegram identities are partitioned per tenant, so one customer's data can never be read - or billed - under another's account. The platform enforces it, not your code.

Usage-Based Pricing

You pay for the requests you actually send: 3,000 every month are free, then €3 per 10,000. Metering runs per tenant and stays visible in your dashboard, and a monthly spend cap means the bill can never run away from you.

Self-Hostable Engines

The data plane runs on open source you can audit and take with you: Svix for webhooks, Ory Kratos for identity, Faktory for scheduled jobs. We run the clusters, the upgrades and the on-call - but if your requirements change, the same engines run on your own infrastructure.

(Get Started)

Four engines, one API, in production since 1.0

Four engines are running in production today, with official SDKs for Node, Python, PHP and Rust and a tagged release behind every fix. Sign up, mint a key, and the first 3,000 requests every month are free.