Image: Cloudflare
Why it mattersA team building an agent that drives a web browser can now read the engine. They can also run it locally and change it. Before today Cloudflare only offered a managed service.
The browser an AI agent uses to click around the web is often a closed service the team pays for. When the agent fails on a page, the team has no way to read the engine and work out why. Cloudflare has removed that limit for one of these browsers.
Cloudflare published the source code for Kitesurf under the Apache 2.0 licence. The repository is at github.com/cloudflare/kitesurf. The post was written by Celso Martinho on the Cloudflare blog.
What Kitesurf is
Kitesurf is a browser engine Cloudflare first launched earlier this year. Agents call it instead of driving a full Chrome or Firefox. Cloudflare says it uses less memory than a full browser. The engine has no user interface and no features meant for a human. The engine speaks the Chrome DevTools Protocol. An agent can drive it the same way it drives Chrome through Puppeteer or Playwright.
What is new today
Before today, Kitesurf ran as a managed service on Cloudflare Workers. A customer could use it, but could not read the code or change it. From today, three things are possible that were not possible before. A team can read the engine source on GitHub. A team can clone the repository and run Kitesurf on their own laptop. A team can deploy their own copy to their own Cloudflare account.
The deploy option still needs a Workers Paid plan. Kitesurf uses Dynamic Workers to give each page its own isolated Worker, and Dynamic Workers are a paid feature.
What is inside
Kitesurf is Rust compiled to WebAssembly. Cloudflare says each major job runs through an existing open-source library. Blitz, from Dioxus Labs, does HTML parsing, the document object model, layout and painting. Stylo, from Mozilla, handles CSS parsing and the cascade. Boa runs JavaScript inside WebAssembly. Linebender libraries handle text layout and 2D graphics. Krilla handles PDF output. The Kitesurf repository has three top-level packages: Engine, PageScript and PageRenderer.
Each library keeps its own licence. The NOTICE file in the repository lists them.
Where it runs
Cloudflare says a developer can run Kitesurf in two places. The first is locally on a laptop. The first build has to compile the Rust core, so it is slow. Later builds use the cache. The second place is the developer's own Cloudflare account. This needs a Workers Paid plan, because Kitesurf uses Dynamic Workers. The repository README has the exact commands.
What this does not say
The post gives no current count of Web Platform Test subtests. It gives no benchmark number for this release, and no new price. It does not name any customer. The post is also silent on the managed Kitesurf service. Cloudflare has not said whether that service is going away or will run alongside the open source copy. Cloudflare says the project is under heavy development. The team is focused on compatibility, reliability and efficiency.
What this changes
For a team building an agent that drives a browser, this is a rare open move. Before today, the team had three options. Pay for a managed agent browser. Run a full Chromium in a container. Write a browser driver. Running a full browser costs more memory, and a container service bills per minute. Kitesurf is now a fourth option the team can read before trying it. The gap to watch for is production support. Cloudflare has not said who to call when a self-run copy breaks in production.
Source
- Kitesurf is now open source, Celso Martinho, Cloudflare blog.
- cloudflare/kitesurf on GitHub.
This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.
Get AI News in your inbox
New developer tools, model and agent releases, and how teams are actually using them to release software. Short, and only when there is something worth reading.
