On Friday, 13 November 2026, Cloudflare kept a promise. In a post on its company blog, the firm announced that Kitesurf, the browser engine it built for AI agents rather than for people, is now open source on GitHub under the Apache 2.0 licence. Anyone may read the code, run it on their own machine, change it, and deploy their own copy to Cloudflare Workers.
The company had made the promise every time Kitesurf appeared in public. The engine was introduced on 6 August as a stateless browser running entirely on Workers, a launch TechCrunch covered at the time. In September came an update with WebMCP support, new APIs and better compatibility. Each time, Cloudflare said developers would one day be able to run their own engine on their own accounts. That day has now come.
A browser with no window
For as long as most people can remember, a browser has been something made for human eyes, with tabs and themes and a window to look through. At the launch, Cloudflare argued that an agent cares about none of that. What an agent needs, the company said, is a way to manage context windows, token costs, performance and scale, along with defences against a different set of threats, prompt injection among them.

So Kitesurf does the work of a browser and leaves out the face. It parses HTML, applies CSS, executes a page’s JavaScript and renders screenshots, all without a browser container. It speaks the Chrome DevTools Protocol, so clients such as Puppeteer can connect to it as if it were Chrome. Cloudflare’s stated aim is a light engine that loads sites and interacts with pages on less CPU and memory than Chromium, scaling on demand across the company’s global Workers network. In August its developer account put a number on that, claiming Kitesurf uses 3 to 7 times less CPU and memory. That is the company’s own figure.
The reader of the page is no longer a person. It is a program, and the program wants to be cheap.
Borrowed parts
Like most modern machines, the engine is assembled from other people’s work. It sits on Cloudflare’s Developer Platform and on a set of open-source Rust packages compiled to WebAssembly. Blitz handles HTML parsing, the DOM, layout and painting. Stylo does CSS parsing, cascading and computed styles. Boa runs JavaScript inside WebAssembly, though Cloudflare says it falls back on Boa only as a last resort, when the JavaScript cannot run in Dynamic Workers. Linebender libraries supply text layout and 2D graphics, and Krilla produces PDFs.
“These projects made Kitesurf possible,” the company writes, a rare sentence of gratitude in a corporate announcement. Each keeps its own licence. According to the repository’s README, Stylo is under MPL-2.0 while the others carry MIT, Apache-2.0 or Unlicense terms, and a NOTICE file lists them all.

Kitesurf itself comes in three parts. The Engine manages browser sessions and client connections, PageScript runs the page and its JavaScript, and PageRenderer draws the result. The Rust core, DOM shims, renderer and a terminal client called Kitesurf CLI each live in their own folder under the repository’s packages directory.
The price of the door
Running it locally takes a clone of the repository, a dependency install and the command pnpm run dev. The README lists the requirements as Bazelisk, Node.js 22 or newer and pnpm 9.15.4. The first build compiles the Rust core and takes a while; later builds reuse the cache. Wrangler then opens a development server at 127.0.0.1:8787, where a page can be tried in Chrome DevTools or driven from a Puppeteer script. Or, the company suggests, a developer can point an AI harness at the local CDP port and let it take over. “Agents love CDP,” Cloudflare adds.
Moving the engine onto Cloudflare’s own servers, in place of the managed Browser Run APIs, takes one more command, pnpm run deploy, and one more condition: a Workers Paid plan. Kitesurf needs it because it uses Dynamic Workers to give each page an isolated Worker. One could put it this way: the code is now free, but the ground it was designed to stand on is still rented.

The README is blunter than the blog post. It warns that the engine has no built-in authentication and tells users not to deploy it without Cloudflare Access or some other authentication layer in front. It calls the project “a CDP endpoint, not a full Chrome implementation,” and notes that some DevTools features do not yet work.
Petitioners at the gate
Cloudflare welcomes forks and contributions, but it sets terms. Kitesurf is under heavy development, the company says, and its priorities are compatibility, which it tracks through Web Platform Tests, along with reliability and efficiency. Anyone who wants to submit code must first open an issue with a minimal reproduction or a proposed approach, then be vouched for by a maintainer before opening a pull request. Small fixes with tests and clear evidence are preferred to large rewrites or unrelated cleanup. Help does not have to be code: a small page that reproduces a rendering bug, a broken automation workflow or a documentation correction all count.
Every institution that opens its doors also posts a guard. Here the guard is polite and speaks in contribution guidelines, but the rule is the old one: you may enter once someone inside has vouched for you.
The queue has already formed. By Saturday the repository showed 904 stars, 37 forks, two open issues and 34 open pull requests. The company, which has lately been counting how its network feeds pages to ChatGPT’s index, says further news will come through its blog, its changelog and a Discord server where the team takes questions about a browser that no human was ever meant to look through.

