wSMTP

Email infrastructure, minus the infrastructure

The mail server you’ll never run.

wSMTP turns your Cloudflare account into a complete email stack. Send, receive, and triage mail on your own domain — with a shared team inbox on top and no SMTP server underneath.

Create your inboxSign in

Your Cloudflare account · your domain · your data in Postgres & R2

wsmtp — delivery log
$wsmtp send --to [email protected]
→ queuedoutbound:4821
→ cloudflareemail send · accepted
→ authspf=pass dkim=pass dmarc=pass
← 250 OKdelivered in 1.2s
$which smtpd
smtpd not found← exactly.
$

Everything a mail stack does, nothing a mail server needs.

Received:

Bring your own Cloudflare

Mail flows through your Cloudflare account — Email Routing brings messages in, Email Send takes them out. Your domain stays on infrastructure you control.

To:

A real inbox for your team

A three-pane mail app with threads, folders, and shared mailboxes, so your whole organization works out of the same inbox.

X-Priority:

AI triage on arrival

Every inbound message is classified as it lands, so important mail surfaces first. Works with the model of your choice via OpenRouter.

Message-ID:

Durable by design

Messages are stored in Postgres and attachments in R2. Sending and receiving run through persistent queues, so a hiccup never drops mail.

DKIM-Signature:

Authenticated mail

Outbound mail is signed and aligned — SPF, DKIM, and DMARC handled through Cloudflare Email Send, so your messages land in inboxes.

Authorization:

Secrets encrypted at rest

Your Cloudflare credentials are encrypted with AES-256-GCM before they ever touch the database. Each tenant’s keys stay theirs.

Live in three steps

  1. 1

    Create your organization

    Register, verify your email, and connect your Cloudflare account ID and Email Send token in Settings.

  2. 2

    Point Email Routing at wSMTP

    Add your unique inbound webhook to Cloudflare Email Routing. Inbound mail for your domain starts arriving in your inbox.

  3. 3

    Send and receive on your domain

    Compose, reply, and triage from the shared inbox — authenticated outbound, classified inbound, no server anywhere.

Sending & receiving email on Cloudflare

How wSMTP uses Cloudflare Email Routing and Email Send to replace a traditional SMTP server.

Can you send and receive email through Cloudflare?
Yes. Cloudflare Email Routing delivers inbound mail to a webhook, and Cloudflare Email Send relays authenticated outbound mail. wSMTP wires both together into a real inbox, so you send and receive on your own domain without running a mail server.
Does Cloudflare provide an SMTP server?
Cloudflare doesn't give you a classic SMTP daemon to connect to. Instead it exposes Email Routing (inbound) and the Email Send API (outbound). wSMTP uses these APIs directly, so you get SMTP-style send and receive without hosting or securing an SMTP server.
Do I need to run my own mail server?
No. wSMTP runs entirely on your Cloudflare account plus a small app for the inbox. There is no Postfix, Exim, or SMTP daemon to patch, no IP reputation to warm, and nothing listening on port 25.
Is outbound mail authenticated with SPF, DKIM, and DMARC?
Yes. Outbound messages are signed and aligned through Cloudflare Email Send, so SPF, DKIM, and DMARC pass and your mail lands in the inbox rather than spam.
Whose infrastructure and data is this?
Yours. Mail flows through your own Cloudflare account and domain. Messages are stored in your Postgres database and attachments in your R2 bucket, and your Cloudflare credentials are encrypted at rest with AES-256-GCM.

Your domain’s mail, minus the mail server.

Connect Cloudflare, point Email Routing, and your team has an inbox. That’s the whole setup.

Get started