One API for receipts, sign-in links and alerts, plus broadcasts when you need them. Templates you write in React, a delivery log you can actually read, and sending that pauses itself before a bad list hurts your domain.
Illustrative example. Addresses are placeholders.
Why Postie
Most email trouble isn't the API call. It's the bounce nobody noticed, the template only one engineer can edit, and the domain that slowly starts landing in junk. Postie watches those for you.
When bounces or complaints cross a safe line, sending from that stream pauses and you get told why, before it turns into a reputation problem.
Bars show bounce and complaint levels against the pause line. Illustrative.
Receipts and alerts from your code, newsletters to lists that opted in, in separate streams.
Write emails as components, preview them, and send by template name with your data.
Every send, delivery, open, bounce and complaint, findable by address in seconds.
Signed events to your server so your app knows what happened to each message.
The exact DNS records to add, and a live check that SPF, DKIM and DMARC are right.
Send on behalf of your own customers, each with separate limits so one can't hurt the rest.
For developers
Pass an idempotency key and a retried request never sends twice. Node and Python libraries come first.
Amazon SES does the delivery. Postie adds the API, templates, log, guard rails and domain tooling on top.
It's built on an AGPL-licensed open-source project, and our changes to it are published under the same license.
Yes, to people who opted in. Unsubscribe links and list hygiene are handled for you.
Early access opens to a few teams at a time. Tell us what you send and we'll reach out.
Request early access and tell us roughly what you send.