🇺🇸 English 🇰🇷 한국어 🇯🇵 日本語
Home › Developer Tools
Developer Tools

Cloudflare Open-Sources Kitesurf AI Browser

Cloudflare released the source code of Kitesurf, its experimental browser engine for AI agents, under Apache 2.0 on Nov. 13, letting developers run it locally or deploy their own instances on Cloudflare Workers.

Cloudflare on Nov. 13 released the source code of Kitesurf, its experimental browser engine for AI agents, on GitHub under the Apache 2.0 license. The move lets developers read and modify the engine, run it on their own machines and deploy private instances to their own Cloudflare accounts instead of relying only on the company's managed Browser Run service.

Curved glass and white office building in Lisbon's Alcântara district under a blue sky
An office complex in Lisbon's Alcântara district that houses Cloudflare, file photo. 사진: Dale Cruse - 10M views from San Francisco, CA, USA / 위키미디어 공용(CC BY 4.0)

Key takeaways

  • Kitesurf's code is now public at github.com/cloudflare/kitesurf under Apache 2.0, three months after the engine was first introduced in August.
  • Running it locally is free, but deploying it on Cloudflare requires a Workers Paid plan because each page runs in its own Dynamic Worker.
  • The engine has no built-in authentication, and the README tells self-hosters to put Cloudflare Access or another login layer in front of it.

What is Kitesurf, the Cloudflare browser for AI agents?

Kitesurf is a headless browser that runs entirely on Cloudflare Workers. According to the Cloudflare blog post announcing the release, it parses HTML, applies CSS, executes page JavaScript and renders screenshots without Chrome or a browser container. It speaks the Chrome DevTools Protocol (CDP), so clients such as Puppeteer can connect to it.

The engine has three parts: an Engine that manages sessions and client connections, PageScript that runs the page and its JavaScript, and PageRenderer that draws the result. It is assembled from open-source Rust projects compiled to WebAssembly, including Blitz for HTML parsing and layout, Firefox's Stylo for CSS, Boa as a last-resort JavaScript engine, Linebender libraries for text and graphics, and Krilla for PDF output.

The post was written by Cloudflare engineers Celso Martinho, Rui Figueira, Bernardo Pereira and Luís Duarte. Cloudflare said in September that it had added WebMCP support, new APIs and compatibility fixes.

How to run and self-host Kitesurf

The repository's README lists Bazel, Node.js 22 or newer and pnpm 9.15.4 as requirements. A single pnpm run dev command builds the Rust core and starts a local server at 127.0.0.1:8787, and pnpm run deploy pushes the engine to a user's own account.

The README carries a blunt warning. The engine "has no authentication of its own," and a default workers.dev address is public. Anyone with the URL could browse the web through the engine, send outbound requests from the owner's account and burn CPU time the owner pays for.

Cloudflare also says Kitesurf provides a CDP endpoint, "not a full Chrome implementation," and some DevTools features do not work yet. At launch in August, the company said video, WebGL, TLS-fingerprint bot challenges and long logged-in sessions were unsupported.

Kitesurf benchmarks and web standards tests

Cloudflare publishes live test data on kitesurf.dev. In a run dated Nov. 15, the median screenshot across 38 pages used 58 MiB of memory in Kitesurf, compared with 329 MiB for a freshly started Chrome. CPU time was 352 milliseconds versus 818 milliseconds.

Speed is a different story. The same median render took 1.51 seconds in Kitesurf and 1.00 second in cold-start Chrome, and some heavy news sites took several times longer. On the Web Platform Tests dashboard, Kitesurf passed 98.3% of subtests, or 1,517,208 of 1,543,968, in a Nov. 13 run, but only 77.3% of whole test files.

Median screenshot render across 38 pages (Kitesurf benchmark, Nov. 15, 2026)
MeasureKitesurfBrowser RunChrome (cold start)
Wall time1.51 s1.21 s1.00 s
CPU time352 ms1.88 s818 ms
Memory58 MiB399 MiB329 MiB

Why it matters

Running one full Chromium instance per agent gets expensive as agent fleets grow, which is the problem Kitesurf targets: lower memory and CPU per task in exchange for less fidelity. The release also delivers on an open-source promise Cloudflare made at launch.

The trade-off is lock-in. The code is open, but the engine depends on Cloudflare's Dynamic Workers to isolate pages, so a production deployment still runs on Cloudflare's paid platform.

What's next

Cloudflare says Kitesurf is under heavy development, with work focused on compatibility, reliability and efficiency. Contributors are asked to open an issue with a minimal reproduction and get vouched for by a maintainer before sending a pull request. As of Nov. 15, the repository showed 368 commits and 53 stars.

FAQ

Is Kitesurf free to use?
The code is free under Apache 2.0, and it runs locally at no cost. Deploying it on Cloudflare requires a Workers Paid plan.

Can Kitesurf replace Chrome for agents?
Not fully. Cloudflare recommends it for lightweight page loading and extraction, and it lacks video, WebGL and some DevTools features.

References

#Cloudflare #Kitesurf #AI agents #headless browser #open source #Cloudflare Workers #Chrome DevTools Protocol #Puppeteer
S
Seung Jung
AI Newsway · Developer

Editor responsible for AI Newsway. Writes about AI, developer tools, cloud and productivity technology.

More by this reporter ›
Copyright © AI Newsway All rights reserved. Unauthorized reproduction, redistribution, and AI training prohibited.
Share
f X K

Comments 0

Comments are currently disabled.

Be the first to comment.