This discussion thread revolves around the announcement of Cloudflare’s new Email Sending service (a transactional email tool integrated with Cloudflare Workers). The launch immediately sparked a widespread debate among users regarding the increasing centralization of internet infrastructure under Cloudflare. Critics express significant concern that the company is becoming an unchecked “quasi monopolist” and “global gatekeeper,” capable of deciding who accesses content, and fear future vendor lock-in or data exploitation (e.g., selling user data for ads). Counterarguments defend Cloudflare, emphasizing that their services are essential for mitigating severe threats like DDoS attacks and bot traffic, making the internet functionally "better" for website operators. The discussion also touches upon the technical difficulties of self-hosting email and the high cost of existing transactional email providers, underscoring the market need Cloudflare is attempting to fill by offering a potentially simpler and cheaper alternative to services like AWS SES and SendGrid.
Cloudflare's Email Service: Debate on Centralization and Utility
Cloudflare’s New Service: The announced service is a private beta for an email sending capability (similar to SendGrid or AWS SES) integrated with Cloudflare Workers, allowing transactional emails to be sent via Workers, REST APIs, or SMTP.
Centralization Concerns: Many commentators view the expansion into email as further evidence of Cloudflare becoming a dangerous "single point of interception" and gatekeeper of the internet. They fear this concentration of power makes the internet vulnerable to censorship, government pressure, and future business model changes (e.g., selling user data) (mosura, egorfine).
The Necessity Argument: Defenders argue that Cloudflare provides vital services, particularly DDoS mitigation and bot traffic reduction, which are necessary for businesses to operate safely and affordably. They contend that the internet is "worse without Cloudflare" because bad actors dominate traffic without proper defense (stingraycharles, r00f).
Negative User Experience: Several users complained about Cloudflare’s aggressive security measures, noting frequent frustrations with constantly being blocked or forced to solve captchas, particularly when using residential CGNAT, mobile routers, or VPNs, which they feel impedes freedom of access (segmondy, jasonvorhe).
Competition and Pricing: Users currently relying on competitors like SendGrid (which recently eliminated its free tier) and AWS SES are interested in Cloudflare’s offering, hoping for better pricing, especially for low-volume projects, and improved usability compared to the complex AWS interface.
Challenges of Email Hosting: A significant tangent acknowledged that self-hosting email has become extremely difficult due to the IP reputation systems enforced by giants like Gmail and Microsoft, validating the need for commercial intermediaries to ensure deliverability (matheusmoreira, parliament32).
Vendor Trust: Concerns remain about potential future risks, including vendor lock-in and the possibility of the company shifting its current policy against selling user data or ads, particularly under future leadership (kalaksi, mike_d).