Courier
Notification infrastructure with visual journeys.
Courier blends notification infrastructure with marketing-style journeys. Visual template builder, drop-in inbox UI, native Slack and Teams routing. Bridges product notifications and customer engagement.
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, Courier covers developer experience, SDK breadth, event stream, and webhook coverage, and does not cover idempotency keys and operating track record. Whether that gap matters depends on how central those are to the build.
- DX score: 8/10
- SDKs: node, python, go, ruby, php, java
- Idempotency keys: No
- Operating since: 2019
- Event stream: Yes
- Best published rate per 1,000: Tiers not published in comparable form
- Webhooks: Yes
- Deliverability: Inherits providers you connect.
- Free tier: 10,000 sends/mo
Inherits providers you connect.
Teams that need both product notifications and marketing-style journeys.
- › Visual journey editor
- › Native Slack/Teams routing
- › Drop-in inbox component
- › Less code-first than Knock
- › Pricing climbs with volume
Features at a glance
| API | Yes |
| SMTP | No |
| SDKs | node, python, go, ruby, php, java |
| Webhooks | Yes |
| Templates | rich |
| React Email | No |
| Batch send | Yes |
| Scheduled send | Yes |
| Suppressions | Yes |
| Multi-tenant | Yes |
| Inbound parsing | No |
| Event stream | Yes |
| Idempotency keys | No |
| Dedicated IP | No |