Warming up
Transactional email API
Warmerly sends your email through Amazon SES and adds what raw SES leaves to you: guided domain setup, bounce and complaint handling, a suppression list, retries, a delivery timeline per email and a dashboard. It is not cheaper than SES. Raw SES costs $0.10 per 1,000 emails, so 100,000 a month is $10 there against $29 on Warmerly. SES is the better pick if you have engineers to build and run that layer, or send in the millions.
Both options send through Amazon SES. With raw SES you build domain setup, event handling, suppression, retries, the delivery log and key management yourself; Warmerly runs that layer on top of SES.
Raw SES is $0.10 per 1,000 at any volume. A Warmerly plan used in full works out at $0.29 to $0.64 per 1,000, and more when it isn't. The difference pays for the layer on the right of the diagram above, and for not having to run it.
| Emails a month | Warmerly | Amazon SES |
|---|---|---|
| 10,000 | $15Starter | $1$0.10 per 1,000 |
| 50,000 | $15Starter | $5$0.10 per 1,000 |
| 100,000 | $29Growth | $10$0.10 per 1,000 |
| 500,000 | $279Scale 500k | $50$0.10 per 1,000 |
List prices, monthly billing, USD: the cheapest published plan that includes that many emails, overage left out on both sides. Amazon SES prices from aws.amazon.com/ses as of September 2026; check their site for current rates. Shaded cells are the cheaper side.
The same SES underneath. The rows are what sits around it, and who runs it.
| Feature | Warmerly | Amazon SES |
|---|---|---|
| API shape | REST, JSON over HTTPS, bearer key, Idempotency-Key header | AWS SDK or signed HTTPS API (SendEmail v2); AWS credentials |
| SMTP relay | Not yet (on the roadmap) | Yes |
| Delivery webhooks | Not yet. Read each email's delivery timeline from GET /emails/{id} | Events go to SNS, EventBridge or Firehose; you build the consumer |
| Templates | Not yet. You send your own HTML and text | Yes (SES templates) |
| Dedicated IP | $29/mo on Scale plans | $24.95/mo per IP; managed IPs $15/mo plus a per-email fee |
| Suppression list | Automatic on hard bounce and spam complaint, shared with Warmerly outreach | Account-level suppression list; anything per app is yours to build |
| Free tier | 5,000 a month (200 a day), no time limit, no card | Up to $200 in AWS Free Tier credits for new AWS customers, for 6 months |
| Log retention | Content 30 days; the email record and its delivery events are kept | No message log to browse by default; you store the events you want |
| SDKs | None. One HTTP request from any language | Every AWS SDK |
| Support | Email (support@warmerly.com), plus a 99.9% monthly uptime commitment with service credits | AWS Support plans (technical support needs a paid plan) |
Honestly, in these cases we would stay with Amazon SES.
Most of the work is DNS. The code change is small, but it is a change.
Warmerly creates the SES identity in its own AWS account, so your domain gets new DKIM tokens: three new CNAMEs ending in dkim.amazonses.com, plus a bounce MX, SPF and DMARC. Your current SES records can stay while you test.
Destination.ToAddresses becomes to, Content.Simple.Subject.Data becomes subject, Body.Html.Data and Body.Text.Data become html and text. No AWS credentials in your app: a sending key does it.
The SNS topic, the queue and the Lambda that marks bounces and complaints are no longer needed for this mail: Warmerly records delivery events and suppresses bad addresses itself.
Throttling and connection errors are queued and retried for up to 24 hours under the same email id, and an Idempotency-Key header makes your own retries safe.
| Amazon SES | Warmerly |
|---|---|
| AWS credentials + SigV4 | Authorization: Bearer wm_tx_... |
| FromEmailAddress | from |
| Destination.ToAddresses | to |
| Destination.CcAddresses / BccAddresses | cc / bcc |
| ReplyToAddresses[0] | reply_to |
| Content.Simple.Subject.Data | subject |
| Content.Simple.Body.Html.Data | html |
| Content.Simple.Body.Text.Data | text |
| EmailTags | tags |
| ConfigurationSetName | (handled for you) |
Yes. Every transactional email is sent through Amazon SES in eu-north-1, from Warmerly's own AWS account, with each workspace in its own SES tenant. You get SES's deliverability; Warmerly adds the setup, event handling, suppression, retries and dashboard around it.
No. Raw SES is $0.10 per 1,000 emails, so 100,000 a month costs $10 there and $29 on Warmerly. What the difference buys is not having to build and run domain setup, bounce and complaint processing, a suppression list, retries and a delivery log yourself.
Domain verification and DNS guidance, an SNS or EventBridge consumer for delivery, bounce and complaint events, a per-app suppression list, retry logic that doesn't double-send, a searchable log of what was sent, and alerts when your bounce or complaint rate climbs. Warmerly does each of those.
No. Warmerly sends from its own AWS account, so the domain is verified again with new DKIM keys, and sending reputation builds from your mail on Warmerly. Your domain's own reputation with inbox providers goes with the domain.
Yes, on Scale plans for $29 a month. SES charges $24.95 a month for a standard dedicated IP on your own account.
Create a free account, verify a sending domain and send a test from the dashboard. 5,000 emails a month free, no card.
