Cloudflare Launches Kitesurf, a Browser Built for AI Agents That Runs Entirely on Its Workers Platform

Overview

Cloudflare has launched Kitesurf, a cloud-hosted web browser built specifically for AI agents rather than human users, according to TechCrunch. Instead of pitching a Chrome alternative to consumers, the internet infrastructure provider designed Kitesurf so that AI developers can build software that navigates websites, fills out forms, and completes other browser-based tasks without building their own browser software, as TechCrunch reported.

What We Know

Unlike traditional browsers built for humans, a browser built for AI agents doesn’t need to render themes, tabs, or extensions — instead it has to manage context windows, performance, token costs, and scalability, and it faces a different threat model that includes risks like prompt injection attacks, Cloudflare explained in its announcement, according to TechCrunch.

Kitesurf runs entirely inside Cloudflare Workers, the company’s serverless compute platform, using V8 isolates rather than Chromium underneath. The browser was assembled from a modular rendering engine from Blitz, Firefox’s CSS parser Stylo, and Boa JS, a Rust-based ECMAScript engine, with everything else running inside Workers, TechCrunch reported. Cloudflare said it began building Kitesurf about 12 weeks before the announcement, and that the project’s first proof of concept was a port of Obscura — an open-source Rust headless browser engine that inspired the effort — to Workers, according to TechCrunch.

On performance, Cloudflare published benchmark figures from a test corpus comparing Kitesurf to a warm Chromium pool: Kitesurf used 380 milliseconds of CPU time per screenshot versus 1,173 milliseconds for Chromium, a 3.1-times reduction, and 229 milliseconds versus 877 milliseconds for HTML extraction, a 3.8-times reduction, according to Cloudflare’s announcement and independently corroborated by MarkTechPost. Memory use dropped from 271.0 MiB to 57.8 MiB for screenshots, a 4.7-times reduction, and from 273.7 MiB to 39.4 MiB for HTML extraction, a 7.0-times reduction, per the same figures reported by both Cloudflare and MarkTechPost. The tradeoff is speed: Kitesurf took 1.7 to 1.8 times longer than Chromium to complete the same tasks, according to TechCrunch.

“Kitesurf is significantly more efficient in CPU and memory consumption than Chromium for common agentic tasks like screenshots and HTML extraction,” Cloudflare said, according to TechCrunch.

Cloudflare said Kitesurf already passes more than 215,000 web platform tests and is adding hundreds more each week, per TechCrunch and independently confirmed by MarkTechPost. The company said the browser correctly renders pages including TodoMVC, Wikipedia, Hacker News, the Cloudflare Blog, and much of the Cloudflare dashboard, according to TechCrunch.

Kitesurf is available for free during its beta period through Browser Run, Cloudflare’s product for programmatically controlling headless browser instances on its network, TechCrunch reported. Developers can reach it through the Browser Run CDP endpoint or Quick Actions API by adding a browser=kitesurf parameter, or try it through a public playground at kitesurf.cloudflare.app with integrated Chrome DevTools, according to Cloudflare. The browser is compatible with existing automation libraries including Puppeteer, Playwright, chrome-remote-interface, and clients using the Model Context Protocol, per Cloudflare’s announcement.

What We Don’t Know

Cloudflare has not disclosed a timeline for taking Kitesurf out of beta or for its planned open-source release, according to Cloudflare’s own announcement. The company also acknowledges the browser cannot yet handle video playback, WebGL rendering, bot-challenge TLS fingerprinting, or persistent multi-minute authenticated sessions, and recommends its Chromium-powered Browser Run product for those workloads in the meantime, per Cloudflare.

Analysis

Kitesurf’s core bet is that AI agents don’t need a browser built for humans. By stripping out rendering fidelity, tabs, and extensions in favor of a stateless, isolate-based architecture, Cloudflare is targeting the same operational costs — CPU cycles and memory — that determine cloud bills at scale. The tradeoff Cloudflare has been explicit about, a slower wall-clock time in exchange for lower resource consumption, mirrors a familiar cost-versus-latency calculation that cloud infrastructure providers routinely ask customers to make, and it positions Kitesurf as an infrastructure play built to run natively on Cloudflare’s own serverless platform rather than as a general-purpose browser product competing directly with Chrome.