AI

How Cloudflare helps you democratize AI access for your teams, developers, and applications — without losing visibility, security, or your budget. TL;DR — In part one of this series, I covered the AI traffic hitting your infrastructure from the outside — crawlers, training bots, the broken value exchange between content creators and AI platforms. This post is the mirror image: the AI your organization reaches out to, every day, across every team — and why that consumption is far less controlled than most organizations realize. Shadow AI usage, fragmented provider accounts, API keys scattered across codebases, and no centralized data governance are the norm, not the exception. The real challenge isn’t getting your teams to use AI — they already are. It’s building the infrastructure layer that makes that adoption sustainable, secure, and cost-controlled. Cloudflare’s AI Gateway, combined with the broader Cloudflare developer platform, is that layer. Not because of what it says on a product page, but because of what I see in the field. ...

Disclaimer: This post reflects my own synthesis and perspective on publicly available Cloudflare research and announcements — it does not represent an official Cloudflare position. TL;DR — AI crawlers now represent a structural threat to how the web creates and distributes value. They consume content at massive scale, send little traffic back, and are quietly degrading CDN performance for real users. This post covers how Cloudflare is responding — not just with bot controls, but with a coherent platform: cryptographic bot identity (co-authored as an IETF standard), content monetization via Pay Per Crawl, token-efficient delivery for agents, a pub/sub AI Index to replace blind crawling, AI-aware cache architecture, and a secure execution layer for agentic code. Each piece reinforces the others. Together they represent Cloudflare’s answer to the question: what should the AI-era internet actually look like? ...

Disclaimer: This article reflects my personal views and experiences and does not represent the official stance of Cloudflare. It is not an official Cloudflare tutorial or documentation. The project discussed is a personal initiative created independently. The Moment I Realized Simple Wasn’t Enough “It works perfectly!” I remember telling myself three months ago, watching Claude query my Cisco Meraki network in real-time. The AI assistant could check device status, monitor client connections, and even troubleshoot network issues—all through a simple API key I’d hardcoded into my Cloudflare Worker. ...