Bot Preference Sync turns Cloudflare’s AI crawler controls into both an enforcement policy and a published robots.txt signal. It is rolling out to every plan, with different defaults for publishers and other sites and important limits around custom per-bot rules.
Edge Scripts no longer have to sit behind bunny.net’s automatic cache. New pre-cache hooks can execute before cache lookup, while a separate Cache API lets scripts read, write and delete regional cache entries under application control.
Cloudflare’s new MCP controls turn TLS-inspected Gateway traffic into an inventory and policy surface for remote MCP use, while explicitly leaving local stdio, off-network and uninspected traffic outside visibility.
Cloud CDN can now honor CDN-Cache-Control separately from browser-facing Cache-Control. That gives builders a standards-based way to set shared-cache behavior at the edge while preserving different client-side caching rules.
Published Updated 3 min read
CDNs began with cached files and now sit in front of applications, APIs, security controls and edge compute. That position can improve speed and resilience, but it also concentrates important routing, data and operational decisions in a provider layer.
This page follows changes in content delivery, edge runtimes, networking and web security services. BTN examines geography, limits, standards support, pricing and failure behaviour so builders can judge where an edge feature is genuinely useful. Coverage avoids treating lower latency as an automatic win; the relevant question is whether a change simplifies the whole system or moves complexity into a less visible place.
Standards and interoperability are especially important at this layer because proprietary request, data and deployment APIs can spread throughout an application. BTN follows movement toward portable primitives as well as new provider features. The practical test is whether a team gains useful reach without losing the ability to reason about requests.