Resend alternative
One API · any provider

Looking for a Resend alternative that also handles inbound mail?

Flowmails sits on top of the provider you already chose — inbound mail, route tables, an event log and a hosted mailbox in one place, with no per-email markup from us.

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 own the whole mail surface — inbox, route table, events and outbound — behind one API instead of three vendors.

Flowmails is what you ship when those are the things you've started to care about. It connects to your domain provider over OAuth and runs one shared mail worker for every tenant, so your inbox, outbox, and route table live in one place, scoped to your domain. There is no per-email fee on top of your provider'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 and Enterprise is $39.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 connects your domain provider over OAuth and runs one shared mail worker for every tenant; outbound goes to Resend or Cloudflare Email Sending, whichever you pick per domain.

Resend: zero-ops teams who want the fastest possible first-send and outbound only. Flowmails: teams that need inbound mail, route tables and an agent-usable API alongside outbound, on one connection.

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

Flowmails' own storage, scoped by domain id

Inbound webhook

Yes

Hosted mail worker

Yes — one shared worker, inbound + outbound

Custom-domain setup

Cloudflare Email Routing auto-configured

Per-email pricing

No (your provider bills you directly)

Audit / export

API export, documented schema

Migration

How to migrate from Resend to Flowmails

    01

    Point your domain's routing at Flowmails

    If your domain is already on Cloudflare, skip this step. Otherwise the domain needs an active provider zone — Cloudflare is the routing provider we support today, and the provider SPI is open to others, so more are on the way.

    02

    Connect Flowmails with an OAuth sign-in

    Flowmails connects to your provider over OAuth — no API token is pasted and none is stored. The grant has a bounded lifetime, and Flowmails provisions the shared mail worker, the storage and the route table for you.

    03

    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

All Flowmails alternative pages