AivexaNewsSearch
AI news for builders and product teamsChecked every hour

Kitesurf is now open source

Collected Nov 13, 2026

Cloudflare has released Kitesurf, its stateless browser built for AI agents, as open source on GitHub under the Apache 2.0 license. The project first appeared in August, followed in September by WebMCP support, new APIs and improved compatibility, and Cloudflare said at each step that it intended to open the code so developers could run the engine on their own Cloudflare accounts. That is now possible: the code can be read, run locally, modified, and deployed as a self-hosted instance on Workers.

Kitesurf runs entirely on Cloudflare Workers. It parses HTML, applies CSS, executes page JavaScript and produces screenshots without a browser container such as the ones used to run headless Chromium. It speaks the Chrome DevTools Protocol (CDP), the interface Puppeteer and many automation and agent harnesses use to drive a browser, so existing CDP clients can connect to it. The stated aim is a lightweight browser for agents that loads sites, runs JavaScript and interacts with pages while consuming less CPU and memory than a full browser like Chromium, and that scales on demand across Cloudflare's global Workers network.

The design puts together a set of open-source Rust packages compiled to WebAssembly. Blitz handles HTML parsing, the DOM, layout and painting. Stylo covers CSS parsing, cascading and computed styles. Boa executes JavaScript inside WebAssembly, but only as a last resort, when JavaScript cannot run in Dynamic Workers. Linebender libraries provide text layout and 2D graphics, and Krilla generates PDF output. These dependencies keep their own licenses, and a NOTICE file in the repository records the third-party notices.

Internally the system splits into three parts: the Engine, which manages browser sessions and client connections; PageScript, which runs the page and its JavaScript; and PageRenderer, which draws the output. Packages for the engine, its Rust core, DOM shims, the renderer and a Kitesurf CLI each sit in their own folder under the repository's packages directory. This layout suggests a modular structure where the rendering pipeline, the scripting layer and session handling can be worked on or swapped somewhat independently, which is useful for anyone who wants to experiment with only part of the stack.

Running it locally takes a clone of the repository, an install with pnpm install --frozen-lockfile, and pnpm run dev. The first build compiles the Rust core and its dependencies, so it takes a while; later builds reuse the cache. Wrangler then starts a development server at http://127.0.0.1:8787. Opening that address in Chrome DevTools lets you try a page, and the same endpoint works programmatically. With puppeteer-core, for example, a Node script connects to ws://127.0.0.1:8787/devtools/browser, opens a new page, navigates to a URL, captures a screenshot and disconnects. An AI harness can also be pointed at the local CDP port and take control of the browser the same way it would drive Chrome.

Deploying to your own Cloudflare account uses pnpm run deploy from the repository root, after which the self-hosted engine can replace the managed Browser Run APIs Cloudflare offers. One constraint applies: a Workers Paid plan is required, because Kitesurf relies on Dynamic Workers to spin up isolated Workers per page. That per-page isolation is the mechanism behind the stateless model, and it is worth noting for cost planning that self-hosting does not mean the platform bill disappears; usage is billed under the paid plan, though Cloudflare does not detail specific pricing in this announcement.

Cloudflare describes Kitesurf as under heavy development, with work focused on compatibility, reliability and efficiency. Compatibility progress can be tracked through Web Platform Test results. Contribution starts with the project's guidelines: open an issue with a minimal reproduction or a proposed approach, then get vouched by a maintainer before submitting a pull request. Focused fixes with tests, clear evidence and a defined scope are easier to review than large rewrites or unrelated cleanup. Non-code help counts too — a small page that reproduces a rendering bug, a failing automation workflow, or a documentation correction are all cited as useful.

Why it matters: teams building agent workflows that need to load and interact with real web pages have so far mostly relied on headless Chromium containers, which are heavy to run and awkward to scale. A CDP-compatible engine on Workers, now self-hostable, gives developers a lighter option and lets them keep browsing traffic and execution inside their own Cloudflare account rather than a managed API. The trade-off, based on the emphasis on ongoing compatibility work, is that a young engine built on Blitz and Stylo will not match Chromium's coverage of every site and script edge case; teams should expect to test against their own targets and contribute fixes where rendering or scripts misbehave.

Read at Cloudflare AI

Based on reporting from the original publisher. Visit the source for full context and later updates.

Publisher excerpt

Kitesurf, our experimental browser engine for AI agents, is now open source. Inspect the code, run it locally, or deploy your own instance on Cloudflare Workers.