Sending & Deliverability
Docs chevron_right Sending & Deliverability chevron_right Amazon SES infrastructure

Amazon SES infrastructure

EmailFlow AI delivers every email through our managed Amazon SES infrastructure — the same enterprise-grade delivery network behind many of the world's largest senders. You do not need an AWS account, IAM keys, or SES configuration of any kind: we operate the infrastructure, and you verify your domain on it with a few DNS records.

How it works

When you add a sending domain in EmailFlow AI, we register it on our Amazon SES account behind the scenes and hand you the DNS records SES requires: an ownership TXT record and DKIM CNAME records. Once you publish them and the domain verifies, every email you send is delivered by SES, DKIM-signed as your domain, with SPF alignment handled by our infrastructure. Your recipients see mail from you, sent over infrastructure we keep warm and reputable.

What we manage for you

  • Sending IPs & reputation — warmed, monitored, and protected around the clock.
  • DKIM & SPF authentication — generated when you verify your domain; signing is automatic on every send.
  • Bounce & complaint feedback — SES notifies us instantly; hard bounces and spam complaints are unsubscribed automatically so your lists stay clean.
  • Capacity & throughput — account-level quotas, throttling, and scaling are our problem, not yours.
verified
The result: 99%+ deliverability on every plan — including Free — without you ever opening an AWS console.

Verify your domain

The one step that is yours: prove you own your sending domain. Open Sending › Domains, add the domain you send from (for example news.yourbrand.com or yourbrand.com), and publish the DNS records shown. Verification usually completes within minutes of the records propagating. The full walkthrough is in Sending domains & DKIM.

Why domain verification matters

Mailbox providers like Gmail and Outlook require authenticated mail: DKIM proves the message really came from your domain, and SPF proves the sending server was authorized. Verifying your domain wires both into every send automatically. It also means you can use any From address at that domain — hello@, news@, team@ — without verifying each one individually.

Frequently asked questions

Do I need an AWS account? No. The SES account is ours; you never interact with AWS directly.

Can I send before my domain is verified? No — mailbox providers reject unauthenticated mail, so verification is required before your first campaign. It only takes a few minutes of DNS work.

Which From addresses can I use? Any address at a domain you have verified. Verify yourbrand.com once and send as hello@yourbrand.com, news@yourbrand.com, and so on.

What happens to bounces and complaints? They flow back from SES in real time and are handled automatically — affected addresses are unsubscribed and your reports show exactly what happened.