edge computing

Diagram of a programmable secure web gateway using Cloudflare Workers to evaluate policy and transform traffic at the edge
Cloud Services

When a Firewall Learns to Run Your Code

For nearly three decades, the logic inside a corporate secure web gateway has barely changed: a request comes in, it’s checked against a rule, and the gateway spits out one of four verdicts — allow, block, isolate, or log. That simplicity is also the ceiling. The moment a security team needs something slightly more specific — read a token, call an internal database, send a real-time alert — the gateway shrugs, and the team goes off to build another piece of infrastructure to compensate. Cloudflare’s latest announcement is interesting less because it adds a feature, and more because it attacks that ceiling directly, by letting customers run their own code inside the decision itself.

Cloudflare Traces showing a request timeline across an edge network and origin server
Cloud Services

Cloudflare Wants to Watch Every Request Pass Through Its Network — and Show You the Receipt

If you have ever tried to figure out why a single web request was slow, blocked, or simply vanished somewhere between a browser and a server, you know the ritual: open one dashboard for firewall logs, another for cache statistics, a third for application traces, and then try to line up timestamps by hand and hope they actually describe the same event. Cloudflare’s new feature, Traces, is built around a simple bet: if a huge share of the internet’s traffic already passes through Cloudflare’s network, then Cloudflare itself is in a good position to hand you one timeline instead of three disconnected logs.

Diagram showing how EmDash serves structured JSON content to both human browsers and AI agents through different request paths at the network edge
Cloud Services

Why Cloudflare Rebuilt Its Own Blog on an AI-Native CMS — and What That Says About the Next Content Stack

When Cloudflare gave its corporate blog a fresh coat of paint this August — dark mode, a cleaner layout, a redesigned subscription box — most readers probably filed it under routine housekeeping. What they didn’t see was the infrastructure overhaul underneath: the blog had quietly moved onto EmDash, a brand-new, open-source content management system that Cloudflare built for itself and is now offering to everyone else. That migration is a more interesting story than a redesign, because it doubles as a real-world stress test of an idea that, until recently, existed mostly as a pitch deck: that content management systems need to be rebuilt from the ground up for a web where AI agents read, query, and even edit content alongside humans.

Scroll to Top