# Cloudflare open-sources Kitesurf, a Chromium-free browser engine for AI agents: what it does and its limits

> Cloudflare has released Kitesurf, its experimental Rust/WebAssembly browser engine that runs on Workers and speaks the Chrome DevTools Protocol, under Apache 2.0. Agent builders get a lightweight alternative to headless Chrome they can self-host, but compatibility is incomplete and there's no built-in authentication.

Published Nov 14, 2026 by TechMeasured Staff · Repos · Canonical: https://techmeasured.com/repos/cloudflare-kitesurf-open-source-chromium-free-browser-engine-ai-agents-what-it-does-limits

Cloudflare has open-sourced **Kitesurf**, the experimental browser engine for AI agents it introduced in August, under the **Apache 2.0** licence. The November 13 announcement puts the code at `github.com/cloudflare/kitesurf`, where it had about **1,320 stars and 59 forks** on November 15, according to GitHub's search API.

Why it matters: most agent "browsing" today means running headless Chrome in a container, which is heavy on CPU and memory and awkward to scale. Kitesurf has no browser container at all. It parses HTML, applies CSS, runs page JavaScript and renders screenshots inside Cloudflare Workers, and Puppeteer-style clients can drive it over the **Chrome DevTools Protocol (CDP)**. Until now you could only use it through Cloudflare's managed Browser Run APIs. Now you can read the code, run it locally and deploy it to your own account.

## How it's built

Cloudflare's post describes a Rust core compiled to WebAssembly, assembled largely from existing open-source projects:

| Job | Component |
|---|---|
| HTML parsing, DOM, layout, painting | Blitz |
| CSS parsing, cascade, computed styles | Stylo |
| Page JavaScript | Cloudflare **Dynamic Workers**, with the **Boa** engine (compiled to WebAssembly) as a last-resort fallback |
| Text layout and 2D graphics | Linebender libraries |
| PDF output | Krilla |

The engine has three parts: **Engine** (sessions and client connections), **PageScript** (page and JavaScript execution) and **PageRenderer** (drawing). Unite.AI adds that a separate **SandboxOutbound** worker handles all outbound fetches, enforces network policy and keeps each page's cookies separate. Third-party components keep their own licences, listed in the repo's NOTICE file.

## Try it

From Cloudflare's post:

```bash
git clone https://github.com/cloudflare/kitesurf.git
cd kitesurf
pnpm install --frozen-lockfile
pnpm run dev
# Wrangler serves http://127.0.0.1:8787
# Point Puppeteer at ws://127.0.0.1:8787/devtools/browser
```

- The first build compiles the Rust core and its dependencies and takes a while; later builds use the cache.
- Unite.AI lists the local requirements as **Bazelisk, Node.js 22+ and pnpm 9.15.4**. Check the repo's build notes before you start.
- `pnpm run deploy` puts it on your own Cloudflare account. That needs a **Workers Paid plan**, because each page runs in a Dynamic Worker. Local development doesn't.

## Limits to know before you build on it

- **Experimental.** Cloudflare says the engine is under heavy development, with work focused on compatibility, reliability and efficiency. Linuxiac notes Cloudflare says not all CDP features are supported yet.
- **No published benchmark in the announcement.** The pitch is lower CPU and memory than full Chromium, but the post doesn't include a measured comparison. It points to a benchmarks page and a Web Platform Tests page on kitesurf.dev instead.
- **Known gaps.** According to Unite.AI, at the August launch Cloudflare said Kitesurf wasn't yet suitable for video, WebGL, bot-challenge handshakes that need real browser TLS fingerprints, or long authenticated sessions.
- **Secure your deployment.** Unite.AI reports the engine has **no built-in authentication** and that its workers.dev address is public by default. Put Cloudflare Access or another auth layer in front of it before you deploy, or anyone who finds the URL can use your browser engine on your bill.
- **Contribution rules.** Maintainers ask contributors to open an issue and get approval before sending large pull requests.

## Who should care

Teams running agents that mostly read, scrape or screenshot ordinary pages, and that are tired of babysitting Chromium fleets, should look at it. If your agents need logged-in sessions, rich media, or need to get past anti-bot checks, a real browser is still the safer choice for now. The thing to watch is the Web Platform Tests pass rate on kitesurf.dev. That's the clearest sign of whether Kitesurf can handle more of the web than simple pages.


## Sources

1. [Cloudflare Blog — Kitesurf is now open source](https://blog.cloudflare.com/kitesurf-open-source)
2. [GitHub — cloudflare/kitesurf](https://github.com/cloudflare/kitesurf)
3. [Linuxiac — Cloudflare Open-Sources Kitesurf, Its Lightweight Browser Engine for AI Agents](https://linuxiac.com/cloudflare-open-sources-kitesurf-its-lightweight-browser-engine-for-ai-agents/)
4. [Unite.AI — Cloudflare Open-Sources Kitesurf Browser Engine for AI Agents](https://www.unite.ai/cloudflare-open-sources-kitesurf-browser-engine-for-ai-agents/)
