What Is Kitesurf? Inside Cloudflare's Browser Built for AI Agents Kitesurf is a browser Cloudflare shipped on August 6, 2026, built specifically to be driven by an AI agent instead of a human. It's not a trimmed down Chromium and it's not a wrapper around Puppeteer, it's a purpose built engine that runs entirely inside V8 isolates on Cloudflare Workers , and Cloudflare claims it uses 3 7x less CPU and memory than Chromium for common agentic tasks like screenshots and HTML extraction. It's available for free during beta through Browser Run , and it's compatible with tools that already speak CDP or MCP, Puppeteer, Playwright, chrome remote interface, by simply adding one parameter to the endpoint. If you're shipping agents that touch the web, research agents, scrapers, form filling bots, visual QA pipelines, this matters directly, because it resets the cost math everyone quietly assumed: that "browser automation" meant "headless Chromium in some expensive container, " full stop. Why did Cloudflare build a whole new browser instead of just using Chromium? Cloudflare's own technical post lays out the argument plainly, and it's easier to state than to build: Chromium was designed to be looked at by a human. Full graphics rendering pipeline, video decoding, WebGL, extension support, twenty years of web compatibility baggage. An AI agent needs almost none of that. It needs to load a page, run JavaScript, read the resulting DOM, and maybe grab a screenshot. Spinning up a complete Chromium process for that, in Cloudflare's own framing, is industrial overkill for a task that doesn't require it. Their answer was to build a browser that runs entirely on V8 isolates , the same lightweight isolation mechanism Workers already use to run serverless functions for thousands of tenants on shared hardware in milliseconds. The team says they built it in roughly 12 weeks , which, if that timeline holds up under scrutiny, says as much about how thin a browser can get once you strip out everything an agent doesn't touch as it does about the team that shipped it. The important nuance: this isn't "Chromium, but lighter." It's a different engine with its own behavior and its own hard limits, and Cloudflare explicitly positions it as a complement to, not a replacement for, the Chromium based browsers it already offered inside Browser Run. How does Kitesurf actually work under the hood? Three design choices explain most of what you need to know: 1. An engine on V8 isolates, not OS processes. Every Kitesurf session spins up as an isolate, the same mechanism Workers use to run untrusted third party code side by side without cross contamination. Booting an isolate is orders of magnitude cheaper and faster than booting a full Chromium process with its own memory space. 2. Stateless by design. Cloudflare documents that the public facing component, what they call the Engine , holds no persistent state beyond what's needed for the active session. That maps directly onto the intended usage pattern: short, bursty jobs, not hours long authenticated sessions. 3. Protocol level compatibility, not a full CDP reimplementation. Kitesurf speaks enough CDP (Chrome DevTools Protocol) that existing tools, Puppeteer, Playwright, chrome remote interface, MCP based agents, can point at it without rewriting their automation logic. Here's Cloudflare's own MCP configuration for wiring Kitesurf into an agent: And for a one shot Quick Action, say, a screenshot without spinning up a full automation session: Notice what Cloudflare didn't do: they didn't ship a separate product with a separate API. It's the exact same Browser Run endpoint that already existed for Chromium, with tacked onto the query string. That's a smart product call, it drops the switching cost to almost zero for anyone already on Browser Run. How does Kitesurf compare to Chromium, Browserbase, and Browserless? This is the table that actually drives the decision of which engine sits behind your agent: | | Kitesurf | Headless Chromium | Browserbase | Browserless | | | | | | | | Engine | Custom, on V8 isolates / Workers | Full Chromium engine | Managed Chromium in containers | Managed headless Chromium | | CPU on agentic tasks | 3.1x less than Chromium (Cloudflare's own screenshot benchmark) | Baseline | Comparable to Chromium | Comparable to Chromium | | Memory on HTML extraction | 7.0x less than Chromium (Cloudflare's own benchmark) | Baseline | Comparable to Chromium | Comparable to Chromium | | Real world speed (wall clock) | Slower on several of Cloudflare's own benchmark runs | Reference point | Fast (full Chromium) | Fast (full Chromium) | | Long authenticated sessions | Not the intended use case | Yes | Yes, with debugging/stealth focus | Yes | | Video / WebGL | Not supported | Yes | Yes | Yes | | Puppeteer/Playwright/MCP compatibility | Yes, via CDP with | Native | Yes | Yes, via WebSocket CDP | | Pricing | Free during beta (per account limits) | Cost of your own infra | Paid plans with a