EMAIL CONTROL PLANE
We don’t send your email. We prove what happened to it.
Password resets, invoices, “verify your email” — the mail your product has to send. You keep the mail server you already have (or SES, Mailgun, Postmark). We keep the proof: did it go out, what it said, and who sent it.
live
STATUSRECIPIENTSUBJECTTIME
HOW IT WORKS
It sits between your app and the mail server you already pay for.
Spoolway sits between the apps you build and the mail server you already pay for. Nothing about your sending changes. What changes is that afterwards, you can look any of it up.
WHO WE AREWe are YS Progress Inc., a small Canadian company. We built the layer we could not buy — one place that answers did it send, what did it say, who can send.
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, Mailgun, Postmark, or your own server. We never send as if the mail were ours.
Your customerGets the email, the same as they do today.
and every step above is written down
Afterwards you can look up the body, the server’s reply, and who sent it. That is the cards below.
An archive that answers “what exactly did it say?”Search any email later. We store the body encrypted, for as long as you choose — or, for password resets, at zero, where the hourly sweep removes it once the message is final. When a retention period ends, deletion is a dated event you can see — not a mysterious 404.
to
subject
template
Body deleted 12 Jun 2026 per billing-prod’s 30-day policy — the envelope stays (who it was to, the subject, the delivery record).
Templates, versioned in gitWrite a password-reset once. Every product uses the same copy. Later you can see exactly which version went out.
Every message names its ApplicationAn Application is one of your products. “Which of my products sent this?” is a filter, not a forensic hunt. Unapproved senders have nowhere to hide.
Who can send. Who can read.
If you sign the contracts, these are the questions you actually ask — answered in the product, not in a PDF.
Reading a customer’s email is an audited actMost tools let anyone with a login read every customer’s mail and leave no trace. Here, opening a body records who, when and from where — and tells the reader they are being recorded.
Body views are audit-logged. Who, when, where — recorded. You are casey@acme-corp (owner).
Every key belongs to a personFire someone and their send key dies with their access — watch:
JD
Scope people to ApplicationsA contractor sees one product. A junior sees staging, not billing. That limit ships on Team and Enterprise; on Free, Pro and Scale a member sees every Application.
client-acmeonly
Visibility never costs a licenceAnyone who only needs to look is free, on every plan. Support can always check the log.read-only viewers · free · unlimited
Watch how far we can see.
Your apps → us → your mail server (a transport, in our words — the server or SES/Mailgun/Postmark account you already have). The dashed line is where we stop guessing. A 250 from your server means it accepted the job, not that the inbox got it, so we call it handed to your server. Amazon SES over SMTP, and a plain server, are marked handoff only. Green appears only when Mailgun or Postmark later confirms delivery — tagged as their word, not ours — and if a feed goes quiet, the count shows a dash with the time, never a zero.The whole integration.
You send a subject, the text, who it is from, and which product. We accept it, write it down, and hand it to your server. After that, every step is time-stamped and searchable.
curl -X POST https://spoolway.com/api/v1/messages \ -H "Authorization: Bearer spw_…" \ -H "Content-Type: application/json" \ -d '{ "application": "basalt-prod", "from": { "email": "[email protected]" }, "to": "[email protected]", "subject": "Your first message", "text": "This is the first message through your account." }'
← 202 Accepted · queued, not yet sent
{
"id": "2ee35675-6bae-42be-aa5e-6d4618d0c61d",
"status": "queued",
"application_id": 1,
"over_monthly_quota": false,
"attachments_captured": 0
}ENGINEERING TEAMSSeveral products, one mail logWrite the password-reset once. See which product sent which email. One log instead of five dashboards.authbillingnotifyone layerAGENCIESClient sites, cleanly separatedEach client is its own product in the log. Limiting a contractor to one client ships on Team and Enterprise. On Free, Pro and Scale they see every client. Anyone who just needs to ask “did it send?” looks for free.ANYONE ON CALL“Did that email actually go out?”If you have been asked at 2am and could not answer — search the log. You get the mail server’s own reply as the receipt.
PROOF, THE HONEST KINDNo customer logos yet, so the proof is our own — checkable in the product.
We run five products. We will not claim they are live on Spoolway until each one is.
Your transport. Your record.
Running in five minutes.
connect your mail server → name the product that will send → send a test messageStart free — no card requiredFree forever tier · caps pause, never auto-upgrade