Run a self-hosted email API on your own Cloudflare account. The routing layer runs as a Workers-native delivery path, inbox and outbox data stays in your D1, automation goes through a REST API, and AI draft + reply is on the way. No SMTP server, no third-party lock-in.
Inbox and outbox live in your own D1, attachments in your R2, and outbound sends go through Cloudflare Email Services — no SMTP relay, no shared multi-tenant table, no third-party lock-in. The default route table catches every inbound; route templates fan out to Slack, your CRM, or any Workers webhook; AI draft + reply (Q3 2026) lives one click away from any inbound.
[runtime] flowmails-worker connected flowmails.net → D1 (WEUR)› inbound POST /webhook 200 OK in 38ms› D1 row inserted: messages.id=8421› routing rule matched: support@yourdomain.com → D1› AI draft queued (Workers AI, ~1.2s)Runtime: platform-servicesD1: PLATFORM_DBR2: unbound
Runtime · at a glance
Every Flowmails message traverses the same runtime: Email Routing captures inbound mail, your Worker writes it to your D1, and Email Services handles the outbound side. There is no shared multi-tenant table, no SMTP relay to operate.
Why teams pick Flowmails
How it works
Paste a scoped API token. Flowmails provisions a Worker in your account, claims the D1 database, and prepares the R2 bucket for attachments — none of which leaves your Cloudflare.
Pick a zone you already host on Cloudflare. DNS records are detected automatically; you approve the routing rules and the zone flips to active in under a minute.
Use the dashboard for human workflows, or hit the REST API from your service code. Webhooks stream inbound events as they happen; messages and rules live in your D1.
What you get
Every inbox, outbox, and routing rule is stored in the D1 database of the Cloudflare account you control. No vendor holds your correspondence, no shared multi-tenant table, and no migration tax if you ever leave.
$ wrangler d1 create flowmails
✅ Successfully created DB 'flowmails'
id = 8421ce9c-1f44-4c8d-b9a3-d6f5fc20ab3aInbound mail is captured by Cloudflare Email Routing and forwarded through your Worker. Outbound mail is sent through Cloudflare Email Services with your domain's sender reputation tied directly to your zone.
$ curl -X POST https://flowmails.net/api/v1/messages \
-H "Authorization: Bearer fm_live_…" \
-d '{"to":"hi@yourdomain.com","subject":"hi"}'
{ "id": "msg_8421", "status": "queued" }List messages, send mail, manage routing rules, and rotate API keys over HTTPS. Webhooks fire on inbound events so your backend can react in real time without polling.
POST /api/v1/webhooks
{ "event": "inbound.received",
"domain": "yourdomain.com",
"message_id": "msg_8421" }Coming in Q3 2026: model-backed drafting, auto-reply, summarization, and routing. Inference runs on Workers AI by default; your prompt templates and history stay in your D1.
{ "model": "@cf/meta/llama-3-8b-instruct",
"scope": "domain:yourdomain.com",
"prompt": "draft reply to support ticket #8421",
"data_residency": "your-d1" }Who it's for
Replace the cobbled-together MX forwarder with a single Worker. Send transactional email from `hello@yourdomain.com` without ever touching an SMTP relay.
Route support@, billing@, and abuse@ into a shared inbox, then pipe events into your CRM or ticketing system through webhooks.
Manage custom-domain email for every client from one dashboard. Per-domain API keys, per-domain Workers, and isolation you can show in a SOC 2 review.
When the requirement is 'email data never leaves our infrastructure', a self-hosted D1 backend is the answer — not a marketing claim.
Send order confirmations, password resets, and receipts from a Workers-native REST API — no SMTP relay, no separate SaaS to babysit.
Drafting, auto-reply, and summarization run on Workers AI by default. Your prompt templates, the messages used as context, and the resulting drafts all stay inside your D1. Disable AI per-domain or wire a different model provider.
{ "model": "@cf/meta/llama-3-8b-instruct",
"scope": "domain:yourdomain.com",
"prompt": "draft reply to support ticket #8421",
"data_residency": "your-d1" }FAQ
From the journal
A Cloudflare-native email routing platform that keeps your inbox and outbox in your own D1, with a REST API on top.
ReadThe exact scopes Flowmails needs, the principle of least privilege, and the audit trail you can show your security reviewer.
ReadWhy most transactional-email providers are overkill for a Cloudflare-native team, and how Cloudflare Email Services + a Worker gets you there in a day.
ReadThe architectural case for putting inbox and outbox in your own D1 database, and what that means in practice for compliance, exports, and exit plans.
ReadShip it on your Cloudflare
Self-hosted email in your Cloudflare account, live in about a minute. The Worker, the D1, the R2 — all yours.