# Cloudflare Email Service

Hacker Approved page: https://hackerapproved.com/p/cloudflare-email-service/

19 people recommended Cloudflare Email Service in Hacker News comments, 6 had mixed feelings and 21 criticized it, November 2025 to October 2026. It was recommended in 5 of 12 months, in 8 threads. It does not meet the Hacker Approved badge rule.

13 of the 19 people who recommend it commented in one thread, “Cloudflare Email Service: now in public beta. Ready for your agents”.

**Verdict:** More people criticize it than recommend it. Cheap per-email pricing and tight integration with Cloudflare Workers and other tools people already use. Most common caveat: no SMTP interface yet, and agent-sent mail may hurt deliverability.

Summary written by Claude from the comments below.

## What people warn about

- Hype and AI marketing criticized (4 comments in the sample): "Of course it's just marketing, but that doesn't mean it's above criticism, especially when it's shoved so hard down our throats." ([source](https://news.ycombinator.com/item?id=47794519)) "All the examples they show in the blogpost are just things that were already pretty easy without agents." ([source](https://news.ycombinator.com/item?id=47794010)) "launch the same service that’s been around for decades but slap ai and agent on it" ([source](https://news.ycombinator.com/item?id=47794377))
- Limited sending options, no SMTP (3 comments in the sample): "Doesn’t look like it has parity with being able to send email from many subsystems safely" ([source](https://news.ycombinator.com/item?id=47794596)) "Seems like you can only send email via the worker or REST API for now?" ([source](https://news.ycombinator.com/item?id=47795371)) "without SMTP support, the email sending service is mostly unusable" ([source](https://news.ycombinator.com/item?id=47813280))
- Agent mail risks spam and deliverability (3 comments in the sample): "Agent-produced emails are by definition spam. Everyone should be reacting to this news by immediately blocking your service." ([source](https://news.ycombinator.com/item?id=47799350)) "Why would Cloudflare ruin their email deliverability by allowing this?" ([source](https://news.ycombinator.com/item?id=47799312)) "If I get one email from your agent, I'm torching your entire domain." ([source](https://news.ycombinator.com/item?id=47794777))
- Cloudflare abuse handling criticized (2 comments in the sample): "Cloudflare is very transparent about their prefixes and reverse DNS, which makes it trivial for operators who want to block the entire service" ([source](https://news.ycombinator.com/item?id=47794144)) "Cloudflare is (in)famous for not acting against spammers, fraud, piracy and other less savory groups" ([source](https://news.ycombinator.com/item?id=47794530))

## Why people recommend it

- Cheaper than common email APIs (3 comments in the sample): "Pricing is decent, but imho that is the true value proposition here." ([source](https://news.ycombinator.com/item?id=47800604)) "Cloudflare is way cheaper compared to eg Sendgrid or Postmark." ([source](https://news.ycombinator.com/item?id=47801623)) "$0.35 per 1,000 emails it's fair pricing." ([source](https://news.ycombinator.com/item?id=47793793))
- Integrates with existing Cloudflare tools (2 comments in the sample): "it has everything you would expect like SDKs, binding, observability and more coming on the way" ([source](https://news.ycombinator.com/item?id=47795133)) "I am grateful this now exists and integrates directly with tools I have on cloudflare already" ([source](https://news.ycombinator.com/item?id=47797555))
- Easy, batteries-included setup (2 comments in the sample): "this service is batteries included. S3 is not." ([source](https://news.ycombinator.com/item?id=47801010)) "it's been super easy so far" ([source](https://news.ycombinator.com/item?id=47798309))
- Each agent gets its own identity (1 comment in the sample): "Each agent gets its own identity from a single domain." ([source](https://news.ycombinator.com/item?id=47796873))

## Other email sending services people recommend

- [Amazon SES](https://hackerapproved.com/p/amazon-ses/): 12 recommend, 3 mixed, 11 criticize
- [Postmark](https://hackerapproved.com/p/postmark/): 8 recommend, 0 mixed, 1 criticize
- [AWS SES](https://hackerapproved.com/p/aws-ses/): 7 recommend, 1 mixed, 5 criticize
- [SMTP2GO](https://hackerapproved.com/p/smtp2go/): 7 recommend, 0 mixed, 1 criticize

## Where to get it

- [Visit the official site](https://www.cloudflare.com/)

## The badge

A product earns the Hacker Approved badge when at least 10 people recommend it, recommenders outnumber critics at least 2 to 1 (mixed feelings count toward neither side), it was recommended in at least 4 of the 12 months and in at least 5 different threads, and no single thread supplies more than half of the people who recommend it. Health and money products are never badged.

## Cite as

Hacker Approved, "Cloudflare Email Service", https://hackerapproved.com/p/cloudflare-email-service/ (19 recommend, 6 mixed, 21 criticize; Hacker News comments, November 2025 to October 2026).

Counts updated 3 Nov 2026, with data through October 31, 2026.
