MailKite
Get started
Alternative to Postmark inbound

Postmark-grade inbound — without the per-server tax or the hard limits.

Postmark's inbound parsing and deliverability are genuinely good. MailKite competes on the model around them: unlimited domains free instead of per-server pricing, graceful metered overage instead of hard caps, and an MIT-licensed webmail component you can drop into your app.

A fair take on Postmark

Postmark has an excellent reputation for transactional deliverability and its inbound webhook is solid, clean JSON. This isn't a capability argument — it's a pricing-model and openness argument.

Why teams switch

What MailKite does differently

Unlimited domains, no per-server tax

Postmark organizes sending around servers and message streams. MailKite gives you unlimited domains and addresses on one account, free — no structural cost to adding another product.

Graceful overage, never a hard cut

Cross your quota and MailKite meters it — no interruption. On Free we soft-pause with notice, not a wall.

Open-source webmail

@mailkite/mail is a MIT-licensed, framework-native inbox UI you can embed — a surface Postmark doesn't offer.

MCP + Claude Code plugin

Native MCP server and a Claude Code plugin so agents and AI tools can send, receive, and manage mail directly.

Side by side

MailKite vs Postmark

MailKite Postmark
Inbound → JSON webhook Yes — full parsed message Yes — clean JSON
Deliverability quality SPF/DKIM/DMARC aligned Excellent, established
Per-domain / per-server fees None — unlimited domains Server/stream-based structure
Overage behavior Metered, no hard cut Plan limits
OSS webmail component @mailkite/mail (MIT) None
MCP + Claude Code plugin Yes None
Zero-retention passthrough Per-domain toggle Not offered

Competitor capabilities change — we re-audit these tables regularly. Spot something out of date? Tell us and we'll fix it.

The price advantage

Unlimited domains. One quota. Free to start.

MailKite

  • Free: 3,000 emails/mo (in + out)
  • Unlimited domains, no server tax
  • Pro $20/mo → 50,000, graceful overage

Postmark

  • Per-message pricing, server structure
  • Inbound included, solid quality
  • Add domains/servers as you grow

If you run many small products, MailKite's unlimited-domains model usually wins on total cost — you don't provision a server or stream per product.

See full MailKite pricing →

Switch in an afternoon

Moving from Postmark

  1. 1

    Point MX at MailKite

    Add our MX records or use a managed subdomain. All your domains come along at no extra cost.

  2. 2

    Swap the inbound webhook

    Both send clean JSON, so the port is small: map Postmark's fields to event.from.address, event.subject, event.text, event.attachments[].

  3. 3

    Verify and consolidate

    Verify the HMAC signature, move sending over to share one quota, and optionally embed @mailkite/mail for a webmail view.

Questions

Is Postmark's inbound worse than MailKite's?

No — Postmark's inbound is good. The difference is the model: MailKite doesn't charge per domain or per server, meters overage gracefully, and ships an open-source webmail component. Pick based on how many domains you run and how you want to be billed.

What about Postmark's deliverability reputation?

Postmark has an excellent transactional reputation. MailKite aligns SPF/DKIM/DMARC to your own domain and sends over Cloudflare's network; for most transactional and inbound-first workloads it's a strong match. Evaluate against your specific volume.

Why does unlimited domains matter?

If you ship many products or manage client domains, per-server/per-domain pricing compounds. MailKite keeps that at zero and charges only on combined volume.

Try MailKite free — keep Postmark running until you're ready.

Point a domain, drop in a webhook URL, receive your first email. Unlimited domains, no credit card.