Cloudflare open-sources Kitesurf, a browser engine for agents with no built-in auth
What is Kitesurf? An experimental browser engine from Cloudflare that runs on Cloudflare Workers and is built for AI agents rather than people. The code is now public on GitHub under the Apache 2.0 license, so you can run the engine in your own Cloudflare account. If you do, you have to put access control in front of it straight away: according to the README the engine has no authentication of its own and its address is public after deployment.
We read the announcement on the Cloudflare blog of August 6 and the repository README. On X, @CFchangelog said on November 14 that Kitesurf is open source.
What happened
Cloudflare released Kitesurf in August as a beta inside Browser Run, its headless browser automation service. At the time the company wrote that the engine would be open-sourced "once we're ready". That has now happened: the cloudflare/kitesurf repository is public, with 368 commits on main and no release or tag yet.
The engine parses HTML, applies CSS, runs page JavaScript and renders screenshots without Chrome or a browser container. It speaks the Chrome DevTools Protocol (CDP), so Puppeteer, Playwright and MCP clients can connect to it.
How it works
Kitesurf is mostly written in Rust and compiled to WebAssembly. It uses Stylo (Firefox's CSS parser), Blitz, Parley and the Boa JavaScript engine, among others. Each page runs in its own V8 isolate through Dynamic Workers. One component, SandboxOutbound, handles all network traffic and keeps a separate cookie jar per page.
| Measurement (median, 14 URLs) | Kitesurf | Chromium |
|---|---|---|
| CPU, screenshot | 380 ms | 1,173 ms |
| Memory, screenshot | 57.8 MiB | 271.0 MiB |
| Memory, HTML extraction | 39.4 MiB | 273.7 MiB |
| Wall time, screenshot | 1,148 ms | 637 ms |
The figures are Cloudflare's own (August blog post). Kitesurf uses far less compute and memory but is slower per page. Video, WebGL, bot challenges that need a real TLS fingerprint and long logged-in sessions do not work yet; for those Cloudflare points to Chromium.
Running it yourself
The README lists a paid Workers plan (for Dynamic Workers) as a requirement, plus Bazelisk, Node.js 22 or later and pnpm 9.15.4 for a local build. pnpm run deploy creates a Worker named kitesurf. You then have to put its address behind Cloudflare Access immediately. Without that step anyone with the URL can browse through your account, connect CDP clients, send outbound requests and use your compute time.
What this means
For anyone running browsing agents a lightweight engine is attractive: less memory per session means more sessions at once for the same money. We wrote earlier about AI assistants in the browser and about agentic AI in general. The missing authentication is the thing to watch; an open browser endpoint is a ready-made proxy for abuse. With an earlier leak at Cloudflare Workers AI we saw how quickly a configuration mistake becomes visible. More agent tools are in our overview of MCP servers and agent tooling.
What we did not check
We did not deploy Kitesurf ourselves or re-run the performance measurements. The page does not say exactly when the repository became public; the November 14 date comes from a post on X. We could not establish whether the free beta in Browser Run continues alongside the open-source version.
Checked on November 16, 2026.
This article was written with AI (Claude) and checked against the sources below.
Sources
- Cloudflare Blog, Introducing Kitesurf (August 6, 2026): blog.cloudflare.com
- cloudflare/kitesurf, README: github.com


