Compare
PostMTA Hosted vs Postal, Resend, Halon
Other paths in the outbound stack — honest positioning where we lead and where we differ.
| Capability | PostMTA Hosted | Alternatives |
|---|---|---|
| Postal | Full MTA + enterprise panel | Open-source mail server + tracking |
| Resend | Dedicated infra + Kumo | Developer API relay (SaaS) |
| Halon | Kumo-native open core | Commercial scripting MTA |
| Enterprise | Contact-only, dual deploy | Varies — mostly SaaS or license |
| Proof | Named matrix rows M01–M42 | Vendor claims |
Where PMH is the wrong choice
If you already have deep operational muscle with Alternatives, do not rip and replace for the sake of it. PostMTA Hosted shines when the buyer needs managed control plane + smoke gates + verified From defaults. For pure send-and-forget transactional already covered by your incumbent, stay.
Migration timeline
- Week 1 — appliance bring-up + smoke-prod green.
- Week 2 — verified domains + credits ledger seeded.
- Week 3 — phased traffic at 1%, 10%, 50%, 100%.
- Week 4 — decommission Alternatives.
Operators: see docs/getting-startedand docs/operate/PRODUCTION for the appliance runbook.