← Back to all posts

Cloudflare Email Sending Beta vs MailAnvil — Which Email API Should Indonesian Developers Choose?

2026-07-25 · MailAnvil Team

Cloudflare Email Sending Beta vs MailAnvil — Which Email API for Indonesian Developers?

Cloudflare dropped their Email Sending public beta on April 16, 2026. The pitch: send transactional emails directly from Workers with env.EMAIL.send(). No third-party API. No separate billing. Just Workers + email.

Indonesian developers who already run on Cloudflare (and that's most of us) have a natural question: should I use CF Email Sending, or stick with a dedicated email API like MailAnvil?

The answer isn't obvious. Here's the breakdown.

The Stack Comparison

Cloudflare Email Sending MailAnvil
Status Public beta Production (June 2026)
Infrastructure CF Workers direct CF Workers + AWS SES
Sending backend CF-managed SMTP AWS SES (ap-southeast-1)
Deliverability Unknown (beta) SES — industry gold standard
DKIM/SPF/DMARC Manual DNS Auto-provision for CF DNS
Pricing $0.35/1,000 emails Rp 149rb/10,000 (~Rp 15/email)
Payment Credit card (USD) QRIS, GoPay, OVO, Bank Transfer
Documentation English only Bahasa Indonesia + English
MCP-native No Yes — AI agents auto-discover
Bounce handling Basic Full suppression + webhooks + SNS
Rate limiting Unknown Per-key Durable Objects
Support Global ticket Indonesian timezone, Bahasa

The Hidden Cost of Beta

Three things Indonesian SaaS founders should know:

1. Beta means no SLA

CF Email Sending has no uptime guarantee. If it goes down during your peak Lebaran sale or flash sale campaign, you have no recourse. MailAnvil runs on SES — AWS's battle-tested email infrastructure with 99.9% SLA.

2. Beta pricing will change

Cloudflare hasn't announced GA pricing. The $0.35/1,000 is a beta teaser rate. At 100,000 emails/month, CF costs Rp 585,000 (at Rp 16,700/USD). MailAnvil's Growth plan is Rp 599,000 — nearly identical. But CF pricing can shift upward at GA. MailAnvil's IDR pricing is fixed.

3. SES deliverability is proven

AWS SES delivers billions of emails daily. Inbox placement rates are well-documented. CF Email Sending's deliverability track record is zero — it's been in beta for 3 months.

When to Use Cloudflare Email Sending

When to Use MailAnvil

The MCP Difference

This is where MailAnvil pulls ahead for AI-era development:

// mcp.json — one line, your AI agent sends email
{
  "mcpServers": {
    "mailanvil": {
      "url": "https://mcp.mailanvil.com/mcp",
      "headers": { "Authorization": "Bearer re_..." }
    }
  }
}

Cloudflare Email Sending has no MCP server. Your AI agent can't discover it. You write the integration manually. MailAnvil's MCP tools (send_email, get_email_logs, list_domains, list_templates, get_usage_stats) are auto-discovered by Claude, Cursor, Codex, and any MCP-compatible client.

Real Numbers: 100,000 Emails/Month

Cost Item CF Email Sending MailAnvil
Base cost $35 (Rp 585rb) Rp 599rb
Payment friction Foreign card needed QRIS/GoPay — instant
Exchange rate risk USD exposure Fixed IDR
Support language English Bahasa + English
Setup time Manual DNS CF DNS auto-DKIM

The cost difference is ~Rp 14,000/month. For that, you get: SES deliverability, MCP-native AI integration, Bahasa support, local payment, production SLA, and no beta risk.

The Bottom Line

Cloudflare Email Sending is exciting. It validates the market MailAnvil targets: developers who want email infrastructure that feels native to their stack.

But for Indonesian developers shipping production apps today, MailAnvil is the pragmatic choice. Same CF Workers DNA, better deliverability, IDR pricing, local payment, and MCP-native AI integration.

When CF Email Sending hits GA with stable pricing and proven deliverability, we'll update this comparison. Until then: MailAnvil.


Start with 500 free emails at mailanvil.com. No credit card. QRIS ready. Bahasa support.

MailAnvil — Email API for Indonesian builders. MCP-native. IDR pricing. Production-ready.