Transactional Email across clouds
The platform email service - SES, Azure Communication Services email, OCI Email Delivery - sending from a domain you own, with SPF, DKIM and DMARC published and bounces handled.
3 verified modules, 1 of them live-tested apply→verify→destroy; the rest are static-validated, live-test pending.
Compare by provider
| Provider | Module | Verification |
|---|---|---|
| AWS | SES v2 Sending Stack | ✓ live-tested |
| Azure | Email from Your Own Domain with the DNS Records Exported and Tracking Off | static-validated |
| Oracle Cloud | Sending Mail that Receivers Trust, from Approved Senders | static-validated |
How to choose
Every one of these starts in a sandbox or a low quota and needs a request to send at volume. Compare how the domain is verified (DNS records the module exports), whether DKIM signing is managed, how bounces and complaints reach you (a topic, a webhook, a suppression list), and whether the service will let you send from an address it made up.
When not to use
Deliverability is a reputation, and a reputation belongs to the domain, not the provider. A sending domain shared with marketing mail carries its complaints; a dedicated subdomain with DMARC enforcement is the setting that survives a bad campaign.