Email Routing vs Improvmx vs Forward Email: Honest Comparison

Most comparisons of email forwarding tools solve the problem the wrong way: they list features in a table, say they are all good, and leave it up to you to figure out which one works. The problem is that the right choice depends on where your domain is hosted and what you want to do with the emails that come in — and these two factors eliminate two or three options before you even evaluate anything else.

Cloudflare Email Routing: When integration is the advantage

Cloudflare Email Routing is free with no documented volume limit — at least for now. You set up specific aliases or a catch-all, point each one to verified addresses or Email Workers, and the service automatically manages MX records in your DNS zone.

The real advantage is not the price. It's the integration with the rest of the Cloudflare infrastructure. If your team already uses Workers for APIs, cron jobs or data processing, Email Workers enter the same environment with the same bindings — KV, D1, R2, external services. You can receive an email, parse the MIME with postal-mime, extract an attachment and write it to R2, all in a Worker without adding any external pieces to the stack.

The constraint that determines it all: the domain must use Cloudflare nameservers. If you're on Cloudflare for DNS, CDN, or WAF, you already have this. If not, migrating the DNS zone is a decision with consequences beyond email — it affects the rest of the DNS configuration, SSL, and proxies. For those who are not willing to do this, Email Routing is not available.

There is also no sending. To reply to the domain or send transactional email, you need a separate provider.

Improvmx: the option for those who don't want to change nameserver

Improvmx has a different proposal: it works with any DNS provider. You add a TXT record for domain verification and two MX records, and the aliases work. No nameserver migration.

The free plan has 1 alias and a limit of 500 forwarded emails per month — suitable for a personal project or test, not enough for any real professional use. The Pro plan costs $9 per month and removes the limits: unlimited aliases, unlimited volume.

Improvmx has nothing equivalent to Email Workers. The email is forwarded, period. If you want programmatic processing, you'll need to combine it with another service — which increases complexity and cost. What Improvmx offers is operational simplicity: clean interface, no code, no advanced configuration. For a team that wants domain aliases without technical friction and isn't on Cloudflare, it's probably the right choice.

Forward Email: full control, including sending

Forward Email is open-source — the code is available, you can audit, contribute, or run your own instance. The service hosted at forwardemail.net has a free plan and paid plans starting at US$3 per month.

The difference that other options don't have: support for SMTP outbound by the domain itself. With Forward Email you can send email from voce@seudominio.com without needing a separate provider like Resend or SES. For teams that want receiving and sending in a single service without paying for Google Workspace, this is a solid argument.

The other advantage is privacy. Forward Email does not log the content of emails. For projects where this matters — health data, legal communications, contexts where you don't want a third party to store message content — this guarantee has value.

It also doesn't require changing nameservers: you add the necessary MX and TXT records, and it works with any DNS provider.

The downside is that the setup experience is more technical. It's not difficult, but it requires more attention than Improvmx or Cloudflare.

Postmark Inbound: for developers who need structured parsing

Postmark Inbound is another category. It's not a forwarding service — it's an email processing pipeline with delivery via webhook. When an email arrives, Postmark parses the complete MIME and makes a POST to your endpoint with structured JSON: sender, recipient, subject, body text and HTML, attachments such as base64 strings, headers, and metadata. You don't need to parse anything.

The minimum cost is $15 per month — Postmark's cheapest plan. There is no free tier. For those who already use Postmark to send transactional emails, Inbound fits into the same account and the same billing.

The main use case is email processing at scale: supporting pipelines, email data extraction, automations that need reliable parsing without library maintenance. For a Worker on Cloudflare, you do this parsing yourself with postal-mime. For a webhook in Postmark, you receive a ready-made JSON.

Which one makes sense for each situation

If your domain is already on Cloudflare and you want simple forwarding plus the ability for programmatic processing in the future, Email Routing is the obvious answer — free and with no additional integration costs.

If the domain is on another provider and you don't want to move it, and the only requirement is forwarding of aliases, Improvmx at US$9 per month solves it without complications.

If you need to send email from your own domain without paying for Google Workspace or adding a separate SMTP provider, Forward Email deserves serious attention.

If you're building an email processing pipeline that already uses Postmark for sending, Inbound makes sense as a natural extension of your existing infrastructure.