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 was built to solve this more cleanly. Your domain provider routes inbound mail to a dedicated address for your domain, and the platform takes it from there, so you get managed routing without needing to operate your own mail transfer agent.
How it works
When you add a domain to Flowmails, you connect your domain provider. Incoming messages to your domain are captured by that provider's mail routing layer and forwarded to Flowmails, where a shared receive worker decides which addresses are accepted. You manage that list from the dashboard — it is enforced by the worker itself, not by rules written into your provider account.
Cloudflare is the routing provider we support today — one option among several as the provider interface expands. The same onboarding flow works with any provider that supports email routing, so choosing Cloudflare is a default, not a commitment.
For outbound email, each domain picks its own channel: outbound goes through the provider you chose for that domain — Cloudflare Email Sending or Resend. On the Cloudflare path your sender reputation ties directly to your Cloudflare zone, and on either path you avoid the complications of relaying through an unrelated third-party SMTP provider.
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 the outbound provider you chose for that domain. 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 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 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 is built for product teams and operators who want email routing to fit the domain provider they already use. If your domains are on Cloudflare and you need to route mail without adding another third-party vendor, Flowmails fits naturally into that workflow — and the same is true for the other providers we support.
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 takes a few minutes. You add your domain, connect your domain provider, and define your routing rules through the dashboard — the platform writes the DNS records and the forwarding rules for you. Once your provider 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.