The discussion thread centers on Cloudflare's announcement of its new "Email Sending" service, available in private beta, allowing transactional emails to be sent directly from Cloudflare Workers via bindings, REST APIs, or SMTP. This development is viewed with both excitement for its developer convenience—integrating email into the existing Cloudflare ecosystem (Workers, R2, etc.)—and significant apprehension regarding increased centralization of the internet. Critics argue that Cloudflare is becoming an unavoidable single point of interception (a "master of the Internet") across web traffic and now potentially email, potentially leading to gatekeeping, reduced freedom, and vendor lock-in, similar to concerns raised about Google. Supporters counter that the service addresses real-world issues like DDoS attacks, that competition is lacking from major players like Google, and that for many users (especially small projects), convenience and cost savings outweigh philosophical concerns about centralization. There is also substantial discussion regarding the difficulties and economics of self-hosting email versus using specialized transactional email providers like SendGrid (which recently ended its free tier), Postmark, and newer alternatives.
Summary: Cloudflare Email Service Launch and Centralization Debate
0:00 Cloudflare's New Service: Cloudflare announced the private beta for Email Sending, enabling transactional emails directly from Cloudflare Workers using bindings, plus REST APIs or SMTP for external applications.
335 points Initial Reaction: The announcement sparks immediate debate about Cloudflare's growing influence, with one user suggesting "Eventually all Internet protocols will be MITMed by cloudflare."
1:00 Debate on Service Necessity vs. Freedom: Users discuss whether Cloudflare improves or worsens the internet experience.
Pro-CF: Provides necessary protection against bots/DDoS, offers a good service where competitors (like Google) do not compete effectively.
Anti-CF: Leads to centralization, enabling Cloudflare to unilaterally decide who reads content, posing a risk if laws mandate censorship or if the company's goals shift.
3:00 CAPTCHA/Access Issues: Several users report frequent issues being blocked or repeatedly forced to solve CAPTCHAs when accessing Cloudflare-protected sites, particularly from shared/residential IPs or mobile routers.
3:00 Self-Hosting Email (The Counter-Argument): A significant tangent explores the viability of running personal email servers.
Claim: Some argue self-hosting is easy with modern tools (Docker, services like Mailu), good reverse DNS, SPF, and DKIM records, and offers superior privacy compared to big providers.
Counter-Claim: Others state that IP reputation systems (Gmail, Outlook) make outbound email delivery nearly impossible without warming up IPs or paying intermediaries, making self-hosting impractical for reliable delivery unless one acquires dedicated RIR address space (IPv4 address space is scarce).
4:00 Transactional Email Market: Discussion highlights the high cost and changing terms of incumbent transactional providers.
SendGrid: Recently killed its free tier (100/day), with the lowest plan now being $20/month for 50k emails, deemed overkill for small projects.
Alternatives Mentioned: Resend, Zeptomail (Zoho), Mailpace ($40/year for 1k/month), and SMTP2Go (free tier up to 1k/month or 200/day).
10:00 Cloudflare Ecosystem Strategy: Users recognize Cloudflare is deliberately expanding its platform (Workers, R2, Hyperdrive, now Email) to become a complete infrastructure solution, competing with AWS.
17:00 Trust and Centralization: A core theme is the danger of placing critical infrastructure (Web traffic via DNS/CDN, and now Email Sending) with a single entity.
Vendor Lock-in: Concerns are raised about unravelling services if one chooses to migrate away from the bundled Cloudflare offerings.
Principle vs. Convenience: Many acknowledge the philosophical cost of centralization but admit the convenience and protection offered by Cloudflare are compelling for practical business needs (e.g., avoiding DDoS attacks).
21:00 Previous Email Attempt Recalled: A user notes Cloudflare previously offered email sending via MailChannels integration with Workers, which was later killed, leading to skepticism about the longevity of the new native service.
22:00 Need for Features: Users expressed hope the new service will support features like idempotency keys (to prevent duplicate sends) and offer pay-as-you-go pricing rather than fixed tiers.