CloudMailin
Long-running inbound email to HTTP service.
CloudMailin has been doing inbound email to HTTP since 2010. Reliable, no-frills, JSON or raw MIME delivery.
A SaaS product sends on behalf of its customers, so the deciding factors are tenant isolation, whether suppressions can be scoped rather than global, and whether support can answer why one specific account did not receive one specific email. Lifecycle automation and transactional sending usually need to coexist.
Against trial expiry notices, dunning, onboarding sequences, and per-tenant transactional mail, CloudMailin covers multi-tenant support, event stream, and webhook coverage, and does not cover the suppressions API and scheduling. Whether that gap matters depends on how central those are to the build.
- Multi-tenant: Yes
- Event stream: Yes
- Suppressions API: No
- Operating since: Not published
- Scheduling: No
- Best published rate per 1,000: Tiers not published in comparable form
- Deliverability: Not applicable.
- Webhooks: Yes
- Starts at: $9/mo for 200 emails
Not applicable.
Established workloads that depend on a long-running provider.
- › Mature product
- › Multiple payload formats
- › No free tier
- › Older UI
Features at a glance
| API | Yes |
| SMTP | No |
| SDKs | None |
| Webhooks | Yes |
| Templates | none |
| React Email | No |
| Batch send | No |
| Scheduled send | No |
| Suppressions | No |
| Multi-tenant | Yes |
| Inbound parsing | Yes |
| Event stream | Yes |
| Idempotency keys | No |
| Dedicated IP | No |