Courier vs MailAnvil: notification orchestration vs transactional email API
Courier vs MailAnvil: notification orchestration vs transactional email API
Two products that both "send messages" but sit at different layers. Courier is a notification orchestration layer: it routes one event across email, SMS, push, in-app inbox, Slack, and Microsoft Teams — using your own delivery providers (SendGrid, Twilio, FCM, and 50+ others). MailAnvil is the email API itself: it sends the email over AWS SES, with no provider bill stacked underneath.
Picking wrong costs you either double-billing or a rebuild.
The pricing math
| Courier Business | MailAnvil Pro | MailAnvil Business | |
|---|---|---|---|
| 100K sends/mo | $500/mo + your provider's bill | Rp 249rb (~$15) | Rp 749rb (~$50) |
| 10K sends/mo | Free (Developer plan) | Free (3,000 emails/mo) | — |
| What you pay for | Routing, templates, preferences | Actual email delivery via SES | Actual email delivery via SES |
Courier's rate is simple: $0.005 per notification on any channel, 10,000/mo free on the Developer plan. At 100K notifications that is $500/month — before you pay the underlying email/SMS provider it routes to. If the message actually goes out as email, the ESP bill sits on top.
MailAnvil charges for delivery, full stop. 100K emails is Rp 749rb/month (~$50), roughly 10x cheaper than Courier's routing fee at the same volume — and there is no second invoice underneath it.
That gap is not an apples-to-apples discount; it reflects the scope difference. Courier earns its fee when one event fans out to multiple channels. If all you send is transactional email — OTP, verification, receipts, notifications — you are paying a routing layer to call an ESP you also pay directly.
What Courier gives you that MailAnvil does not
- Multi-channel fan-out — one API call routes to email, SMS, push, chat, and in-app with cross-channel fallback.
- Preference management and inbox components — end users manage channel preferences; drop-in inbox UI.
- Journeys and automations — batching, throttling, delays, conditions.
- Provider portability — swap SendGrid for Twilio/SES in settings, not code.
- MCP server — Courier ships a public MCP (145 tools), so AI agents can send and manage templates. This is table stakes now; every serious notification product has one.
What MailAnvil gives you that Courier does not
- It is the provider. No orchestration layer, no second vendor, no provider bill underneath. Your SES sending reputation lives in one place.
- IDR pricing with QRIS/GoPay. Rp 249rb/month for 50K emails. No USD card needed, no FX spread, hard cap instead of surprise overage.
- Bahasa docs and support for Indonesian dev teams.
- Cloudflare Workers-native — sub-50ms API calls from the edge where your Workers already run.
- MCP-native too. MailAnvil has its own MCP server for agent-driven email, at a delivery price Courier cannot match because it is not paying a provider margin.
When each one wins
Pick Courier if: you send across 3+ channels, want cross-channel fallback, or need end-user preference management. The $0.005 routing fee buys real orchestration — and you bring your own ESP.
Pick MailAnvil if: the message is email — OTP codes, verification links, receipts, billing notifications. Indonesian teams especially: paying an orchestration layer to route to an ESP is a 10x markup on what direct delivery costs, in a currency you can actually pay with QRIS.
Or both: a common pattern is MailAnvil as the email provider connected inside Courier's provider catalog. You get Courier's fan-out and MailAnvil's IDR-priced SES delivery. Just remember Courier's fee is per notification routed, on top of the MailAnvil bill.
Bottom line
Courier solves "which channel and which provider" problems. MailAnvil solves "send this email, cheaply, in rupiah" problems. Most Indonesian startups building transactional flows need the second, not the first — and Courier's own free tier (10K sends) is the fastest way to see the difference in your bill.
MailAnvil is an email API built on Cloudflare Workers + AWS SES, with an MCP server so AI agents can discover and send email. IDR pricing, QRIS/GoPay, Bahasa docs at mailanvil.com.