Cloudflare open-sourced its Kitesurf browser engine on Friday granting developers direct access to the Apache 2.0 licensed code on GitHub for local testing and self-deployment.
How Kitesurf Runs on Workers Without Chromium
Kitesurf operates entirely on Cloudflare Workers without launching a traditional desktop browser container. The engine processes web pages, executes page JavaScript, and outputs screenshots by splitting tasks across three internal roles. The Engine manages sessions and incoming client connections, PageScript executes the page scripts, and PageRenderer handles visual drawing.
Because PageRenderer maintains zero persistent page state, the Engine is able to substitute it following a stalled or failed rendering request. Behind the scenes, the Rust-based architecture compiles components to WebAssembly. Blitz parses HTML and builds the DOM, Stylo computes CSS rules, Linebender libraries handle text layout and 2D graphics, and Krilla generates PDF output. For JavaScript that Dynamic Workers cannot run natively, Boa provides a WebAssembly-based fallback runtime.
“Our main goal is to give AI agents a lightweight, efficient browser — one 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,” the Cloudflare team said in the August 6 launch announcement.
Instead of relying solely on the managed Browser Run APIs, the public repository grants developers the freedom to run and modify the engine inside their personal Cloudflare accounts. Developers have the ability to review and tweak the source code, execute it locally, or publish their very own instance on Cloudflare Workers.
Local Setup and Workers Paid Plan Requirements
Local development requires Bazelisk, Node.js 22 or newer and pnpm 9.15.4. Developers can fetch the repository and test the engine locally by installing dependencies and running the development server, which starts a local instance at 127.0.0.1:8787. Tools such as Puppeteer connect directly through the Chrome DevTools Protocol.
According to the instructions provided in the README for the Puppeteer approach, developers must generate an Access service token, authorize it via a Service Auth policy, and supply CF-Access-Client-Id alongside CF-Access-Client-Secret as headers when establishing the WebSocket connection. While the core code is free on GitHub, deploying an instance to a Cloudflare account requires specific infrastructure resources.
“A Workers Paid plan is required because Kitesurf uses Dynamic Workers to create isolated Workers for pages,” the developers said in the repository instructions.
Authentication Responsibilities for Self-Hosted Deployments
Self-hosting shifts the responsibility of managing external connections and access control entirely to the operator. Because deployed workers.dev URLs are public by default and feature easily guessed naming patterns, unauthenticated instances expose paid CPU time and Dynamic Workers to anyone who connects. Operating independently of Chromium, Kitesurf functions without any browser container while remaining capable of delivering page screenshots.

Cloudflare cautioned in its November changelog that “Kitesurf has no built-in authentication.” To prevent unauthorized access and resource consumption, operators must secure their deployment URLs using Cloudflare Access or a similar protection layer.