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.
The question here is which one a backend engineer would rather operate. That means SDK depth in the language already in use, whether a retry can safely be replayed, how much the event log tells you when a customer says the email never arrived, and whether the pricing curve stays sane as volume grows.
Against password resets, receipts, and magic links shipped from application code, CloudMailin covers developer experience, event stream, and webhook coverage, and does not cover SDK breadth and idempotency keys. Whether that gap matters depends on how central those are to the build.
- DX score: 6/10
- SDKs: None
- Idempotency keys: No
- Operating since: Not published
- Event stream: Yes
- Best published rate per 1,000: Tiers not published in comparable form
- Webhooks: Yes
- Deliverability: Not applicable.
- Free tier: No
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 |