On November 13, 2026, Cloudflare announced on its official blog that Kitesurf, its stateless browser for AI agents, is now open source, with the code on GitHub under the Apache 2.0 license. After its debut in August and the addition of WebMCP support in September, Cloudflare has now kept its promise to open-source it. For teams building agents, the change is direct: no more pairing every task with a full Chromium instance — you can run a browser engine in your own account instead.
A browser with no browser container
Kitesurf runs entirely on Cloudflare Workers: it parses HTML, applies CSS, executes page JavaScript, and renders screenshots, all without a browser container. It supports the Chrome DevTools Protocol (CDP), so tools like Puppeteer can connect directly. The repository has three parts: the Engine manages browser sessions and client connections, PageScript runs the page and its JavaScript, and PageRenderer draws the result. Underneath is a set of open-source Rust components: Blitz handles parsing and layout, Stylo handles CSS, Boa runs JavaScript inside WebAssembly, Linebender does text layout and 2D graphics, and Krilla generates PDF output. Running it locally is simple too: clone the repository, install the dependencies, run pnpm run dev, and the dev server starts at 127.0.0.1:8787 — open it in a browser and try it out.
Where it saves money, and where it falls short
Cloudflare's claim is that Kitesurf uses less CPU and memory than a full browser like Chromium and scales on demand across the Workers global network — but the official blog gives no measured data, so for now that is the company's own claim. Deploying it to your own account requires a Workers Paid plan, because it uses Dynamic Workers to create an isolated worker per page. One more thing to be clear about: Kitesurf is still experimental, and Cloudflare says its focus remains on improving compatibility, reliability, and efficiency, with Web Platform Tests pass rates as its own progress yardstick. Treating it as a drop-in replacement for full Chrome is premature; the more realistic path is to get it running locally first, then decide whether to wire it into your own agent pipeline. The idea itself is not new: open-source Browser Use already builds browser-operating agents, and LangChain's managed agents are growing browsers of their own — what sets Kitesurf apart is that the browser itself has been broken down into a lightweight engine that runs on Workers. The managed Browser Run service continues to be available, sparing you the trouble of self-hosting.
