Overview
Throughput, delivery rate, and provider health at a glance.


Unified notification infrastructure
One API for SMS, WhatsApp, email, and push: routing, provider failover, and pre-flight DND screening. You send. We deliver.
A message that doesn't arrive
is a system that doesn't exist. Delivery is not a feature.
It's the contract.
Edge gateways in Rust acknowledge in <50ms. Your request is durable before we return 202.
Priority lanes separate OTP from marketing. Routing orders by cost for unhurried traffic and by reachability for urgent traffic, then follows your provider-priority chain.
Pre-flight DND and consent checks. Vaultless tokenization keeps raw PII out of logs, queues, and dashboards.
Every provider's chaos normalized into one schema: Triggered → Delivered → Opened → Clicked → Converted. Sub-second analytics at scale.
The problem
Termii for Lagos. Twilio for Texas. SendGrid, FCM, APNs. Every provider is another API to learn, another outage to page you at 3 a.m., another deprecation notice in your inbox.
Flash sales, breaking news, mass OTP storms. Standard request/response architectures buckle exactly when your traffic (and your revenue) peaks.
One misrouted SMS to a do-not-disturb number is a fine. One EU record on a US server is a violation. Compliance isn't documentation; it has to run in the hot path.
The solution
Nervly ingests at hyperscale, routes by cost and reachability over your provider-priority chain, fails over across providers automatically, and clears every message against local regulation before it leaves the building. One API. Every channel. Delivered.
Idempotency keys with configurable TTL mean a network retry never double-charges a customer or double-sends an OTP. Send with confidence at any scale.
Static per-channel cost ordering: non-urgent traffic tries the cheaper channel first (WhatsApp ahead of SMS when you opt in) and falls through to the next on failure, over the provider-priority chain you configure. You set intent. Nervly picks the wire.
Pre-flight DND lookup through our Nigerian carrier before dispatch. PII replaced with format-preserving tokens. Primary datastore in Falkenstein, with onward transfers disclosed in the DPA. Auditable by design.
Nervly is in early access, so there are no customer quotes to lean on yet. What we can show is the system itself — and the commitments it has to keep.
Building on multiple providers and want a say in what ships? We're inviting design partners to work with the team.
Become a design partnerConsole screens 1 / 6
Illustrative interface.
Bring your own provider credentials and carrier costs stay on your own account. The first 1,000 notifications are free.
Strictly-typed SDKs, with Node available today and the rest of the set rolling out. Protobuf or JSON. A local CLI with environment detection, secret management, and webhook forwarding. An MCP endpoint so your AI coding agent can read schemas, write integration code, and run sandbox tests safely.
import { Nervly } from "@nervly/sdk"; const nervly = new Nervly({ apiKey: process.env.NERVLY_API_KEY }); await nervly.events.trigger( { name: "otp.requested", to: { subscriberId: "user_8x2", phone: "+2348011223344" }, payload: { code: "402913" }, }, { idempotencyKey: "ord_29441" }, ); // → 202 Accepted · { eventId, status: "QUEUED" }
Twilio is one provider. Nervly orchestrates the providers you already use, the ones shown above and more, with automatic failover, live cost arbitrage, and one normalized webhook schema. When a provider degrades, your messages don't.
Circuit breakers detect elevated error rates and reroute to the next healthy provider in your configured chain, automatically, without dropped messages. You'll see the failover in your console; your users won't see anything but the message.
Ingestion is an event-driven architecture: stateless Rust edge gateways buffer directly into NATS JetStream. We acknowledge in under 50ms at p99 and shape egress to each provider's real limits so nothing is dropped downstream.
Pre-flight DND lookup through our Nigerian carrier runs before dispatch; non-Nigerian numbers skip the check. Marketing to DND numbers is suppressed, and transactional traffic is permitted under the NCC rules. GDPR and NDPA controls (residency, consent, erasure) ship as platform features, not custom builds; POPIA support is on the roadmap.
Our primary production datastore and compute run in Falkenstein, Germany. Onward transfers to the sub-processors named in our DPA are disclosed there and rest on standard contractual clauses, so this is not a claim that data never leaves the EU. Internally, PII is replaced with format-preserving tokens, so raw phone numbers and emails never appear in logs or analytics.
No. This site sets no cookies, runs no third-party analytics, and writes nothing to browser storage, which is why there is no consent banner to dismiss. Client-side errors go only to our own first-party endpoint, with the URL query and hash stripped and no identifiers. It is a claim we enforce in the build, not just a line in a policy: the build fails if a cookie, a browser-storage call, an analytics vendor, or a third-party script origin is ever introduced.
It is one flat plan: ₦50,000 a month for 500,000 notifications and 100 requests a second, billed in NGN. You bring your own provider credentials, so carrier costs are billed by your provider at cost; we add nothing to them. Start free on 1,000 notifications a month. Prefer our providers? Platform, where Nervly provides the carriers, is on the roadmap; its pricing will be published before it ships.
Your first 1,000 notifications are on us. Integrate in an afternoon.