As of August 8, 2026, Beijing time, Cloudflare has opened Kitesurf testing by account through Browser Run. A public report published by TechCrunch on August 7 confirmed that the product is a cloud browser for AI agents rather than for daily browsing by humans. The Cloudflare announcement also notes that Kitesurf is still in its early stages and only supports a subset of the Chrome DevTools Protocol, and is not suitable for video playback, WebGL, or tasks that require real TLS fingerprinting challenges. The company plans to open source Kitesurf when preparations are complete, and hopes that customers can deploy customized versions in their own accounts in the future; however, no official date or license has been given.
Test portal and proxy browsing positioning
Currently, Kitesurf is available as a Browser Run test function on an account basis, but the date, price, and region of official availability have not yet been disclosed. The announcement clearly states that the product is still in its early stages and only supports a subset of the Chrome DevTools Protocol, which is not suitable for tasks such as video playback or WebGL. Cloudflare said it plans to open source the project when preparations are complete; however, no official date or license was given. In addition, Kitesurf is not a desktop browser designed for daily browsing by humans, but is developed for AI agents and automated applications that need to render web pages, extract HTML, take screenshots or generate PDF through the browser.
Cloudflare believes that traditional browsers such as Chromium contain a large amount of state overhead for human interfaces, which will increase memory and computing costs when deployed on a large scale. The design judgment given by the company is that the agent is more concerned with structured machine-readable content, contextual extensibility, and performance and cost control, and has less need for tabs, themes, extensions, and cross-device synchronization. Cloudflare said that Kitesurf is a stateless, isolated browser developed based on this judgment, with the goal of reducing resource usage for common proxy tasks. The above product motivations and effect targets are derived from company announcements and are not independent test conclusions.
Three components share session and rendering
Kitesurf consists of three main components: Engine, PageScript and PageRenderer: Engine is responsible for processing CDP WebSocket and HTTP REST interfaces and saving session state, while the other two components remain stateless; PageScript uses Dynamic Workers to start an isolated environment to parse HTML and CSS, and execute JavaScript or WebAssembly code. Officials stated that the relevant parsing uses Blitz components and Firefox's Stylo CSS parser, and handles occasional eval operations through the Boa engine written in Rust. Additionally, Kitesurf supports Puppeteer, Playwright, and proxy connections within MCP and CDP compatibility ranges.
PageRenderer obtains the page object from PageScript and obtains the fonts and images and rasterizes them into image buffers; Engine and the renderer communicate through Workers RPC to complete the final JPEG or PNG output. Each load is treated as untrusted input, each session is restarted, and SandboxOutbound performs operations such as URL verification, request header injection, and response filtering. Officially, the development process uses Web Platform Tests and multi-step Puppeteer integration testing on real websites; relevant test and benchmark numbers are self-reported by Cloudflare and have not been independently reproduced. Kitesurf's network access is concentrated through SandboxOutbound Worker, and other components cannot directly access the network.
Internal benchmarks show resource vs. speed trade-offs
According to the median data of Cloudflare's five Browser Run internal benchmarks: on the screenshot and HTML extraction tasks, Kitesurf used CPU time of 380 milliseconds and 229 milliseconds respectively, while Chromium consumed 1173 milliseconds and 877 milliseconds; in terms of memory usage, the former consumed 57.8 MiB and 39.4 MiB respectively, while the latter consumed 271.0 MiB and 273.7 MiB. Kitesurf in internal data used less CPU and memory, but its wall clock times were 1148ms and 820ms, respectively, about 1.7x to 1.8x slower than Chromium's 637ms and 472ms. These test results have not been independently replicated.
Kitesurf is suitable for proxy tasks such as HTML extraction, screenshots or PDF generation for compatible sites. However, it currently does not support video playback, WebGL rendering, and tasks that require real TLS fingerprint challenges and long-lasting authentication sessions. Officials stated that the project was in the early stages at the time of the announcement and clearly listed these limitations; for the above tasks, Cloudflare recommends continuing to use Browser Run's default Chromium. Kitesurf has not been independently verified, and existing materials cannot confirm that it can fully replace Chromium or prove the actual effect of security controls. Cloudflare has not yet announced an official availability date, price, or region list.
Applicable boundaries and open source plans to be determined
TechCrunch summarizes Kitesurf as a cloud-hosted browser, and Cloudflare officials more specifically describe it as running in V8 isolates of Workers and composed of multiple Worker components. The former summarizes the product form, and the latter explains the operating architecture. The two expressions do not conflict. The official status is still subject to the testing scope announced by the company: Kitesurf has not yet been officially commercialized, and it cannot be written as a comprehensive replacement for Chromium; it currently only supports a subset of CDP. Cloudflare's internal benchmarks also show that its wall clock time is slower than Chromium's, and neither its capability coverage nor its security effectiveness have been independently verified.
Cloudflare said the project was about 12 weeks old from launch to announcement, with the first commits occurring in May. The company plans to open source Kitesurf when preparations are complete, and hopes that customers can deploy customized versions in their own accounts in the future; however, officials have not yet given a specific date or license information, and the official availability date, price, and region list have not yet been announced. Cloudflare also said that the project has passed approximately 215,000 more Web Platform Tests, and continues to add more passing projects every week. Relevant tests and performance benchmarks come from the company's internal reports, and public materials do not provide external reproduction or independent audit records.