Looking for a Resend alternative that runs on your own Cloudflare account?
Self-hosted on Cloudflare — data lives in your D1, not Resend's multi-tenant database. No per-email pricing once you're past their plan tiers.
Resend is a great product — it's where most teams land the first time they need transactional email that "just works." But as your stack matures, the calculus often shifts: data residency requirements, predictable cost at higher volumes, and the desire to keep the email control plane on the same host as the rest of your infrastructure.
Flowmails is what you ship when those are the things you've started to care about. It runs on Cloudflare — the same one your Workers, R2 buckets, and Pages deployments already live in — and stores your inbox, outbox, and routing rules in your own D1. There is no per-email fee on top of Cloudflare's own pricing; the platform subscription is what you see on the /price page.
Resend's free tier caps at 100 emails/day and 3,000 / month; paid plans start at $20 / month for 50,000 emails. Flowmails' Base plan is $0 forever; Pro is $9.9 / month regardless of volume (Cloudflare's own usage is billed by Cloudflare directly).
Resend is a hosted API — sign up, verify your domain via DNS, call the API. Flowmails deploys a Worker into your Cloudflare account and provisions the D1 + R2 in your name; no separate billing relationship.
Resend: zero-ops teams who want the fastest possible first-send. Flowmails: teams that need data residency, predictable cost, and a self-hosted control plane they can audit.
Both expose a Node SDK and a REST API. Resend's SDK runs in any runtime; Flowmails' SDK is the same shape and additionally targets Cloudflare Workers, Bun, and Deno out of the box.
Highlights
What Flowmails does differently
Data residency
Your D1 in your Cloudflare account
Inbound webhook
Yes
Self-hosted runtime
Yes — Worker in your account
Custom-domain setup
Cloudflare Email Routing auto-configured
Per-email pricing
No (Cloudflare bills usage directly)
Audit / export
Direct D1 SQL dump
Migration
How to migrate from Resend to Flowmails
Move DNS to Cloudflare (or keep it there)
If your domain is already on Cloudflare, skip this step. Otherwise add the zone to Cloudflare — Flowmails relies on Email Routing and Email Services, which require an active Cloudflare zone.
Connect Flowmails with a scoped API token
Flowmails provisions the receive Worker, the D1 database, and the R2 bucket using a Cloudflare API token you mint. The token's permission list is documented in the Cloudflare API token permissions post.
Swap the sending path
Replace `Resend` SDK calls with the Flowmails SDK, point it at the new API key, and ship templates as plain HTML / text — Resend's templates are not locked to its own renderer.
FAQ
Common questions about switching from Resend
Other alternatives