OPERATIONAL REST API + SMTP RELAY SPF · DKIM · DMARC ALIGNED FULL DELIVERY AUDIT TRAIL Status →

[ 00 ] Transactional email infrastructure

Transactional email you actually control.

Send from your own domains, signed with your own DKIM keys, from warmed IPs with matching reverse DNS. Every message keeps a record of where it went, which IP it left on, and what the receiving server said back — in its own words.

Start free, 500 emails Read the docs

No card. Add a domain, publish the DNS we generate, send.

Delivery log live

Time Recipient Stream Status Latency

12:04:19 gmail.com receipts delivered 412ms

12:04:19 outlook.com receipts delivered 377ms

12:04:18 yahoo.com password deferred —

12:04:17 proton.me receipts delivered 298ms

12:04:16 icloud.com alerts bounced —

12:04:16 fastmail.com receipts delivered 341ms

Remote response 250 2.0.0 OK 1760254 - gsmtp dkim passspf passdmarc pass

DKIM per domain Your key, your d= tag SPF 1 lookup Nine left for everyone else DMARC aligned Not merely passing Reverse DNS FCrDNS Forward-confirmed, both ways

[ 01 ] The send path

From your application to the inbox, accounted for at every step

Five stages, each one logged. When a message does not arrive you can see precisely where it stopped and what the remote server returned.

Accept

API or SMTP. Validated, deduplicated and queued in single-digit milliseconds.

Sign

DKIM-signed with your domain’s own 2048-bit key before the message leaves.

Route

A VERP return-path selects the sending IP and ties the recipient to a traceable token.

Deliver

Warmed IPs with clean reverse DNS hand off, honouring SPF, DKIM and DMARC.

Account

Delivered, bounced, opened, complained — every event logged and sent back to you.

[ 02 ] Capabilities

Everything an ESP gives you, without the black box

The deliverability engineering of a large provider, on infrastructure you can see into and records you can export.

F-01

Your domains, your reputation

Send from send.yourbrand.com with your own DKIM keys. No shared via-domain diluting your identity.

F-02

Dedicated IP option

Start on warmed, monitored IPs and move to a dedicated one when your volume justifies it. Your DNS never changes either way.

F-03

Full forensic audit trail

Which domain sent to whom, when, from which IP, and exactly what the receiver said, verbatim.

F-04

Bounce and complaint handling

VERP-tracked bounces and feedback-loop complaints correlate to the exact message and recipient.

F-05

Signed webhooks

HMAC-signed delivery events, with retries and a circuit breaker so a slow endpoint never blocks the queue.

F-06

Automatic IP failover

A CNAME-first design means an IP or server change is a change to our zone. You never touch DNS again.

All features Documentation Free DNS tools Deliverability blog

[ — ] Platform

0 Uptime target

0 Messages / day capacity

0 Median accept latency

0 Events logged

[ 03 ] Developer surface

One call. Signed, routed, accounted for.

A REST API and a standard SMTP relay, with idempotency keys so a retry never sends twice. Every response carries a message ID that joins to every later event.

Idempotency keys — a timeout is not a failure
HMAC-signed webhooks — verified, replay-bounded
Per-message batch results — 200 does not mean all sent
SMTP or API — both, through the same pipeline

Read the API reference

delivery.webhook.js

// verify the signature, then trust the event
const ok = crypto
  .createHmac('sha256', secret)
  .update(req.rawBody)
  .digest('hex') === sigHeader

if (ok) {
  const { type, message_id, recipient } = req.body
  // delivered | bounced | opened | complained
  db.events.record(message_id, type, recipient)
}