Browse past weeks of engineering reads.
Distinguishing between legitimate human users and sophisticated automated bots across full user journeys while minimizing false positives that create friction for real users.
How to build infrastructure that enables direct monetization of content creators in an AI-agent-driven internet where traditional search referral models are becoming obsolete.
Website owners lacked visibility into crawler behavior, traffic patterns, and the business value generated by different crawlers accessing their sites.
Security teams needed a way to automatically block traffic from known threat actors and targeted industries in real-time without manually updating WAF rules.
Uncontrolled spending on API calls to multiple AI providers due to lack of visibility and budget enforcement mechanisms.
Cloudflare needed to unify fragmented analytics data across its global edge network and enable intelligent querying of that data at scale.
Enabling developers to build conversational agents with real-time voice capabilities without requiring complex infrastructure setup.
AI agents needed a way to interact with browsers at scale while maintaining visibility and control over automated actions, requiring higher concurrency and real-time debugging capabilities.
Third-party feature flag services introduce unacceptable latency for applications requiring sub-millisecond flag evaluation at global scale.
Detecting sophisticated client-side security threats like zero-day exploits while minimizing false positives in real-time across millions of requests.
Traditional WAFs force a trade-off between logging (risking missed attacks) and blocking (risking false positives), requiring extensive manual tuning to balance security coverage with availability.
Tunnel layering in Cloudflare's WARP/One client caused MTU mismatches, leading to silently dropped oversized packets that degraded connectivity and resilience.
Cloudflare's existing server fleet could not keep pace with rapidly growing global traffic demands, requiring a new generation of hardware with significantly higher compute and network throughput.
Cloudflare needed to significantly increase edge compute throughput per server but faced a tradeoff where high-core-count CPUs came with smaller per-core L3 cache, risking latency penalties for cache-dependent workloads.