Cloudflare Keeps Expanding, and Not Everyone Is Happy
Cloudflare launched self-managed OAuth for all, and the reaction in the HN thread was skeptical. Several commenters argued that Cloudflare is drifting away from the thing it did really well, which was making the hostile web manageable for small operators, and toward becoming a generic cloud platform competing with AWS and GCP. The concern is that as Cloudflare chases cloud revenue, the specific product advantages that attracted independent builders will erode.
This is a recurring tension for infrastructure companies that start with developer love and then try to expand upmarket. The OAuth launch itself is a platform move, giving third parties delegated access to Cloudflare accounts, which commenters read as Cloudflare trying to build an app ecosystem rather than just an infrastructure layer.
The Nub toolkit for Node.js landed the same day, showing that developers are still hungry for zero-config, all-in-one tooling. Bun set expectations high, and builders want that experience across more of the stack.
So what?
Founders using Cloudflare for edge deployment and DNS should watch whether pricing and product focus shift as Cloudflare competes more directly with the hyperscalers. The more forward-looking signal is that developer tooling which removes friction, think Bun, Nub, RubyLLM for AI integrations, keeps finding audiences fast, and the bar for 'good enough' keeps rising.