Cloudflare has entered the browser business, although Kitesurf isn’t really trying to replace Chrome on anyone’s laptop.
The company has launched Kitesurf, a cloud-hosted browser engine created specifically for AI agents — software that needs to open websites, inspect pages, collect information, take screenshots, fill out forms, and carry out tasks without a person manually clicking through every step.
That distinction matters. Traditional browsers have spent decades optimizing the web for people. Kitesurf is being built around machines.
And machines want something very different.
Kitesurf Drops the Browser Features AI Agents Don’t Need
A normal browser carries plenty of baggage because humans expect tabs, extensions, themes, synchronization, polished graphics, video playback and dozens of other conveniences.
An AI agent doesn’t care whether scrolling looks buttery smooth.
Cloudflare argues that an agent-focused browser should instead worry about memory consumption, processing costs, context windows, scalability and the amount of useful information that can be extracted from a page.
There is also a security problem that regular browsers weren’t originally designed around. AI agents can encounter hostile instructions embedded inside websites, including prompt injection attempts intended to manipulate an agent into doing something its user never requested. Cloudflare says tool safety and these newer attack models were part of the thinking behind Kitesurf.
Cloudflare Built Kitesurf in About 12 Weeks
This wasn’t apparently a years-long browser project quietly sitting inside Cloudflare.
The company says the decision to build its own browser came roughly 12 weeks before the August 7 announcement. Kitesurf now runs entirely on Cloudflare Workers and is available through the company’s Browser Run service while the product remains in beta.
Its origins are slightly unusual, too.
Cloudflare credits Obscura, an open-source Rust headless browser engine designed for AI automation, as an early inspiration. An experiment to port that approach to Cloudflare Workers eventually turned into the proof of concept that pushed the team toward building a much more complete browser.
Kitesurf also borrows established pieces rather than attempting to reinvent every layer of the web stack. Its technology includes the Blitz rendering engine, Firefox’s Stylo CSS parser and the Boa JavaScript engine.
The result isn’t supposed to be Chromium with a new logo. That’s basically the point.
Kitesurf Uses Far Less CPU and Memory Than Chromium in Cloudflare’s Tests
The more interesting argument for Kitesurf comes down to infrastructure costs.
Running one browser isn’t difficult. Running huge numbers of browser sessions for autonomous AI agents is another story entirely. Every additional CPU cycle and chunk of memory starts to matter when agents are constantly opening pages, extracting HTML and taking screenshots.
Cloudflare’s own testing found substantial differences.
For screenshot workloads, the company reported Kitesurf using about 380 milliseconds of CPU time compared with 1,173 milliseconds for Chromium. Memory consumption was 57.8 MiB versus 271 MiB.
HTML extraction showed a similar pattern. Kitesurf used 229 milliseconds of CPU time and 39.4 MiB of memory, while Chromium used 877 milliseconds and 273.7 MiB respectively.
That doesn’t mean Kitesurf wins every benchmark.
Chromium was actually faster in overall wall-clock time during Cloudflare’s tests. Kitesurf’s screenshot workload took around 1.8 times longer, while HTML extraction took roughly 1.7 times longer. Cloudflare’s bet is that the steep reduction in compute and memory matters more for large-scale agent workloads than winning every raw speed test.
That’s an interesting trade.
For a human waiting for a webpage, milliseconds are noticeable. For a fleet of autonomous agents operating simultaneously, infrastructure efficiency can become the bigger bill.
Kitesurf Has Already Passed More Than 215,000 Web Platform Tests
Building a lightweight browser isn’t especially useful if half the internet breaks when it opens a page.
Cloudflare says Kitesurf has already passed more than 215,000 Web Platform Tests, with hundreds of additional tests being passed each week.
Coverage already includes areas particularly important to automated agents, such as HTML, CSS, DOM handling, SVG, XHR and text selection. Cloudflare says the engine can correctly render sites and applications including Wikipedia, Hacker News, TodoMVC, its own blog and significant portions of the Cloudflare dashboard.
Still, nobody should mistake this beta for a complete Chrome replacement.
Not yet.
There Are Things Kitesurf Still Can’t Do
Kitesurf works best when an AI system needs a temporary browser session to inspect or process a page and then move on.
More demanding browser workloads remain better suited to Chromium.
Cloudflare says Kitesurf isn’t currently the right choice for video playback, WebGL rendering, some bot-challenge handshakes that depend on real TLS fingerprints, or long authenticated browsing sessions requiring persistent state.
Those limitations reveal what Kitesurf really is.
It’s less a browser you live inside and more a disposable browser that an AI agent can summon for a task, use briefly and discard.
Cloudflare describes the architecture as ephemeral, isolated and stateless. That could fit particularly well with agents running thousands of short web interactions rather than maintaining a traditional browsing session for hours.
Existing AI Agent Tools Can Already Connect to Kitesurf
Cloudflare has also avoided forcing developers into an entirely new automation ecosystem.
Kitesurf is available through Browser Run’s Chrome DevTools Protocol endpoint, meaning existing tools that communicate through CDP can work with it. Cloudflare specifically lists Puppeteer, Playwright, chrome-remote-interface and AI agents using MCP and CDP among the compatible options.
Developers can select Kitesurf by specifying it as the browser when connecting to supported Browser Run endpoints.
There is also a public playground where developers can enter a URL and see how Kitesurf handles the page, including access to Chrome DevTools-style inspection features.
Kitesurf is currently free while in beta, subject to Cloudflare’s account limits.
Browsers Are Becoming Infrastructure for AI Agents
The bigger story isn’t really that another technology company built another browser.
It’s that browsers are quietly becoming part of the infrastructure layer for autonomous AI.
Today’s chatbots mostly wait for information to arrive. Agents are expected to go out and get it. That means visiting websites, reading interfaces, interacting with controls, checking results and sometimes asking a human to intervene when something doesn’t work.
Cloudflare has already been pushing Browser Run in this direction, including browser sessions that agents can control programmatically and workflows where a human can temporarily take over before returning control to the agent.
Kitesurf takes that idea one level deeper by asking whether AI agents should even be using browsers designed for humans in the first place.
Maybe not.
If autonomous agents eventually generate millions or billions of browser sessions, shaving memory and compute from each one stops looking like a small optimization. It starts looking like infrastructure.
Kitesurf is still a beta, and its compatibility gaps mean Chromium isn’t disappearing from agent workflows anytime soon.
But Cloudflare is making an early bet on something that may become obvious later: when software starts browsing the internet on its own, the browser itself probably needs to change.
Sources
- TechCrunch — Cloudflare launches Kitesurf, a browser built for AI agents
- Cloudflare — Introducing Kitesurf: The agent-first browser that runs in V8 isolates on Cloudflare Workers
- Cloudflare — Browser Run