Cloudflare transactional email for WordPress: what it is, and how Flarepipe fits

Cloudflare now lets you send transactional email from your own account, without signing up for a separate SMTP company. For a WordPress site already living on Cloudflare DNS, that can mean order confirmations and password resets leave through infrastructure you already pay for. The catch: Email Sending is still in public beta, it needs a Workers Paid plan, and WordPress needs a bridge. Flarepipe is that bridge.

Two different things people keep mixing up

Cloudflare Email Sending is the mailer. It lives in your Cloudflare account, sends from Workers or a REST API, and is part of Cloudflare Email Service. Public beta opened in April 2026. It is built for transactional mail (receipts, resets, notifications), not for blasting a newsletter list.

Flarepipe Email is a WordPress plugin. It intercepts outbound site mail and posts it to Cloudflare’s send API using an API token on your account. You install it from WordPress.org or start from the Flarepipe Email product page. It is not a mailer option inside WP Mail SMTP. It replaces the usual SMTP-plugin path.

If you already compared the mailers WP Mail SMTP supports, think of Cloudflare as a path that sits outside that list, closer in spirit to wiring Amazon SES yourself than to clicking “SendLayer” in a dropdown.

What it costs (checked July 21, 2026)

Cloudflare’s own pricing page is blunt: outbound Email Sending to real recipients needs the Workers Paid plan. That plan starts at $5/month. On Email Sending you get 3,000 outbound emails included per month, then $0.35 per 1,000. Sends only to verified destination addresses in your account stay free and do not burn the quota (useful for testing, useless for customers).

Flarepipe’s free plugin covers the WordPress connection. Paid Flarepipe tiers add things like multi-site licenses and longer analytics; they do not replace the Cloudflare bill. Flarepipe also notes that edge features (queues, companion Worker) assume that same Workers Paid plan.

Compare that shape to a classic relay: SMTP2GO’s paid entry is about $15/month for 10,000, Postmark about $15/month for 10,000, Amazon SES about $0.10 per 1,000 after you survive the sandbox. Cloudflare’s headline can look cheaper at modest volume if you were going to pay for Workers anyway. If you are not on Cloudflare today, you are buying a new platform, not saving a line item.

At a glance

Path	Free / included	Entry cost shape	Setup feel	Best for	Key limitation
Cloudflare Email Sending + Flarepipe	3,000 sends/mo on Workers Paid	$5/mo Workers + usage; Flarepipe free plugin	Medium (token, domain, DNS auth)	Sites already on Cloudflare DNS	Public beta; no independent inbox score yet
SMTP2GO (via WP Mail SMTP)	1,000/mo permanent free	~$15/mo for 10k	Easy	Most small WP sites	200/day free cap
Amazon SES (via WP Mail SMTP Pro)	Low after sandbox	~$0.10/1,000	Hard	High volume / AWS-native	Sandbox + steep setup
Postmark (via WP Mail SMTP)	Testing-only free	~$15/mo for 10k	Easy	WooCommerce receipts that must land	US hosting; paid for real volume

Independent inbox-placement labs have scored SMTP2GO, Postmark, and SES. They have not published a figure for Cloudflare Email Sending yet. Treat any “enterprise reputation” claim as unverified until a neutral test lands.

Who this is actually for

You are a good fit if:

• Your domain already uses Cloudflare for DNS (or you are willing to move DNS).
• Your volume is mostly transactional: WooCommerce receipts, form notifications, password resets.
• You are comfortable pasting an API token and checking that SPF, DKIM, and DMARC still line up after the switch.

You should wait, or keep a proven relay, if:

• You need a long track record and third-party inbox scores before you touch production receipts.
• You send big marketing blasts from the same tool (this stack is not aimed at that).
• Nobody on your team can read a Cloudflare dashboard without panic.

For WooCommerce stores in particular: beta plus unknown independent deliverability means run a careful test period, not a Friday-night cutover on a sale weekend.

How Flarepipe fits on WordPress

In plain terms: install Flarepipe, add a Cloudflare API token with Email Sending permission, enter your account ID and sending domain, send a test. Flarepipe’s readme says it hooks early (pre_wp_mail) and talks to Cloudflare over HTTPS. Disable WP Mail SMTP or any other mailer plugin while you use it, or you will get double-sends and confused logs.

Flarepipe can help inject authentication records into a Cloudflare zone when you grant the right token. That is useful, and it is still not proof the receiver trusts you. After setup, run a free deliverability scan and read your SPF, DKIM, and DMARC the way Gmail and Outlook will. The plain-English guide walks through what each record is asking for if something is red.

Honest bottom line

Cloudflare Email Sending is a real option now, not a rumor. For a WordPress site already on Cloudflare, Flarepipe is the practical way to use it without standing up your own Worker. It is also early: public beta, Workers Paid required, no independent inbox-placement score yet. If your receipts pay the rent, start with a low-stakes test domain or a parallel send, not an all-in swap.

And once any mailer is wired, do not trust the “test email” button alone. Check what the receiving side actually sees.

FAQ

Is Cloudflare Email Sending the same thing as Flarepipe?

No. Cloudflare Email Sending is the mail service on your Cloudflare account. Flarepipe is a WordPress plugin that sends your site’s outbound mail through that service. One is the road, the other is the on-ramp.

Do I still need WP Mail SMTP if I use Flarepipe?

Usually no. Flarepipe takes over WordPress mail early and talks to Cloudflare’s API directly. If another SMTP plugin is still active, turn it off so the two do not fight over the same messages.

Is this ready for a busy WooCommerce store?

Treat it as early. Email Sending is in public beta, new accounts start with conservative daily limits, and no independent lab has published an inbox-placement score yet. Fine for testing and low volume if you already live on Cloudflare; keep a proven relay handy if receipts are mission-critical today.

What does it actually cost?

You need Cloudflare’s Workers Paid plan at $5 per month. That plan includes 3,000 outbound emails per month through Email Sending, then $0.35 per 1,000. Flarepipe itself has a free WordPress plugin on wordpress.org, with optional paid tiers for extras like multi-site licenses.

Cloudflare and Flarepipe prices and limits were checked July 21, 2026 and change often; re-verify on each provider’s own page before buying. Flarepipe is an independent product that interfaces with Cloudflare services; it is not affiliated with or sponsored by Cloudflare, Inc.