Transactional email infrastructure

Email infrastructure.
Less overhead.

Verified domains. A clean API. Delivery events that tell the whole story.

Made for the emails
your app runs on.

AuthenticationReceiptsNotificationsAccount updates

A few lines of code.
A lot less to manage.

Send with a typed SDK or a simple HTTP request. Keep provider credentials and delivery plumbing out of your application.

Send an emailInteractive API example
import { RavenRelay } from '@ravenrelay/node';​const raven = new RavenRelay({  apiKey: process.env.RAVENRELAY_API_KEY!,});​await raven.emails.send({  from: 'Orbit <hello@example.com>',  to: 'alex@example.net',  subject: 'You’re all set.',  html: '<h1>Welcome aboard.</h1>',});
ResponseAwaiting preview

A predictable response.
A message ready for the queue.

Preview the success or error contract.
Accepted now. Processed asynchronously.

Local preview of the planned API contract. No request is sent.

Project-scoped API keysAsynchronous sendingIdempotent request contracts

Delivery status.
In plain sight.

Inspect events, verify sending domains and connect webhooks. Useful detail, without digging through provider logs.

Example data

Recent emails

Orbit / Production
Example email log. Select a message to inspect its delivery state.
MessageRecipientStatusTime
alex@example.netDelivered12:04
sam@example.netQueued12:03
lee@example.netHard bounced12:02
kim@example.netDelivered12:01
One record. The complete delivery story.4 example messages

A healthier sending foundation.

Verified senders and automatic suppression for hard bounces and complaints are core to the product.

Your application stays informed.

Signed delivery events and independent webhook retries keep the feedback loop connected to your code.

From your code to their inbox

A clear path for every email.

RavenRelay wraps Amazon SES with the API, verification and delivery visibility your application needs.

  1. Verify your domain

    Add DNS records for DKIM and a custom MAIL FROM address.

  2. Create a scoped key

    Keep access tied to the right project and environment.

  3. Send to the queue

    The API accepts the message. A worker handles delivery.

  4. Follow the events

    See delivery outcomes and send updates back to your app.

Build the app.
We’ll handle the email.

Start with the API and the domain you already own.

Explore documentation