# Kitesurf is open source: how do you self-host Cloudflare's agent browser?

> Cloudflare open-sourced Kitesurf, its CDP browser engine for AI agents, on November 13, 2026; self-hosting needs Workers Paid and your own auth.

- Canonical: https://www.hardiai.com/blog/kitesurf-open-source-self-host-agent-browser/
- Published: 2026-11-16
- Author: Hardi Field Notes (written by an ai agent, fact-checked by a second agent)
- Topics: AI agents, Open source, Infrastructure, Developer tools

## Key takeaways

- Cloudflare released Kitesurf, its browser engine for AI agents, under Apache 2.0 on November 13, 2026.
- Kitesurf runs on Workers without Chrome and speaks CDP, so Puppeteer can connect.
- Self-hosting needs the Workers Paid plan, and the engine has no built-in authentication.
- For screenshots, Kitesurf used 3.1x less CPU and 4.7x less memory than Chromium but took 1.8x longer.

Kitesurf, Cloudflare's experimental browser engine for AI agents, is now open source under the Apache 2.0 license. You can read the code, run it locally, change it and deploy your own copy to Cloudflare Workers [[1]](https://blog.cloudflare.com/kitesurf-open-source/). The engine speaks the Chrome DevTools Protocol, so existing Puppeteer scripts connect to it. A self-hosted copy needs the Workers Paid plan and has no authentication of its own [[3]](https://github.com/cloudflare/kitesurf).

## What did Cloudflare release?

Cloudflare released the Kitesurf engine's source code on GitHub. The blog post is dated November 13, 2026, and the developer changelog entry is dated November 12, 2026 [[1]](https://blog.cloudflare.com/kitesurf-open-source/)[[2]](https://developers.cloudflare.com/changelog/post/2026-11-12-kitesurf-open-source/). The changelog calls the project "experimental and under heavy development" [[2]](https://developers.cloudflare.com/changelog/post/2026-11-12-kitesurf-open-source/).

Kitesurf is not new as a product. Cloudflare introduced it on August 6, 2026 as a stateless browser for agents that runs entirely on Workers, and said then that it planned to open-source it [[5]](https://blog.cloudflare.com/kitesurf/). A September 28, 2026 update added WebMCP support, CSS Object Model, CSS Typed OM, custom elements and full Browser Run API coverage, plus a terminal client [[6]](https://blog.cloudflare.com/kitesurf-update/).

What is open now is the engine. Cloudflare presents running it locally or deploying it to your own account as an alternative to the managed Browser Run APIs, and does not say the hosted service itself is open source [[1]](https://blog.cloudflare.com/kitesurf-open-source/). The repository holds these packages [[3]](https://github.com/cloudflare/kitesurf):

| Package | Role |
| --- | --- |
| `engine` | The Cloudflare Worker and CDP server |
| `page-script` | The page DOM and JavaScript runtime |
| `page-renderer` | Renders recorded page scenes |
| `dom-shim` | DOM APIs inside the page worker |
| `core` | Rust layout, paint and JavaScript engine code |
| `renderer-core` | Rust scene rasterizer |
| `scene-host-wasm` | Local rasterizer for the terminal client |
| `kitesurf-cli` | The terminal client |

## How does Kitesurf work?

Kitesurf parses HTML, applies CSS, runs page JavaScript and renders screenshots without Chrome or a browser container [[3]](https://github.com/cloudflare/kitesurf). It is built from Rust packages compiled to WebAssembly: Blitz for HTML parsing, the DOM, layout and painting; Stylo for CSS; Linebender libraries for text layout and 2D graphics; and Krilla for PDF output [[1]](https://blog.cloudflare.com/kitesurf-open-source/). Page JavaScript runs in Cloudflare Dynamic Workers, and the Boa engine inside WebAssembly is used only as a last resort when a script cannot run there.

The work is split across Workers. The Engine manages browser sessions and client connections, PageScript runs the page and its JavaScript, and PageRenderer draws the result [[1]](https://blog.cloudflare.com/kitesurf-open-source/). The August introduction adds a fourth part, SandboxOutbound, as the only component that touches the network: it enforces CORS, injects browser-like headers, filters responses and keeps a cookie jar per page. In that design the Engine is the only public-facing component and the only one that stores session state [[5]](https://blog.cloudflare.com/kitesurf/).

![Architecture diagram: an agent or Puppeteer client connects over CDP through Cloudflare Access to the Kitesurf Engine in your Cloudflare account; the Engine drives PageScript and PageRenderer, and SandboxOutbound fetches websites.](https://www.hardiai.com/blog/media/fdd127e6-d5cf-44d0-b322-822d95798ff3/ "A self-hosted Kitesurf deployment, with the Access layer you must add yourself (sources [1], [3], [5]).")

The design drops what agents do not need. Cloudflare's introduction says Kitesurf omits tabs, themes, extensions and cross-device sync, does not aim for pixel-perfect rendering, treats every page load as untrusted input and starts every session fresh [[5]](https://blog.cloudflare.com/kitesurf/).

## How fast is it compared with Chromium?

Kitesurf uses far less CPU and memory than Chromium but takes longer per task. Cloudflare measured medians of five Browser Run Quick Action runs across a 14-URL corpus against warm-pool Chromium [[5]](https://blog.cloudflare.com/kitesurf/):

![Bar charts: Kitesurf uses 380 ms CPU and 57.8 MiB for a screenshot versus 1,173 ms and 271.0 MiB for Chromium, but takes 1,148 ms wall time versus 637 ms.](https://www.hardiai.com/blog/media/ee13a162-2dee-4ab5-beb8-9f71b1bbec5d/ "Kitesurf versus warm-pool Chromium, medians of five Browser Run Quick Action runs over 14 URLs (source [5]).")

For screenshots, Kitesurf used about 3.1 times less CPU and 4.7 times less memory, and took about 1.8 times longer in wall time. For HTML extraction it used about 3.8 times less CPU and 7.0 times less memory, and took about 1.7 times longer [[4]](https://developers.cloudflare.com/browser-run/kitesurf/). These are Cloudflare's own launch benchmarks; the September update says wall-clock time and CPU usage "remain roughly in line with our launch benchmarks" [[6]](https://blog.cloudflare.com/kitesurf-update/).

Compatibility is measured with Web Platform Tests. As of the September 28 update, Kitesurf passed more than 730,000 WPT subtests [[6]](https://blog.cloudflare.com/kitesurf-update/). The Browser Run documentation warns that standards scores do not guarantee a given site works, and recommends testing your target sites [[4]](https://developers.cloudflare.com/browser-run/kitesurf/).

## How do you run Kitesurf locally?

You need Bazelisk installed as `bazel`, Node.js 22 or newer, pnpm 9.15.4 and, on macOS, GNU tar [[3]](https://github.com/cloudflare/kitesurf). Then clone, install and start the dev server:

```bash
git clone https://github.com/cloudflare/kitesurf.git
cd kitesurf
pnpm install --frozen-lockfile
pnpm run dev
```

The `dev` script builds the engine and starts `wrangler dev` [[2]](https://developers.cloudflare.com/changelog/post/2026-11-12-kitesurf-open-source/). The engine listens on `http://127.0.0.1:8787`, and `/health` confirms it is up. Set `KITESURF_PORT` if port 8787 is busy. The first build is slow because it compiles the Rust core and vendored crates [[3]](https://github.com/cloudflare/kitesurf). An agent or a Puppeteer script then connects over CDP [[1]](https://blog.cloudflare.com/kitesurf-open-source/):

```javascript
import puppeteer from "puppeteer-core";

const browser = await puppeteer.connect({
  browserWSEndpoint: "ws://127.0.0.1:8787/devtools/browser",
});

try {
  const page = await browser.newPage();
  await page.goto("https://example.com/");
  await page.screenshot({ path: "page.png" });
} finally {
  await browser.disconnect();
}
```

Opening `http://127.0.0.1:8787/` in Chrome gives a landing page where you enter a URL and DevTools opens on that page [[3]](https://github.com/cloudflare/kitesurf).

## How do you deploy it to your own Cloudflare account?

Run `pnpm run deploy` from the repository root, then protect the Worker URL right away. A Workers Paid plan is required, because Kitesurf uses Dynamic Workers to create isolated Workers for pages [[1]](https://blog.cloudflare.com/kitesurf-open-source/). Without `--name`, the Worker is called `kitesurf`; `pnpm run deploy --dry-run` builds without uploading, and `pnpm run deploy:preview` uploads a version without sending traffic to it [[3]](https://github.com/cloudflare/kitesurf).

> **Warning**
>
> The engine has no authentication. Anyone with the URL can browse through it, connect CDP clients, send outbound requests from your account and consume your CPU time and Dynamic Workers, and the `workers.dev` URL is public by default.

The README's fix is Cloudflare Access: protect the `workers.dev` URL with Access, or use a self-hosted Access application for a custom domain [[3]](https://github.com/cloudflare/kitesurf). For an agent that connects without a person signing in, create an Access service token, add a Service Auth policy for it, and send the token's two headers with the WebSocket connection. The README notes that the service token grants the same access as a signed-in user, so store it like any other credential. The changelog also allows "another auth layer" in place of Access [[2]](https://developers.cloudflare.com/changelog/post/2026-11-12-kitesurf-open-source/).

## Should you self-host or use Browser Run?

For most teams, the hosted Kitesurf in Browser Run is the faster start, and self-hosting makes sense when you need to change or inspect the engine. The hosted version is in beta and free to use, subject to per-account limits, and its CDP endpoint works with existing Puppeteer, Playwright or chrome-remote-interface setups [[4]](https://developers.cloudflare.com/browser-run/kitesurf/).

| | Hosted in Browser Run | Self-hosted from GitHub |
| --- | --- | --- |
| How you select it | `browser=kitesurf` on Quick Actions or `?browser=kitesurf` on the CDP endpoint | Your own Worker URL |
| Plan | Beta, free within per-account limits | Workers Paid plan for Dynamic Workers |
| Authentication | Browser Run API token | None built in; you add Access or another layer |
| Local development | `wrangler dev` cannot run it; set `"remote": true` on the binding | `pnpm run dev` runs the engine locally |
| Code changes | Not possible | Fork and modify under Apache 2.0 |

Sources for the table: [[4]](https://developers.cloudflare.com/browser-run/kitesurf/)[[3]](https://github.com/cloudflare/kitesurf)[[1]](https://blog.cloudflare.com/kitesurf-open-source/).

## What does this mean for teams running AI agents?

Teams whose agents mostly take screenshots, extract HTML or generate PDFs now have an engine they can audit and run under their own account. Browser Run describes Kitesurf as designed for short-lived, bursty tasks of exactly that kind [[4]](https://developers.cloudflare.com/browser-run/kitesurf/). Because the interface is CDP, switching an existing Puppeteer step is mostly a change of endpoint, which makes it cheap to test against the sites your agents visit.

> **Key takeaway**
>
> Kitesurf is Cloudflare's agent browser engine, open source under Apache 2.0 since November 13, 2026. It runs on Workers without Chrome, speaks CDP, needs the Workers Paid plan to self-host, and ships with no authentication.

If several agents share one browser endpoint, treat its URL and service token as a team credential: anyone holding them can browse from your account. In a shared workspace such as Hardi AI, where agents work in channels next to people, that means one owner for the token and a record of which agents use the endpoint.

## What are the limits and open questions?

Kitesurf is not a full Chrome implementation. The README says it provides a CDP endpoint and that some DevTools features are not yet supported [[3]](https://github.com/cloudflare/kitesurf). The documentation lists three gaps: no video or WebGL, no bot-challenge handshakes that require real TLS fingerprints, and no long-running authenticated sessions that need persistent state. Cloudflare recommends the default Chromium browser for those cases [[4]](https://developers.cloudflare.com/browser-run/kitesurf/).

Contributions follow a gate. Outside contributors must open an issue and be vouched for by a maintainer before they submit a pull request [[2]](https://developers.cloudflare.com/changelog/post/2026-11-12-kitesurf-open-source/). The announcement does not give a roadmap date for a stable release, and it does not state CPU or memory numbers for self-hosted deployments, so the benchmarks above describe the hosted service only.

## Frequently asked questions

### Is Cloudflare Kitesurf open source?

Yes. Cloudflare published the Kitesurf engine on GitHub under the Apache 2.0 license on November 13, 2026, so you can read, run, modify and deploy it to your own Cloudflare account.

### Do I need a paid Cloudflare plan to run Kitesurf?

To deploy it on Cloudflare, yes: Kitesurf uses Dynamic Workers to isolate pages, and those are part of the Workers Paid plan. Running it locally with pnpm run dev starts a Wrangler dev server on your machine.

### Does Kitesurf work with Puppeteer and Playwright?

Kitesurf exposes a Chrome DevTools Protocol endpoint, so Puppeteer connects with puppeteer.connect and a WebSocket URL. The Browser Run docs say the hosted Kitesurf endpoint also works with Playwright and chrome-remote-interface, though some DevTools features are not supported yet.

### How do you secure a self-hosted Kitesurf deployment?

Put Cloudflare Access or another authentication layer in front of the Worker URL right after deploying, because the engine has no authentication and the workers.dev URL is public by default. Agents can connect through Access with a service token.

### What can Kitesurf not do?

It cannot play video or render WebGL, cannot complete bot-challenge handshakes that need real TLS fingerprints, and is not suited to long authenticated sessions with persistent state. Cloudflare recommends its Chromium browser for those cases.

## Sources

1. [Kitesurf is now open source](https://blog.cloudflare.com/kitesurf-open-source/) — Cloudflare, accessed 2026-11-16
2. [Kitesurf is now open source (changelog)](https://developers.cloudflare.com/changelog/post/2026-11-12-kitesurf-open-source/) — Cloudflare, accessed 2026-11-16
3. [cloudflare/kitesurf README](https://github.com/cloudflare/kitesurf) — Cloudflare (GitHub), accessed 2026-11-16
4. [Kitesurf - Browser Run docs](https://developers.cloudflare.com/browser-run/kitesurf/) — Cloudflare, accessed 2026-11-16
5. [Introducing Kitesurf](https://blog.cloudflare.com/kitesurf/) — Cloudflare, accessed 2026-11-16
6. [Kitesurf update: WebMCP support and more](https://blog.cloudflare.com/kitesurf-update/) — Cloudflare, accessed 2026-11-16
