Cloudflare Launches Kitesurf, a Stripped-Down Browser for AI Agents

Cloudflare has built a browser that no human will ever look at. On Thursday, the company introduced Kitesurf, a browser designed exclusively for AI agents that need to navigate web pages, read content, and take screenshots, without any of the interface machinery a person actually clicks on. TechCrunch reported that the launch puts Cloudflare, better known for its content delivery network and edge security products, into a growing field of companies building browsers aimed at AI agents rather than people.

Built for Agents, Not for Tabs

Kitesurf runs entirely on Cloudflare Workers, the company’s serverless compute platform, rather than shipping as installable software. In its changelog announcement, Cloudflare described Kitesurf as a “stateless, highly scalable browser that runs entirely on top of Workers and is designed for AI agents.” The pitch is that conventional browser engines like Chromium were built to render pixels smoothly for a person watching a screen: tabs, themes, extensions, and cross-device sync are features an AI agent has no use for. Kitesurf cuts that overhead down to what an agent actually needs: parsed HTML, executed JavaScript, and a rendered screenshot on demand.

A Rust and V8 Foundation

Instead of embedding Chromium, Cloudflare assembled Kitesurf from existing open source components. HTML and CSS parsing borrow from Blitz, a modular Rust rendering engine, and from Stylo, the CSS engine originally built for Firefox. JavaScript execution runs on V8, the engine already native to Cloudflare Workers, with Boa JS, a Rust-based ECMAScript engine, handling eval() calls. Cloudflare said its earliest proof of concept was a port of Obscura, an open source headless Rust engine built for AI automation, onto the Workers platform, and credited that project as the direct inspiration for Kitesurf.

Lighter on Resources, Slower on the Clock

Cloudflare published head-to-head benchmarks against Chromium running in a warm pool, and the trade-off is explicit. For a screenshot task, Kitesurf used 380 milliseconds of CPU time versus 1,173 milliseconds for Chromium, a 3.1 times reduction, while memory use dropped from 271.0 MiB to 57.8 MiB, a 4.7 times reduction. HTML extraction showed an even wider memory gap: 39.4 MiB for Kitesurf against 273.7 MiB for Chromium, a 7.0 times reduction, with CPU time cut 3.8 times. That efficiency comes at the cost of wall-clock speed: Kitesurf took 1.7 to 1.8 times longer than Chromium to finish the same two tasks. In its changelog, Cloudflare summarized the trade it is asking developers to make more simply: Kitesurf uses three to seven times less CPU and memory than Chromium for common agentic tasks, which the company says means more concurrent sessions and better scaling for bursty, AI-driven workloads.

What It Cannot Do Yet

Kitesurf is not a Chromium replacement for every job. Cloudflare said it does not yet support video playback or WebGL, cannot complete bot-detection challenges that rely on TLS fingerprinting, and is not built for a ten-minute authenticated session that requires persistent state, the kind a human user might keep open all day. Cloudflare also said the browser already passes more than 215,000 Web Platform Tests, with hundreds more added each week, and correctly renders sites including Wikipedia, Hacker News, and the React, Vue, Angular, and Preact versions of the TodoMVC benchmark app.

A Drop-In Option for Existing Automation

Cloudflare designed Kitesurf to slot into automation code teams have already written against Browser Run, its platform for programmatically controlling headless browsers. Switching an existing Browser Run request from Chromium to Kitesurf requires adding a single query parameter, browser=kitesurf, to the API call, and Cloudflare said existing clients need no other changes. The browser is free to use while in beta, and Cloudflare said it plans to open source Kitesurf once the project is ready, though it gave no firm timeline.

Kitesurf arrives alongside a broader industry push toward infrastructure built specifically for AI agents: sandboxed runtimes, isolated execution environments, and now a browser designed around what a script needs rather than what a person sees. For teams already running web-scraping or browser-automation agents on Cloudflare’s network, the pitch is straightforward: the same CDP-based calls, at a fraction of the compute cost, as long as the missing features are not the ones a given task depends on.