Inbound (inbound.new)
Email-to-webhook with TypeScript-first DX.
Inbound converts any address into a webhook endpoint with structured JSON, automatic retries, and exponential backoff. Webhook delivery typically under 2 seconds. TypeScript types for the payload.
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, Inbound (inbound.new) covers every capability this audience leans on: developer experience, SDK breadth, idempotency keys, event stream, and webhook coverage. The deciding factor becomes price and operational preference rather than feature gaps.
- DX score: 8/10
- SDKs: node
- Idempotency keys: Yes
- Operating since: Not published
- Event stream: Yes
- Best published rate per 1,000: Tiers not published in comparable form
- Webhooks: Yes
- Deliverability: Not applicable; receive-only.
- Free tier: 100/mo
Not applicable; receive-only.
Modern stacks that need email-to-webhook with TypeScript.
- › Typed payloads
- › Fast delivery
- › Good free tier
- › Newer entrant
- › Node-only SDK
Features at a glance
| API | Yes |
| SMTP | No |
| SDKs | node |
| 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 | Yes |
| Dedicated IP | No |