Cloudflare Kitesurf Is Now Open Source Under Apache 2.0

Cloudflare has kept a promise it made in August. On 13 November 2026, the company announced that Kitesurf, its experimental browser engine built for AI agents, is now open source on GitHub under the Apache 2.0 licence. Kitesurf is Cloudflare's stateless browser engine built for AI agents — it parses HTML, applies CSS, runs JavaScript and renders screenshots without a browser container, running entirely on Cloudflare Workers. Developers can now read the code, run it on their own laptop, change it, and deploy their own instance to their own Cloudflare account instead of relying only on Cloudflare's managed Browser Run service.

Why agents need a different kind of browser

A normal browser is built for a human sitting in front of a screen. It keeps tabs open, remembers logins, plays video and carries around the full weight of a desktop application. An AI agent does not need most of that. It needs to load a page, run its JavaScript, read what is there, click something, and take a screenshot — then do the same thing a thousand times, cheaply and in parallel.

That is the gap Kitesurf is designed to fill. It runs entirely on Cloudflare Workers, the company's serverless platform, and it has no browser container at all. It parses HTML, applies CSS, executes page JavaScript and renders screenshots, and it speaks the Chrome DevTools Protocol, known as CDP, so existing automation clients such as Puppeteer can connect to it exactly as they would to a full browser. The goal, in Cloudflare's own words, is a lightweight and efficient browser for agents that can load websites, execute JavaScript and interact with pages while using less CPU and memory than a full browser like Chromium, and scaling on demand across Cloudflare's global Workers network.

Software engineer looking at a lightweight browser engine running in a terminal window on a laptop, code on screen, modern workspace
AI-generated illustration (generated 15 Nov 2026)


What is inside the repository

Kitesurf is not a stripped-down copy of Chrome. It is a new engine assembled from open-source Rust packages compiled to WebAssembly, and Cloudflare names each piece in the announcement. Understanding the parts explains what the engine is good at and where it will struggle.

ComponentWhat it does
BlitzHTML parsing, the DOM, layout and painting
StyloCSS parsing, cascading and computed styles
BoaRuns JavaScript inside WebAssembly, as a last resort when JavaScript cannot run in Dynamic Workers
Linebender librariesText layout and 2D graphics
KrillaGenerates PDF output
EngineManages browser sessions and client connections
PageScriptRuns the page and its JavaScript
PageRendererDraws the rendered result

These projects made Kitesurf possible, and they keep their own licences — the repository's NOTICE file documents the third-party notices. That matters for anyone planning to use the code commercially: the Kitesurf code itself is Apache 2.0, which is a permissive licence that allows use, modification and distribution, but the dependencies carry their own terms, and the NOTICE file is where those are recorded. All packages, the engine, its Rust core, DOM shims, renderer and the Kitesurf command-line tool live in folders under the repository's packages directory, where developers can explore how the pieces fit together.

Running Kitesurf on your own laptop

The local setup is short, and Cloudflare publishes the exact commands. First, follow the repository's build requirements, then clone the repository, install dependencies and start the engine: git clone https://github.com/cloudflare/kitesurf.git, then cd kitesurf, then pnpm install --frozen-lockfile, then pnpm run dev. The first build compiles the Rust core and its dependencies, so Cloudflare warns to give it some time; later builds reuse the build cache. When it is ready, the local development server starts at http://127.0.0.1:8787, where you can open a page in Chrome DevTools or connect programmatically.

Open source code repository on a computer screen with a globe network map in the background, developer workspace
AI-generated illustration (generated 15 Nov 2026)

Deploying it to your own Cloudflare account

When you are done changing and testing locally, you can deploy the engine to your own account with a single command from the repository root: pnpm run deploy. From there you use Kitesurf from your own account instead of Cloudflare's managed Browser Run APIs. There is one condition that catches people out: a Workers Paid plan is required, because Kitesurf uses Dynamic Workers to create isolated Workers for each page. The open-source licence is free, but running it on Cloudflare's platform is not, and the paid plan is the price of that isolation.

Self-hosting also brings a security responsibility that Cloudflare states bluntly. Kitesurf has no built-in authentication, and the workers.dev address of a deployed instance is public by default. Deploy it without access control in front of it, and anyone with the address could browse the web on your bill. Cloudflare's answer is to put Cloudflare Access in front of it, and anyone deploying Kitesurf should treat that step as mandatory rather than optional. This is the kind of detail that is easy to skip in excitement and expensive to discover later.

What Kitesurf cannot do yet

Cloudflare is unusually honest about the limits, and the announcement repeats the word experimental. Kitesurf is under heavy development, with the team focused on making the engine more compatible, more reliable and more efficient. It is a CDP endpoint rather than a complete Chrome implementation, and some Chrome DevTools features are still unsupported.

Cloudflare's own documentation draws the practical lines. Kitesurf is not yet suitable for video, for WebGL, for bot-challenge handshakes that need real TLS fingerprints, or for long authenticated sessions that depend on persistent state. For those jobs, the company tells users to stick with its Chromium-based default browser. Extensions are also among the features traded away. None of this makes Kitesurf a failure; it makes it a specialised tool. A stateless engine is ideal for extraction, screenshots, and short agent tasks, and the wrong choice for a long logged-in session. Knowing which job you have is the whole decision.

Cloud data centre corridor with rows of server racks and orange network lights, wide angle photograph
AI-generated illustration (generated 15 Nov 2026)


Why this release matters beyond Cloudflare

Open-sourcing a browser engine is a bigger commitment than open-sourcing a library. It invites forks, contributions and criticism, and it lets competitors study the design. Cloudflare is inviting all of that: the project lives on GitHub, forks and contributions are welcome, and the contribution guidelines ask for issues with a minimal reproduction and a proposed approach, with focused fixes preferred over large rewrites. That is a normal open-source posture, but it is notable for infrastructure that sits close to a company's paid platform.

The release also lands in a wider open-source moment. The 96,000-star GitHub skill changing how developers work and the 41,000-star Hallmark GitHub skill both show how quickly developer tooling spreads once the code is public and the community can build on it. Kitesurf is a different kind of project — infrastructure, not a skill file — but the dynamic is the same: public code earns trust faster than a managed API alone. The open model world is moving the same way, as Mistral Large 4 open model and Kimi K3.1 Pro open reasoning model both show: openness is becoming a competitive feature rather than a concession.

Key Takeaways

  • Cloudflare open-sourced Kitesurf on 13 November 2026 under the Apache 2.0 licence, fulfilling a promise made when the engine launched in August 2026.
  • Kitesurf is a stateless browser engine for AI agents that runs entirely on Cloudflare Workers, parsing HTML and CSS, running JavaScript and rendering screenshots with no browser container.
  • It speaks the Chrome DevTools Protocol, so Puppeteer and similar tools can drive it; locally it runs at http://127.0.0.1:8787 after four commands.
  • Deploying to your own account needs a Workers Paid plan, and Kitesurf has no built-in authentication — put access control in front of any deployment.
  • It is experimental and under heavy development, not a complete Chrome: video, WebGL, extensions and long authenticated sessions are out of scope for now.

Conclusion

Kitesurf going open source is good news for anyone building AI agents that need to browse the web, and the licence is the headline: Apache 2.0, public on GitHub, free to read, modify and deploy. The engine itself is a focused bet that agents need something lighter than a full browser, and the parts list — Blitz, Stylo, Boa, Linebender and Krilla — shows serious engineering behind it. The honest limits matter just as much: it is experimental, it needs a paid Workers plan to deploy, it has no authentication of its own, and it is not a replacement for Chromium on hard jobs. Try it locally first, measure it on your own agent workloads, and watch the Web Platform Tests page. If compatibility keeps climbing, Kitesurf could become the default way agents see the web.

Sources

 

Comments