A complete guide to self-hosted email forwarding with Cloudflare: architecture, real cost, and a 30-minute setup for a privacy-focused email forwarding service on your own account.
Self-hosted email forwarding is the best way to keep your email infrastructure on infrastructure you control. In 2026, Cloudflare Email Routing makes it almost free: mail lands at the edge, and a Worker can forward, filter, and archive it — all inside your own Cloudflare account.
Managed forwarders (ImprovMX, ForwardEmail) are convenient, but they route your mail through a third party. Self-hosting with Cloudflare means the forwarding rules, the copies, and the analytics all live in resources you own. No monthly fee for a single feature, no mail sitting on someone else’s servers.
*@yourdomain
From here every inbound email hits your Worker. You can forward it, drop it, bounce it, and store a full copy in R2 before it ever reaches your inbox.
Raw Workers give you forwarding, but not much else. A management layer adds rules you can edit without touching the Cloudflare dashboard, searchable archives, and per-rule stats. This is exactly what InboxFly adds on top of the same architecture — the missing panel for Cloudflare Email Routing.
Is self-hosted email forwarding with Cloudflare free? Yes, within Cloudflare’s free tier: 100k Worker requests/day, 5GB D1, 10GB R2.
Will forwarded mail land in spam? Cloudflare routes via its own infrastructure with SPF aligned; deliverability is generally good. Final placement in the recipient’s mailbox is not observable by any forwarding service.