Compare
PostMTA Hosted vs Mailgun
API-first outbound on infrastructure you control — not Sinch's managed relay with their reputation pool.
| Capability | PostMTA Hosted | Mailgun |
|---|---|---|
| SMTP credentials | Per-workspace on your box | Per-domain on their cloud |
| DKIM/DNS | Full checklist + verify + Kumo publish | Managed DNS helpers |
| Volume economics | Flat enterprise engagement | Per-message + tiers |
| FBL | Included complaint ingest | Add-on / limited |
| Escape hatch | Export ledger + config | API migration project |
Where PMH is the wrong choice
If you already have deep operational muscle with Mailgun, 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 Mailgun.
Operators: see docs/getting-startedand docs/operate/PRODUCTION for the appliance runbook.