The Managed Way To Replace Brevo

Not quite, because this was built by people who run sites. There is a test send because setup fails in predictable ways, and there is a log because the ticket we answer most often is somebody saying an email never arrived.

Cloudflare Email Service is still in beta, and Cloudflare notes that features and APIs may change before general availability. Email Sending reached public beta in April 2026. Plenty of sites run it in production, but you should make that decision knowingly rather than assume it carries the same stability guarantee as a mature product. The email log helps, since you can watch real delivery behavior instead of guessing.

The plugin is published on the WordPress Plugin Directory, so you can install it straight from the Plugins screen in your own admin without downloading a file. Questions about the plugin itself come to us. Questions about your Cloudflare account, your plan, domain onboarding, or API tokens go to Cloudflare, since we cannot see or change anything inside your account.

It makes WordPress send its email through Cloudflare Email Service instead of your web server. The plugin replaces the wp_mail function, so core notifications and anything a plugin sends both go to Cloudflare through its Email Sending API. It also records every send in a log, lets you set the from name and from address site-wide, and gives you a test send to confirm the setup works.

Yes. The plugin costs nothing, has no paid tier, no license key, and no features held back behind an upgrade. You install it from the WordPress Plugin Directory the same way you install any other free plugin. What is not free is the sending service behind it, which belongs to Cloudflare rather than to us. That distinction matters enough that we cover it in the next answer.

Yes, on Cloudflare’s side. Email Sending is available on the Cloudflare Workers Paid plan, so you need that plan on the account you send from. You also need the sending domain onboarded for Email Sending on the account that owns your API token. The plugin cannot work around either requirement. If you already run Workers Paid, there is nothing further to buy.

It is Cloudflare’s email product for developers, combining outbound sending with inbound routing under one service. It is built for transactional mail: password resets, order confirmations, verification messages, and alerts. You can reach it from Workers using a native binding, from any platform over its REST API, or over authenticated SMTP. This plugin uses the REST API, which is what lets ordinary WordPress talk to it without custom code.

Email Routing handles mail coming in, forwarding messages sent to addresses on your domain somewhere else. Email Sending handles mail going out. They sit under the same Cloudflare Email Service umbrella but solve opposite problems. This plugin is concerned only with outbound mail from your WordPress site, so Routing is not required, and switching it on will not make your site’s email start sending.

Three things. A Cloudflare account on the Workers Paid plan, the domain you intend to send from onboarded for Email Sending on that account, and a Cloudflare API token with permission to send. Have those ready before you install, because the plugin’s job is to use them, not to create them. Setup inside WordPress takes a couple of minutes once the token is in hand.

Install and activate the plugin, then open its settings screen. Enter your Cloudflare Account ID and paste your Cloudflare API token. Set the from address and from name you want the site to use, save, then run the test send. If the test message arrives, WordPress is sending through Cloudflare and you are done.

Yes, as long as the plugin sends through wp_mail, which the overwhelming majority do. Because this plugin replaces wp_mail itself rather than hooking one plugin at a time, anything built on the standard WordPress mail function is covered the moment you activate it. The rare exception is a plugin that opens its own connection and bypasses wp_mail entirely. Those are uncommon.