(WEBHOOKS)
Live
POST /v1/relay/eventsRelay
Webhooks-as-a-Service
Reliable webhook delivery with automatic retries, signature verification, and a full management portal. Powered by Svix.
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.
(AUTH)
Live
PATCH /v1/gate/identities/:id/metadataGate
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/jobsClockwork
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/startPassepartout
Telegram Auth-as-a-Service
Let your tenant's end-users sign up and log in via Telegram — no passwords, no email flows, no SMS costs. Drop-in bot integration with full tenant isolation.
(Rust + Go · Bare-Metal Performance)
- 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: no Postgres on the hot path, no cold start between a request and its answer. Rather than promise a latency figure here, we publish the real one — live on our status page.
(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.
Why Verne, when AWS, Google Cloud and Azure have data centres in Frankfurt and Ireland too?
AWS gives you a raw data centre, not a finished business solution. To run webhook delivery, authentication and cron on AWS you have to hire a DevOps engineer, set up SQS, Lambda, Cognito and EventBridge, wire them together and write the monitoring yourself — weeks of engineering before the first customer request goes through, and it stays yours to keep running. Verne gives you a production-ready API from €19 in ten minutes — not a construction kit you assemble and then maintain for months.
GDPR is not just a server in the EU — it is legal agreements (DPAs), and processes for handling and deleting data.
Verne is built on Privacy by Design from the start. We do not keep data we do not need (data minimisation), we offer transparent DPAs (Data Processing Agreements), and we ship ready API endpoints for the complete deletion of a user's data on first request (Right to be Forgotten).
If Verne goes down, my webhooks, my auth and my cron all go down at once. That is a single point of failure.
Inside Verne the engines are isolated from each other. Relay, Gate and Clockwork run as separate services on separate storage, so a failure in one does not stop the others — a stalled cron worker leaves authentication and webhook delivery untouched. The only shared surface is the thin edge gateway that checks API keys and meters usage, and it keeps no engine data of its own.
It is easier for me to take the free tier on Supabase or Firebase than to pay €19 for Verne.
Verne has a free tier as well — 3,000 requests a month, every engine included. The difference shows up later: Supabase and Firebase expect your data to live inside them, so the moment webhooks or authentication have to work against a database you already run — PostgreSQL, MySQL, MongoDB — you are rebuilding your backend around theirs. Verne goes on top of the code you already have: your database stays where it is, and you call an HTTP API from whatever stack you run.
This is too cheap. Either the service is shaky, or you will raise the price once you have the users (dumping / bait-and-switch).
The price follows the stack, not a land grab. Everything that carries your traffic is compiled — Rust for the gateway and the API, Rust and Go for the engines themselves (Svix, Ory Kratos, Faktory) — and compiled services hold far more traffic per gigabyte of RAM than their Node.js and Python equivalents. That makes our infrastructure bill per request small, and the price list is where we pass it on. And if the deal ever stops being good: the engines are open source, so you can take them and run them yourself.
(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.