Inbound (inbound.new)

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.

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, Inbound (inbound.new) 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; receive-only.
• Webhooks: Yes
• Starts at: $10/mo for 1,000 inbound emails

Not applicable; receive-only.

Modern stacks that need email-to-webhook with TypeScript.