Cloudflare open-sources Kitesurf, its Chrome-free browser engine for AI agents
Cloudflare released Kitesurf under Apache 2.0 on November 13, 2026, with full source on GitHub.
· Last verified: 14 Nov 2026 (Cloudflare, Unite AI)

Summary
- Cloudflare released Kitesurf under Apache 2.0 on November 13, 2026, with full source on GitHub.
- The engine renders pages and runs JavaScript on Cloudflare Workers without Chrome or a browser container.
- Teams running web-browsing AI agents can now inspect, modify and self-host the engine.
The latest
Kitesurf, Cloudflare's experimental browser engine built for AI agents, is now open source under an Apache 2.0 license, Unite AI reported, with the code published at github.com/cloudflare/kitesurf. Developers can inspect and modify it, run it locally, or deploy their own instance on Cloudflare Workers. The engine first launched in August 2026 as a hosted product.
Details
- What it does: According to the repository README, Kitesurf parses HTML, applies CSS, executes page JavaScript and returns screenshots while running as a Cloudflare Worker — with no Chrome binary and no browser container behind it. Unite AI described it as swapping Chrome for a lighter engine that renders pages for AI agents.
- Compatibility: The engine implements the Chrome DevTools Protocol, so existing clients such as Puppeteer can connect to it directly. The README states CDP support is only partial, and some Chrome DevTools features do not yet work.
- The architecture: Components listed in the repository include engine (the Worker and CDP server), page-script (page DOM and JavaScript runtime), page-renderer, dom-shim, core for Rust layout, painting and the JavaScript engine, renderer-core, scene-host-wasm and kitesurf-cli. Unite AI said the components are written in Rust and compiled to WebAssembly.
- Built on: Kitesurf rests on existing open-source projects rather than a new stack: Blitz for HTML, DOM and layout, Stylo for CSS, Boa for JavaScript, Linebender libraries for text and 2D graphics, and Krilla for PDF output. Bundled fonts, data and dependencies keep their own licenses.
- The performance claim: Cloudflare's stated goal is lower CPU and memory consumption than running full Chromium, according to Unite AI. No benchmark numbers have been published to support the comparison.
- The limits: At the August launch Cloudflare said the engine was not yet suitable for video or WebGL, for bot-detection challenges requiring real TLS fingerprints, or for long authenticated sessions that depend on persistent state.
- Security warning: The README recommends protecting any deployment with Cloudflare Access, because anyone holding the link can browse through the engine and consume the account's resources. A workers.dev URL is public by default.
- Tooling gaps: There is no bundled documentation. The hosted DevTools frontend only connects to 127.0.0.1, so it does not work against a deployed engine; a bundled frontend works around this but adds roughly a 250MB download. chrome://inspect cannot reach an HTTPS engine and works only locally.
- What you need: Running it requires Bazelisk, Node.js 22 or newer, pnpm 9.15.4, and GNU tar on macOS. Rust via rustup is needed only when modifying bundled package patches, and a paid Cloudflare Workers plan is required for Dynamic Workers.
Between the lines
The dependency list reads as the core of the argument: by assembling Blitz, Stylo and Boa rather than shipping Chromium, Cloudflare can run page rendering inside a Worker. That design explains both the efficiency goal and the gaps — no WebGL, no real TLS fingerprints, partial CDP — since each is a Chrome capability the lighter stack has not reproduced.
What's next
Watch for published benchmarks against Chromium, expanded CDP coverage closing the DevTools gaps, and whether outside contributors begin landing changes in the public repository now that the license permits forks.
Source: Cloudflare, Unite AI