Email routing is one of those problems that seems simple until you actually need it. You have a domain, you want emails sent to addresses on that domain to land somewhere useful, and ideally you want to send from addresses on that domain without managing a full email server. Most teams end up cobbling together MX records, forwarders, and third-party services that were designed for something else entirely.
Flowmails CF was built to solve this more cleanly. The platform routes email through Cloudflare's infrastructure, so you get the reliability and global distribution that Cloudflare provides, without needing to operate your own mail transfer agent.
How it works
When you add a domain to Flowmails CF, you configure Email Routing through Cloudflare. Incoming messages to your domain are captured by Cloudflare's mail routing layer and forwarded to destination addresses you specify. The routing rules are managed through a straightforward control plane that lives alongside your other Cloudflare zone settings.
For outbound email, Flowmails CF uses Cloudflare Email Services to send directly from your domain. This means your sender reputation ties directly to your Cloudflare zone, and you avoid the complications of relaying through third-party SMTP providers.
Built on Workers
The routing logic runs as a Cloudflare Worker, which means it executes at the edge, close to where your users are. The Worker handles address resolution, forwarding rules, and the mechanics of passing messages to Cloudflare Email Services. Because it is Workers under the hood, the platform inherits the security properties and performance characteristics that come with that runtime.
The architecture also means the control plane is itself a Worker. Operators interact with it through the dashboard, and the same API surface that serves the UI can be called directly if you need programmatic access to routing configuration.
What it is not
Flowmails CF is not a marketing email platform. It is designed for transactional and operational mail, not high-volume campaigns. If you need to send bulk marketing email, you should look elsewhere. The platform also does not provide inbox placement services or detailed email analytics beyond basic delivery status.
It is also not a general-purpose mailbox service. Flowmails CF routes email to destinations you control, whether that is another email provider, a ticketing system, or a custom inbox you manage. It does not host mailboxes itself.
Who it is for
Flowmails CF is built for product teams and operators who already use Cloudflare and want email routing that stays within that ecosystem. If you run your domains through Cloudflare and you need to route mail without adding another third-party vendor, Flowmails CF fits naturally into that workflow.
It also works well for teams that want more control over their email routing without operating their own mail transfer agent. The platform handles the operational complexity so you can focus on your product.
Getting started
Setting up Flowmails CF takes a few minutes. You add your domain, configure DNS records to enable Email Routing, and define your routing rules through the dashboard. Once Cloudflare verifies your domain setup, email routing is active immediately.
The platform is designed to stay out of your way once it is running. There are no additional agents to deploy, no recurring configuration to manage, and no separate routing infrastructure to maintain.
