Posthaste is a transactional email API that isn't a layer over Amazon SES. We run our own mail servers, deliver straight to the recipient's server and keep its exact SMTP reply on a tamper-evident, hash-chained record. Free for 750 emails a month.
Hi Product Hunt 👋 I'm Hardil, and I built Posthaste.
Most transactional email APIs are an interface over Amazon SES. When a password reset doesn't arrive, you get "delivered" or "bounced" and have to guess the rest.
Posthaste runs its own mail transfer agent on its own IP. We resolve the recipient's MX, open the SMTP connection, negotiate TLS and hold the conversation ourselves. So for every message we can give you the transcript: what the receiving server actually said, including its diagnostic text when it refuses. Every event goes onto an append-only, hash-linked record (we call it the waybill), which you can export and verify yourself.
What's there today:
• REST API plus SMTP, with SDKs for Node, Python and Go, and a CLI
• Drop-in backends for Nodemailer, Django, Rails and Laravel
• Templates, batch sends (up to 100), signed webhooks, inbound mail routing
• A mailbox for the mail you receive: read, reply, threads, drafts and snooze, right in the dashboard (paid plans)
• One-time-code verification and address validation
• DMARC report ingestion and a reputation view for your domains
• An MCP server, so an AI agent can send mail and read delivery status with scoped keys
Two things you should know up front:
1. The sending IP is young. Inbox placement is still being established, and the warmup ladder is deliberately conservative. The daily cap grows with your own sending history, and it works the same on every plan.
2. Transactional only. No newsletters or campaigns. On shared infrastructure, one bad list damages delivery for everyone.
There's a free plan (750 emails a month). I'd really value feedback from anyone who has fought with a missing email. What would you want to see in the transcript?