Cloudflare's original appeal was that it made the Internet feel simpler. Put Cloudflare in front of your application and it would handle DNS, CDN delivery, DDoS absorption, WAF filtering, TLS termination, and routing on a global edge network.
DNS CDN DDoS protection WAF TLS termination Global routing
The mental model was clean:
User -> nearest Cloudflare edge -> origin
That model works because most of the work is stateless. Requests can be cached, blocked, rewritten, or proxied without dragging application state into every edge location.
Cloudflare's strongest early model was request processing near the user without deep coordination.
Request comes in Cloudflare processes it near the user Request is cached, blocked, routed, rewritten, or proxied
For CDN caching, bot checks, WAF rules, redirects, and TLS handling, that simplicity is real.
Workers shifted the platform from "we protect your app" to "run your app logic on our network."
Workers KV R2 D1 Durable Objects Queues Workflows Containers AI Vectorize
At that point Cloudflare stops being only a network edge and starts behaving like an application cloud.
Stateless compute can run almost anywhere. Stateful applications cannot ignore locality, replication, and legal boundaries.
Where does the data live? Where does code execute? Where do writes go? Where do reads come from? Can replicas lag? Which region is legally allowed?
Cloudflare wants the developer experience of deploy once, run globally. Real workloads demand much tighter control.
The ambition is not just to sit in front of the app anymore. The ambition is to become the place where the app itself runs, and state is what makes that hard.