Skip to content
Apex
Aether Cloud · Communications

Email.

Transactional and marketing email at scale — high deliverability, templates and analytics, with the model drafting content.

✉ Communications
Overview

Send transactional and marketing email at scale with high deliverability, templating and analytics — and let the model draft and personalize the content, grounded in your data.

Where it sits
Deployment
Managed → air-gapped
Governance
IAM · encryption · audit

Sending is trivial. Landing in the inbox is the hard part.

Anyone can send an email; getting it delivered is a reputation and authentication problem that quietly eats engineering time. Aether handles the unglamorous parts — SPF, DKIM and DMARC, IP warm-up, bounce and complaint feedback loops, suppression — so transactional and marketing mail actually arrives. That's the table-stakes; the difference is that the content is the model's job, grounded in your data.

Model-drafted and personalised, not mail-merge.

Dynamic templates are one thing; a model that drafts and personalises each message against your governed data is another. A lifecycle email can be written per recipient from their actual account state, a campaign can be tailored beyond a {first_name} token, and it all stays inside the boundary because the model and the data are on the same platform.

Analytics and governance on the platform.

Opens, clicks and deliverability come back per recipient and per campaign, and because email runs where your data lives, the engagement data flows into the same analytics and the same governance as everything else — no third-party silo holding your customer interactions. It deploys managed or air-gapped.

Worked example

Draft and send a lifecycle email per recipient from their real account state — model and data on the same platform.

import { aether } from "@aether/sdk";

for (const u of await aether.sql`SELECT * FROM users WHERE trial_ends < now()+7d`) {
  const body = await aether.generate({ model: "aether-7b",
    input: `Write a trial-ending nudge for ${u.name} using their usage`, context: u.usage });
  await aether.email.send({ to: u.email, subject: "Your trial", body });
}

Each message is written from the recipient's actual usage, inside the boundary. A standalone email API can deliver well, but the content and the customer data live in two systems — here they're one.

How it works

Three steps to running.

01
Authenticate

Verify your domain with SPF, DKIM and DMARC for deliverability.

02
Send

Via API or SMTP, with dynamic templates the model can write.

03
Track & manage

Opens, clicks, bounces and complaints handled automatically.

What you get

Email, in full.

High deliverability

Reputation, authentication (SPF/DKIM/DMARC) and warm-up handled.

Templates & personalization

Dynamic content the model can write per recipient.

Bounce & complaint handling

Suppression and feedback loops managed automatically.

Analytics

Opens, clicks and deliverability, per campaign and recipient.

API-first

Provision it in a few lines.

Every service is reachable from the same SDK, CLI and infrastructure-as-code — one identity, one bill, one audit trail across the whole catalog.

# Provision email on Aether Cloud
aether communications create \
  --service email \
  --name app \
  --region us-1 \
  --deploy managed   # or vpc | on-prem | air-gapped
Specs

At a glance.

Throughput
High-volume
Auth
SPF · DKIM · DMARC
Templates
Dynamic, model-written
Feedback
Bounce / complaint loops
Analytics
Per-recipient
Use cases

Built for real work.

01

Transactional email

02

Marketing campaigns

03

Lifecycle notifications

Why one platform

On one model, not stitched together.

The usual stack runs email in one product, the model in another and the data in a third — and the seams between them are the cost. Aether Cloud runs it on the same platform that serves the model, governs your identity and deploys into your boundary, with the rest of the catalog one hop away.

One platform

No stitching a vector DB to one place, a warehouse to another and a model to a third — email sits next to the rest of the catalog, one identity, one bill.

The model is here

The provider that runs Aether runs your email — so the data and the model never leave the same governed boundary to talk to each other.

Built on demand

Need a capability that isn’t here yet? The model writes and deploys it into the same boundary — the catalog is a starting point, not a ceiling.

FAQ

Good to know.

How does this compare to AWS SES or email APIs?

High-deliverability transactional and marketing email — with the model drafting and personalizing content grounded in your data.

Transactional and marketing?

Both — with suppression, feedback loops and per-recipient analytics.

How is deliverability handled?

Authentication, reputation and warm-up are managed for you.

Deploy anywhere

Your boundary, your choice.

Managed
Your VPC
On-prem
Air-gapped / sovereign

Run Email on Aether Cloud.

Transactional and marketing email at scale — high deliverability, templates and analytics, with the model drafting content. Deployable managed, in your VPC, on-prem or fully air-gapped — talk to us about the configuration your workloads and your boundary require.