Cloudflare Email Routing is a strong free choice when you want inbound mail for a custom address forwarded to an inbox you already use. A full mailbox provider becomes relevant when a team needs hosted inboxes, IMAP/client access, per-user administration, retention, or a single system for normal person-to-person sending and receiving.
There is an important 2026 update: Cloudflare Email Service now also documents an Email Sending beta for transactional mail on Workers Paid, available through Workers, REST, and authenticated SMTP. That expands Cloudflare beyond inbound forwarding, but transactional application sending is not the same product as a hosted multi-user mailbox service. This comparison separates those use cases instead of claiming Cloudflare has no outbound capability.
What Cloudflare Email Routing and Email Sending Do
Cloudflare Email Routing maps an address pattern to a verified destination address or an Email Worker. It is useful for addresses such as hello@example.com when the person wants messages delivered to an existing inbox.
Routing does not create an independent stored mailbox that users sign into through IMAP or a mailbox web client. A user can still send from the custom address through a separately configured provider’s authenticated “send as” or SMTP feature, subject to that provider’s rules. The old blanket claim that replies must come from the personal identity was therefore too broad.
Cloudflare Email Sending beta, documented in June 2026, supports transactional messages such as notifications and password resets. It is designed around applications and APIs. Teams evaluating human employee mail should separately verify inbox storage, search, drafts, folders, calendar, delegation, retention, recovery, and administrator workflows.
When to Stay on Cloudflare
Stay with Cloudflare when all of the following are true:
- users are happy to receive custom-domain messages in existing destination inboxes;
- there is no need for a separately hosted mailbox at the custom domain;
- outbound person-to-person mail is handled by a properly authenticated external send-as/SMTP setup, or outbound is not needed;
- transactional application email, if required, fits the current Email Sending beta, plan, quota, and compliance requirements;
- the team accepts managing routing rules, verified destinations, and any Worker logic.
Moving providers simply because forwarding is free is not an upgrade. Move when a specific mailbox, administration, retention, migration, or workflow requirement is missing.
How the Alternatives Were Selected
This is a focused shortlist, not a ranking of the entire email market. It compares three common upgrade paths against Cloudflare as the baseline:
- a mail-focused, flat-rate, multi-domain service;
- a polished hosted email-and-calendar service;
- a business productivity suite in which email is one component.
Features and prices are based on the providers’ public pages checked July 23, 2026. Prices vary by region, tax, billing term, and promotion; verify the checkout price and current limits before purchase.
TrekMail: Mail-Focused, Multi-Domain Hosting
TrekMail fits teams that want real mailboxes across one or more custom domains without buying a productivity suite for every user. Nano is a free evaluation/BYO-SMTP path. Starter adds managed SMTP at $4 month-to-month or $3.50/month on annual billing. Pro is $10 month-to-month or $8/month on annual billing.
The tradeoff is explicit: TrekMail does not replace Google Docs or desktop Microsoft Office. Compare mailbox limits, pooled storage, aliases, API access, migration tooling, and support on the current TrekMail pricing page.
Fastmail: Hosted Email and Calendar Polish
Fastmail fits users who value a mature mail, contacts, and calendar experience and do not need a larger office suite. Its business plans support custom domains and shared business addresses; plan capabilities differ for storage, third-party client access, retention, and administration.
Fastmail pricing is per user and varies with plan and billing duration. Use the official Fastmail pricing and feature table rather than relying on an old fixed price quoted in a comparison article.
Google Workspace: Email Plus Collaboration Suite
Google Workspace fits teams that actively use Gmail together with Docs, Sheets, Drive, Meet, and Google administration. As of the check date, the public US annual-commitment price for Business Starter is $7 per user per month before tax and temporary promotions.
Workspace may be poor value when the organization pays for other collaboration tools and wants only email. It may be excellent value when it replaces several tools employees already use. Verify current editions and terms on the official Workspace pricing page.
Comparison Table
| Option | Inbound model | Human mailbox | Outbound model | Storage/admin | Best fit |
|---|---|---|---|---|---|
| Cloudflare Email Routing | Forward to verified destinations or Workers | No independent hosted inbox from Routing | External send-as/SMTP; separate Email Sending beta for transactional use | Routing rules and Worker logic; destination inbox stores human mail | Forwarding-first setups and application routing |
| TrekMail | Hosted custom-domain delivery | Yes | BYO SMTP on Nano; managed SMTP on paid mail plans | Pooled storage, domains, mailboxes, and aliases vary by plan | Mail-focused and multi-domain teams |
| Fastmail Business | Hosted custom-domain delivery | Yes | Managed sending | Per-user storage and admin features vary by plan | Email/calendar experience without a full office suite |
| Google Workspace Business Starter | Hosted custom-domain delivery | Yes | Managed sending | 30 GB pooled storage per user plus suite administration | Teams using Google collaboration tools |
The table intentionally includes Cloudflare as the baseline and avoids calling any paid option “best” or “cheapest” without a defined team size and feature requirement.
Migration and Coexistence
Changing MX records moves inbound delivery for the domain. Multiple MX records are not a way to assign individual recipients to different providers; they express server preference and failover. Recipient-level splitting requires a receiving gateway with routing/dual-delivery rules, or separate subdomains.
For a low-risk migration:
- Inventory every routing rule, destination, catch-all, alias, Worker, and send-as configuration.
- Create and test destination mailboxes before changing MX.
- Configure and validate SPF, DKIM, and DMARC for every legitimate sender.
- Lower DNS TTL in advance where practical; DNS completion time still varies by resolver and previous TTL.
- Keep old destinations active during a defined coexistence window.
- Test inbound, replies, new outbound messages, forwarding loops, attachments, spam placement, and account recovery.
- Document the MX rollback values before cutover.
Decision Checklist
- Only forwarding needed? Stay on Cloudflare Email Routing.
- Application transactional sending needed? Evaluate Cloudflare Email Sending beta alongside dedicated transactional providers; confirm quotas and production readiness.
- Actual hosted inboxes across many domains? Compare mail-focused providers such as TrekMail.
- Mail and calendar experience is the priority? Compare Fastmail.
- Google collaboration suite is used by most seats? Compare Workspace as a bundle.
Start from the missing capability, pilot with non-critical addresses, and keep a tested rollback. For a broader cost model, see business email pricing and the business email decision tree.
Worth adding what a real mailbox buys beyond the ability to send. Storage you can search — across every mailbox at once, not one at a time. Addresses several people can work, with membership rather than a forwarding rule. Server-side filters that run at delivery on every device. And file storage attached to the same account. Free forwarding is genuinely good at forwarding; the gap opens the moment the domain is one people actually work in.
