Cloudflare open-sources Kitesurf, its browser engine for AI agents, under Apache 2.0
Cloudflare published the code of Kitesurf, its experimental browser engine for AI agents, on GitHub under Apache 2.0. Self-hosting needs a Workers Paid plan.
By Emre A.Published
Tech AI LatestCloudflare has released the source code of Kitesurf, the experimental browser engine for AI agents it launched in beta in August 2026, on GitHub under the Apache 2.0 license. Kitesurf parses HTML, applies CSS, runs page JavaScript and renders screenshots without Chrome, and agents control it through the Chrome DevTools Protocol. Developers can run it locally or deploy it to their own Cloudflare account, which requires a Workers Paid plan and an authentication layer in front.
Key facts
- Announced: 12 November 2026 in Cloudflare's developer changelog and a blog post, "Kitesurf is now open source"
- License: Apache 2.0; code at github.com/cloudflare/kitesurf
- Control: Chrome DevTools Protocol endpoint, so Puppeteer and other CDP clients can connect
- Requirement: Cloudflare Dynamic Workers, part of the Workers Paid plan, to run on Cloudflare
- Security: the engine has no authentication of its own; Cloudflare says to put Cloudflare Access or another login layer in front
- Status: experimental; some Chrome DevTools features do not work yet
What Cloudflare released
Cloudflare has published the source code of Kitesurf, its browser engine built for AI agents rather than people. A developer changelog entry dated 12 November 2026 and a post on the Cloudflare blog announced the release, and the code is in a public GitHub repository under the Apache 2.0 license. Bundled fonts, data and dependencies keep their own licenses.
The repository README describes Kitesurf as "an experimental browser engine that runs on Cloudflare Workers". It parses HTML, applies CSS, runs page JavaScript and renders screenshots without Chrome or a browser container. It speaks the Chrome DevTools Protocol (CDP), so an agent or a script written for Puppeteer connects to it the way it would connect to Chrome. The README warns that Kitesurf provides a CDP endpoint, not a full Chrome implementation, and that some DevTools features do not work yet.
The engine is assembled from open-source Rust projects: Blitz for HTML parsing, the DOM, layout and painting; Servo's Stylo for CSS; Boa for JavaScript inside WebAssembly; the Linebender libraries for text and 2D graphics; and Krilla for PDF output. Cloudflare's blog post says Boa is the fallback, used only when page JavaScript cannot run in Dynamic Workers. The repository is split into packages for the engine and CDP server, the page runtime, the renderer, the Rust core and a terminal client.
Running it yourself, and the security catch
Developers can build Kitesurf and run it on their own machine with wrangler dev; the README lists Bazel, Node.js 22 or newer and pnpm as requirements. Running it on Cloudflare is a different matter. Kitesurf starts a separate isolated worker for each page and renderer through Cloudflare Dynamic Workers, and Dynamic Workers are part of the Workers Paid plan. So the code is free to read, change and run locally, but a cloud deployment is billed by Cloudflare.
The README carries an unusually blunt warning. The engine has no authentication of its own, and the workers.dev address it deploys to is public by default with a predictable name, kitesurf.<your-subdomain>.workers.dev. Anyone who finds the URL could browse the web through the engine, connect Puppeteer to it, send outbound requests that come from the owner's Cloudflare account and spend CPU time the owner pays for. Cloudflare tells operators to protect the Worker with Cloudflare Access, its zero trust login service, immediately after deploying, or to turn on Access for all Workers in the account first so there is no gap. Scripts then connect with an Access service token.
Why an agent browser matters
AI agents that read websites, fill in forms or take screenshots usually drive a headless copy of Chromium, a full desktop browser engine that is heavy to run at scale. Cloudflare introduced Kitesurf in August 2026 as a lighter alternative and offered it as a free beta engine inside its hosted Browser Run service. At launch Cloudflare said its tests showed Kitesurf using several times less CPU and up to seven times less memory than Chromium on common agent tasks, at the cost of slower page completion; those figures are Cloudflare's own and have not been independently measured. At the time it said the code would be open-sourced later.
The release gives teams building agents a browser they can inspect and modify, which matters for security reviews of tools that fetch untrusted pages. It also ties the most practical way to run it at scale to Cloudflare's own platform. Other agent platforms have gone the hosted route: OpenAI offers a hosted browser for computer use in its Agents API, and GitHub has added computer use for desktop apps to Copilot. More agent coverage is in the AI agents section.
Open questions remain. The announcement does not give a version number or a roadmap date for features such as fuller DevTools support, and the repository describes the project as under active development. How well Kitesurf handles complex, script-heavy sites compared with Chromium is something early users will now be able to test for themselves.
What changed
| Before | Kitesurf was available only as a hosted beta engine inside Cloudflare Browser Run; the code was not public. |
|---|---|
| After | The full engine is on GitHub under Apache 2.0 and can be run locally or deployed to a customer's own Cloudflare account. |
| Who it affects | Developers building AI agents that browse the web, and security teams reviewing agent tooling |
Questions people ask
- Is Cloudflare Kitesurf free?
- The code is free under the Apache 2.0 license and runs locally with
wrangler dev. Deploying it on Cloudflare needs Dynamic Workers, which are part of the paid Workers plan, according to the README. - Does Kitesurf work with Puppeteer?
- Yes. Kitesurf exposes a Chrome DevTools Protocol endpoint, and Puppeteer connects to it with
puppeteer.connect. Cloudflare notes that it is not a full Chrome implementation, so some DevTools features are missing. - Is it safe to deploy Kitesurf?
- Only behind authentication. The engine has no login of its own and its workers.dev address is public by default, so Cloudflare says to protect it with Cloudflare Access or another authentication layer.
Sources
- Kitesurf is now open source (Cloudflare, 12 Nov 2026)
- cloudflare/kitesurf (README and license) (GitHub, 12 Nov 2026)
- Kitesurf is now open source (changelog) (Cloudflare, 12 Nov 2026)
- Cloudflare launches Kitesurf, a browser built for AI agents (TechCrunch, 7 Aug 2026)
Reference pages
- Cloudflare company
Spotted an error? See the corrections policy and tell the editor. Facts in this story come from the sources listed above; vendor claims are attributed.
Comments
Loading comments.





