November 13, 2026 — Cloudflare has open-sourced Kitesurf, its stateless browser engine built specifically for AI agents, releasing the code on GitHub under the Apache 2.0 license. Anyone can now read the code, run Kitesurf locally, modify it, and deploy their own instance to Cloudflare Workers. Why it matters: agents increasingly do their work through web pages, and Cloudflare just gave developers a free, self-hostable alternative to running heavy Chromium containers for them.
What happened
Cloudflare introduced Kitesurf in August as a browser designed for software agents rather than people, then followed up in September with WebMCP support, new APIs, and improved compatibility. On both occasions the company said it intended to open-source the engine. That release has now landed: the full repository — engine, Rust core, DOM shims, renderer, and the Kitesurf CLI — is public on GitHub, and Cloudflare is inviting forks and contributions.
How Kitesurf works
Kitesurf runs entirely on Cloudflare Workers. It parses HTML, applies CSS, executes page JavaScript, and renders screenshots without a browser container. It supports the Chrome DevTools Protocol (CDP), so existing clients such as Puppeteer can connect to it the way they would connect to Chrome. Cloudflare’s stated goal is a browser that loads pages and interacts with them using less CPU and memory than a full Chromium build, while scaling on demand across its global Workers network.
Under the hood, Kitesurf is assembled from open-source Rust projects compiled to WebAssembly: Blitz provides HTML parsing, the DOM, layout, and painting; Stylo handles CSS parsing and computed styles; Boa runs JavaScript inside WebAssembly as a last resort when JavaScript cannot run in Dynamic Workers; Linebender libraries handle text layout and 2D graphics; and Krilla generates PDF output. The engine itself has three main parts — the Engine manages sessions and client connections, PageScript runs the page and its JavaScript, and PageRenderer draws the result.
Running your own instance
Developers can clone the repository, install dependencies, and start a local engine that serves at 127.0.0.1:8787, then point Puppeteer or an AI agent harness at its CDP endpoint. Deploying to your own Cloudflare account is also supported, but it requires a Workers Paid plan, because Kitesurf uses Dynamic Workers to create an isolated Worker for each page. Cloudflare is candid that Kitesurf remains experimental and under heavy development, with current work focused on web-standards compatibility, reliability, and efficiency.
Why it matters
Every serious AI agent eventually needs a browser, and until now the default answer has been spinning up Chromium — heavy, stateful, and awkward to scale. Kitesurf treats the browser as disposable infrastructure: stateless, serverless, and started per task. Open-sourcing it means agent builders can inspect exactly how their agent sees the web, self-host the engine inside their own Cloudflare account instead of relying on Cloudflare’s managed Browser Run APIs, and fix the rendering bugs their agents hit. It will not replace Chromium for every job — Cloudflare itself flags ongoing compatibility work — but for high-volume agent browsing, a free engine built for the job is a real new option.
Frequently asked questions
Is Kitesurf free to use? Yes. The code is open source under the Apache 2.0 license. Deploying it to Cloudflare requires a Workers Paid plan, because it relies on Dynamic Workers.
Does Kitesurf replace Chrome for AI agents? Not entirely. It speaks the Chrome DevTools Protocol, so tools like Puppeteer can drive it, but Cloudflare describes it as experimental and still improving its compatibility with web standards.
What is Kitesurf built from? A Rust core compiled to WebAssembly, using Blitz for layout, Stylo for CSS, Boa for JavaScript, Linebender for graphics, and Krilla for PDF output — all running on Cloudflare Workers.
Sources: Cloudflare Blog, Unite.AI