Compare
PostMTA Hosted vs Managed MTA
Postmastery-class ops retainer vs productized appliance with panel, smoke gates, and self-serve operator docs.
| Capability | PostMTA Hosted | Managed MTA |
|---|---|---|
| Deliverable | Appliance + panel + matrix | Ops hours + config |
| Transparency | Open smoke-prod gates | Opaque SLA |
| Credits | Ledger hold/commit/void | Provider billing |
| Handoff | Customer VPC install path | Often provider-locked |
| Support | Enterprise by request | Retainer model |
Where PMH is the wrong choice
If you already have deep operational muscle with Managed MTA, 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 Managed MTA.
Operators: see docs/getting-startedand docs/operate/PRODUCTION for the appliance runbook.