FOR TEAMS ON AMAZON SES
SES is the cheapest way to send. It is not a way to remember.
SES takes your message and hands it on for a fraction of a cent. What it does not give you is the thing somebody asks for three months later: what exactly did we send that customer, and what did SES say when it took it? Spoolway sits in front of your SES SMTP credentials and keeps that record.
Keep sending through SES. Keep the price, the deliverability and the AWS bill you already have.SES connects as an SMTP transport today, so the record ends at SES accepting the message: its own reply and message id, word for word. We do not show Delivered for SES yet: SES sends its delivery reports as SNS notifications, and we cannot receive those for an SES transport today.
WHERE WE SIT
Amazon SES still sends the mail. We write down what happened.
Your appyoursSends one request: who it goes to, which template to use, and the values to fill in.
Spoolwaythis is usWe fill in your template, hand it to your server, and write down every step.
Your mail serveryoursAmazon SES, on your own account and at your own rates. We never send as if the mail were ours.
Your customeryoursGets the email, the same as they do today. Your address, your reputation.
and every step above is written down
THE RECORDsearchable later — and kept for exactly as long as you decide
Did that email actually go out?Your mail server’s own reply, word for word, with the time it was accepted.
What exactly did it say?The message itself, stored encrypted, for as long as your retention policy says — or never stored at all.
Who else can send as us?Every key is named and belongs to a person. Revoke one without breaking the rest.
WHAT CHANGES FOR YOU
Four things, in plain words.
Your SES credentials, unchangedAdd your SES SMTP credentials once as a transport. We send through your account, at your rates, from your verified domains. Nothing about your sending reputation moves.
The archive SES does not haveEvery message searchable by recipient, subject or product, with the body stored encrypted for as long as you choose — or never stored at all.
Honest about where it stopsOver SMTP the record stops at “handed to your server” and keeps SES’s answer beside it. No green tick stands in for an inbox nobody has confirmed.
One template set, every stackWrite the password reset once. Every service you run sends the same copy, versioned in git, with the exact version recorded on each message.
THE INTEGRATION
Your SES SMTP credentials, added once
transport: smtp host: email-smtp.us-east-1.amazonaws.com port: 587 username: AKIA… # your SES SMTP credentials # nothing else about your SES setup changes
WHAT WE DO NOT DO
We never send mail as if it were ours, and we never show a delivery we cannot prove.
There is no plan where we become your sender. Your server keeps your reputation. Where a mail server cannot report back, the record stops at the handoff and says so — no green tick standing in for a fact nobody has.
what we hold, and what we do not have yet →ALSO WRITTEN FOR
Your transport. Your record.
Running in five minutes.
connect your mail server → name the product → send a testStart free — no card requiredFree forever tier · caps pause, never auto-upgrade