Tech

News

Updated

Cloudflare makes Kitesurf, its browser engine for AI agents, open source under Apache 2.0

Key facts

The code is on GitHub, runs locally with pnpm, and can be deployed to a person's own Cloudflare account on a Workers Paid plan.

On Nov. 13, 2026, Cloudflare made Kitesurf open source, publishing its browser for AI agents, which runs entirely on Cloudflare Workers, on GitHub under the Apache 2.0 license.

What happened

Cloudflare said in its announcement that developers can now read the code, run it locally, change it and deploy their own instance to Cloudflare Workers. The code is in the cloudflare/kitesurf repository on GitHub.

The post says Kitesurf parses HTML, applies CSS, runs 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.

How it is built

According to the same post, Kitesurf has three main parts: the Engine manages browser sessions and client connections, PageScript runs the page and its JavaScript, and PageRenderer draws the result. It is built on Cloudflare's developer platform and on open-source Rust packages compiled to WebAssembly:

  • Blitz provides HTML parsing, the DOM, layout and painting.
  • Stylo provides CSS parsing, cascading and computed styles.
  • Boa runs JavaScript inside WebAssembly, used 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.

Those projects keep their own licenses, and the repository's NOTICE file lists the third-party notices.

How to run your own copy

The post gives these steps after the repository's build requirements are met: clone the repository, run pnpm install --frozen-lockfile, then pnpm run dev. The first build compiles the Rust core and takes longer, and later builds reuse the cache. Wrangler then starts a local development server at http://127.0.0.1:8787, and a Puppeteer script can connect to ws://127.0.0.1:8787/devtools/browser. That local address uses port 8787 over plain HTTP, not the standard web ports described in what port HTTPS uses.

To move off the local server, the post says pnpm run deploy from the repository root deploys the engine to the user's own Cloudflare account, in place of the managed Browser Run service. That step requires a Workers Paid plan, because Kitesurf uses Dynamic Workers to create isolated Workers for pages.

The numbers

Cloudflare's Kitesurf documentation compares the medians of five Browser Run Quick Action runs across a 14-URL corpus against Chromium with a warm pool:

MetricKitesurfChromium (warm pool)
CPU, screenshot380 ms1,173 ms
CPU, HTML extraction229 ms877 ms
Memory, screenshot57.8 MiB271.0 MiB
Memory, HTML extraction39.4 MiB273.7 MiB
Wall time, screenshot1,148 ms637 ms
Wall time, HTML extraction820 ms472 ms

The documentation says Kitesurf uses less CPU and memory than Chromium at the cost of slower wall time and rendering that is not pixel-perfect. It also says Kitesurf passes over 235,000 Web Platform Tests subtests, with coverage of 97 percent for DOM, 96 percent for HTML and 83 percent for URL in the latest run.

What comes next

The open-source post gives no date for a next release. It says Kitesurf is under heavy development, with work focused on compatibility, reliability and efficiency, and that updates will appear on the Cloudflare blog, the developer changelog and the kitesurf.dev site. Contributors are asked to open an issue with a minimal reproduction or a proposed approach and to be vouched for by a maintainer before opening a pull request.

The managed version stays in beta: the documentation says Kitesurf is free behind per-account limits. For how a server tells a client it has sent too many requests, see what HTTP 429 means.

Background

Cloudflare first announced Kitesurf on Aug. 6, 2026, as a browser that runs entirely on Workers, built for agents and available for free while in beta in Browser Run. The open-source post says a September update added WebMCP support, new APIs and improved compatibility.

What Kitesurf cannot do yet

The documentation says Kitesurf is not yet the right option to play video or render WebGL, to pass a bot-challenge handshake with real TLS fingerprints, or to hold a long-running, authenticated session that needs persistent state. For those cases it points to Browser Run's default browser, which is powered by Chromium.

Developers using the hosted service can opt in by adding browser=kitesurf to a Quick Action or to the Browser Run CDP endpoint. The documentation notes that under wrangler dev, a binding call with browser: "kitesurf" throws an error because Kitesurf is not available locally, and that setting "remote": true in the browser binding configuration works around it.

Have another question?