Cloudflare Launches Kitesurf, a Chromium-Free Browser Built for AI Agents

Cloudflare has built a browser from scratch that doesn’t run Chromium at all. Called Kitesurf, it’s a stateless browser engine written mostly in Rust and compiled to WebAssembly, running entirely inside Cloudflare Workers — the company’s serverless compute platform. Cloudflare announced it on August 6, 2026, as a free public beta inside Browser Run, its existing browser-automation product.

The pitch is straightforward: AI agents that browse the web today typically rely on full Chromium instances, which were designed for humans clicking through tabs, watching video, and expecting pixel-perfect rendering. None of that matters to an agent extracting text or taking a screenshot, but the computing cost does. Cloudflare says Kitesurf uses 3 to 7 times less CPU and memory than Chromium for common agentic tasks, while conceding it’s currently slower to actually load a page. That trade-off — and how real it is — is the story worth understanding.

What Is Kitesurf?

Kitesurf is a stateless browser that runs entirely on top of Cloudflare Workers, rather than shipping a browser engine like Chromium into the cloud. It launched in public beta on August 6, 2026, free to use within Browser Run’s per-account limits. It is not a general-availability product, and Cloudflare has not set a GA date.

Instead of loading a full desktop-class browser, Kitesurf focuses on what Cloudflare says agents actually need: managing token counts and context windows, keeping compute costs down, and scaling to handle bursts of automated traffic. Things that matter to a person using a browser — tabs, themes, extensions, smooth scrolling — are simply not part of the design.

Why Cloudflare Built a Browser for Agents, Not Humans

Cloudflare’s argument, laid out in its own announcement, is that browser engines like Chromium were built for humans and carry overhead that AI agents don’t need. Running a full Chromium instance for every agent session is expensive enough, the company says, that it restricts sophisticated web-browsing capability to only the costliest AI models, while locking cheaper or higher-volume agentic applications out of large parts of the web.

The company also frames the security question differently for agents than for humans. A browser used by an AI agent faces new risks — prompt injection through malicious page content, and questions about what tools an agent should be allowed to invoke — that a browser built for a human user doesn’t need to think about in the same way. Kitesurf’s isolation model, described below, is Cloudflare’s response to that.

Origins: From Obscura to Kitesurf

Cloudflare says the idea traces back to Obscura, an open-source headless browser engine written in Rust for AI automation, built explicitly with no Chrome and no Node.js dependencies. Cloudflare’s team used an AI coding agent to port Obscura to Workers as a first proof of concept. According to the company, the initial attempt didn’t work well — but once the team gave the agent a clear plan and a well-defined measure of success, it did.

From that starting point, Cloudflare says it built Kitesurf in about 12 weeks, with the first commit landing around May 2026. The team leaned on the Web Platform Tests suite — a large, standardized set of browser-conformance tests — to give its AI coding agents concrete, checkable goals, while human engineers focused on architecture and review.

How Kitesurf Works

Kitesurf splits browser work across three components. The Engine is the only public-facing piece: it handles the Chrome DevTools Protocol (CDP) over WebSocket and REST, and it’s the one component that stores session state. Everything else is designed to be stateless.

PageScript does the heavy lifting of interpreting a page. It parses HTML and CSS using parts of Blitz, a modular rendering engine, and Stylo, the CSS parser originally built for Firefox — both written in Rust. It then runs the page’s JavaScript and WebAssembly inside the same isolated environment. One notable wrinkle: Cloudflare Workers doesn’t support native eval() for security reasons, so Kitesurf falls back to Boa JS, a JavaScript engine written in Rust, to handle the pages that still use it. Cloudflare describes this as running “a runtime on top of a runtime” — not optimal, but functional — and says it plans to drop Boa once Workers gains native eval support.

PageRenderer turns the parsed page into actual pixels, producing screenshots or PDFs for compatible sites.

Network access is tightly controlled. A separate SandboxOutbound worker handles every outbound request — images, scripts, fonts, stylesheets, and the page’s own fetch calls — enforcing cross-origin rules, filtering responses, and keeping each page’s cookies in a separate jar. Anything that violates policy gets rejected outright. Cloudflare built this around the assumption that every page a Kitesurf instance loads could contain hostile code, and that each session should start clean rather than share state with anything else.

That statelessness is also central to the performance story: a component with nothing to reconstruct can be killed the moment something goes wrong and relaunched instantly, and can be spun up in parallel by the thousands to absorb bursty automation traffic.

Performance: 3–7x Less CPU and Memory, But Slower

Cloudflare published its own benchmark comparing Kitesurf to Chromium, based on the median of five runs across a 14-URL test corpus using Browser Run’s Quick Actions.

Source: Cloudflare Blog, August 2026

The pattern is consistent: Kitesurf uses dramatically less CPU and memory, but currently takes longer, in wall-clock terms, to actually complete a request. Cloudflare attributes that gap to Chromium’s just-in-time compiler, which has effectively already “seen” common patterns and can outrun a cold software renderer — plus overhead in Kitesurf’s image rasterization and encoding, which the company says it’s still optimizing.

It’s worth being clear about what this benchmark is and isn’t. It’s Cloudflare’s own test, run on its own infrastructure, using its own corpus of 14 URLs. No independently run, third-party benchmark comparing Kitesurf to Chromium has been published. The efficiency gains are real enough that Cloudflare is willing to publish the numbers alongside the performance shortfall, which lends some credibility to the disclosure — but readers evaluating Kitesurf for their own workloads should treat these as a starting point, not a guarantee.

Separately, Cloudflare says Kitesurf passes more than 215,000 Web Platform Tests, with new ones added weekly, and that coverage is already solid for the browser features agents rely on most — CSS, the DOM, HTML parsing, selection, SVG, and XHR.

What Kitesurf Can and Can’t Do Yet

Cloudflare says Kitesurf correctly renders TodoMVC across five different frontend frameworks, along with Wikipedia, Hacker News, the Cloudflare Blog, and much of Cloudflare’s own dashboard. As something of an internal stress test, the team also got it running the browser-based version of Doom.

But there’s a real list of things it can’t do yet. Kitesurf doesn’t support video playback or WebGL rendering. It can’t negotiate bot-challenge handshakes that depend on real TLS fingerprints. And it isn’t built for long-running, authenticated sessions that need to hold state over time — the kind of workflow where an agent stays logged into an account for an extended task. For any of those cases, Cloudflare’s own guidance is to fall back to Browser Run’s standard Chromium-powered option.

Source: Cloudflare Browser Run docs

The company also describes its CDP support as a subset of the full protocol — enough to cover most agent and automation needs, including DOM and network inspection, but not complete. Cloudflare says it’s continuing to expand that coverage.

Getting Started: Compatibility With Existing Tools

One of Kitesurf’s more practical selling points is that it doesn’t require developers to rewrite their automation code. Because it speaks the Chrome DevTools Protocol, it works with tools already built around CDP: Puppeteer, Playwright, chrome-remote-interface, and MCP-compatible AI clients. Switching a request from Chromium to Kitesurf inside Browser Run is a matter of adding a single browser=kitesurf parameter to an existing CDP or Quick Actions endpoint. Cloudflare also offers a public playground where anyone can point Kitesurf at a URL and inspect what happens, including a DevTools memory panel that reports the WebAssembly footprint of each page.

What Kitesurf doesn’t have, as of this writing, is any announced formal integration with major agent frameworks. Cloudflare hasn’t announced a partnership or built-in support with LangChain, CrewAI, OpenAI’s agent tooling, or Anthropic’s computer-use feature. Any of those frameworks could reach Kitesurf indirectly, through the same Puppeteer, Playwright, or CDP libraries they already use — but that’s compatibility by virtue of a shared protocol, not a named integration.

Competitive and Strategic Context

Kitesurf doesn’t compete with human-facing browsers like Chrome, Firefox, or Safari. Its real point of comparison is the Chromium-based automation stack that currently dominates AI agent browsing — Puppeteer and Playwright running headless Chromium instances, and commercial headless-browser services such as Browserless.io and Bright Data. Cloudflare isn’t claiming to have built the fastest or most capable browser in that space; its argument is narrower and more specific: lower CPU and memory cost for a defined set of agent tasks.

It’s also worth noting that Cloudflare isn’t abandoning Chromium. Browser Run’s default option remains Chromium-powered, and Cloudflare is explicit that Kitesurf is a second option for workloads that fit its current constraints — not a replacement.

Some industry observers have framed Kitesurf as a strategic extension of a business Cloudflare already has some position in. The company already sits at the network layer for a large share of internet traffic through its content-delivery and bot-management services. A browser engine running on its own infrastructure moves that presence up a layer, from routing and filtering traffic to actually rendering and interacting with it on an agent’s behalf. Cloudflare hasn’t framed it in exactly those terms, but the shift is a reasonable reading of what the product does.

Pricing and Availability

Kitesurf itself is free to use during its beta period, subject to Cloudflare’s standard per-account usage limits. It doesn’t yet have its own separate pricing structure — it runs as an option inside Browser Run, which does have documented pricing. On the Workers Paid plan ($5 per month base), Browser Run charges $0.09 per browser-hour and $2.00 per concurrent browser beyond the plan’s included allowances.

What isn’t clear is how — or whether — Cloudflare will price Kitesurf differently from standard Chromium-based Browser Run sessions once it moves out of beta. That decision hasn’t been publicly disclosed.

What’s Still Unknown

A handful of open questions remain unanswered by Cloudflare’s own materials or independent reporting. There’s no confirmed date for open-sourcing Kitesurf, something Cloudflare has said it intends to do so that customers can eventually run their own deployments. There’s no independent benchmark data to check Cloudflare’s performance claims against. Post-beta pricing hasn’t been announced. No AI agent framework has confirmed formal support. And there’s no public data yet on how many developers or organizations are actually using Kitesurf, or in what volume.

Conclusion

Kitesurf is a genuine technical undertaking — a browser engine built largely from scratch in a serverless environment, verified against hundreds of thousands of standards tests, and backed by benchmark numbers Cloudflare is willing to publish even where they’re unflattering. The efficiency case is real: for tasks like screenshots and HTML extraction, using several times less CPU and memory than Chromium translates directly into lower infrastructure costs at scale.

What the evidence doesn’t yet show is how Kitesurf performs outside Cloudflare’s own test conditions, what it will cost once the beta ends, or whether any of the major AI agent frameworks will build around it. For now, it’s a promising, actively developed option for a specific slice of agent workloads — simple, stateless, high-volume tasks — rather than a wholesale replacement for Chromium-based automation. Developers already using Puppeteer, Playwright, or CDP tooling can test it today, for free, without changing their code. Whether it becomes a default rather than an option will depend on how quickly Cloudflare closes the gaps it has already acknowledged: wall-clock speed, feature coverage, and, eventually, a clear price.

FAQ

What is Cloudflare Kitesurf? Kitesurf is a stateless browser engine Cloudflare built to run entirely inside Cloudflare Workers, designed specifically for AI agents rather than human users. It launched in public beta on August 6, 2026, as part of Cloudflare’s Browser Run product.

Is Kitesurf free to use? Yes, during its current beta period. It’s available at no cost within Browser Run’s standard per-account usage limits. Cloudflare hasn’t disclosed what pricing will look like after the beta ends.

How is Kitesurf different from Chromium-based headless browsers? Instead of running a full Chromium engine, Kitesurf is built largely in Rust and compiled to WebAssembly, using components like the Blitz rendering engine and Firefox’s Stylo CSS parser. Cloudflare’s own benchmarks show it uses 3 to 7 times less CPU and memory than Chromium for tasks like screenshots and HTML extraction, though it’s currently 1.7 to 1.8 times slower to complete those same tasks.

Does Kitesurf work with Puppeteer or Playwright? Yes. Because Kitesurf supports the Chrome DevTools Protocol, existing Puppeteer, Playwright, and CDP-based automation code works with it. Developers switch to it by adding a browser=kitesurf parameter to existing Browser Run endpoints, without rewriting their scripts.

What can’t Kitesurf do yet? It doesn’t support video playback or WebGL rendering, can’t handle bot-challenge systems that check real TLS fingerprints, and isn’t designed for long-running sessions that need to stay authenticated over time. Cloudflare recommends its standard Chromium-based Browser Run option for those cases.

Is Kitesurf open source? Not yet. Cloudflare has said it plans to open-source Kitesurf so customers can eventually run their own deployments, but hasn’t given a timeline.

How much faster or cheaper is Kitesurf than Chromium, really? Based on Cloudflare’s own published benchmarks, it’s substantially cheaper to run in terms of CPU and memory — 3 to 7 times less, depending on the task — but it currently takes longer in wall-clock time to complete a request. These figures come from Cloudflare’s own testing; no independent benchmark has been published to confirm them.

Sources

• Introducing Kitesurf: The agent-first browser that runs in V8 isolates on Cloudflare Workers — Cloudflare Blog
• Kitesurf · Cloudflare Browser Run docs — Cloudflare Developer Docs
• Introducing Kitesurf, an agent-first browser on Browser Run — Cloudflare Changelog
• Pricing · Cloudflare Browser Run docs — Cloudflare Developer Docs
• Kitesurf Playground — Cloudflare