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.
Growth work lives or dies on targeting and measurement. What matters is whether behavioral triggers can be built without engineering time, whether the event stream supports attribution past the open, and whether deliverability holds when broadcast volume shares a reputation with product email.
Against behavior-triggered journeys, broadcasts, and winback campaigns measured on revenue, CloudMailin covers event stream and multi-tenant support, and does not cover scheduling and the suppressions API. Whether that gap matters depends on how central those are to the build.
- Scheduling: No
- Event stream: Yes
- Deliverability: Not applicable.
- Operating since: Not published
- Suppressions API: No
- Best published rate per 1,000: Tiers not published in comparable form
- Multi-tenant: Yes
- Free tier: No
- 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 |