Kitesurf deserves a prototype, not yet a replacement for the browsers that validate your sites. On 12 November 2026, Cloudflare announced that its code is now open under the Apache 2.0 licence: we see it as a way to lighten some web automations, provided the reliability of the results is preserved.
Kitesurf: what opening the code changes
According to Cloudflare's announcement, Kitesurf runs entirely on Workers, its execution platform, without launching a conventional browser container. The engine processes HTML and CSS, runs the pages' JavaScript and produces screenshots. Its CDP interface, the protocol used to control Chrome, notably allows it to be connected to Puppeteer.
Opening the code lets you examine the engine, run it locally with Wrangler or deploy your own instance on Cloudflare. For that deployment, the announcement states that you need a Workers Paid subscription and Dynamic Workers, which creates isolated environments for pages.
This change mainly matters for tools that visit pages on your behalf. For an SME, the question becomes practical: could you check content or feed an AI agent with fewer resources while keeping a usable result? Access to the code gives you more grip on that assessment. It does not remove the need to carry it out.
For a French-speaking Swiss SME, a use to be chosen precisely

We would start with a short, verifiable task: read a piece of information on a public page, check that some content is present, or produce a screenshot for an agent. The expected result must be explicit. “The page opened” is not enough if the information you are looking for only appears after an interaction.
Cloudflare’s documentation positions Kitesurf precisely on agents and one-off operations that are compatible with a rendering that is not pixel-identical to Chromium. It also flags limits for video, WebGL and long authenticated sessions that need to keep state.
This calls for a distinction in your projects. To extract a text, we would check that it is present and accurate. To approve the appearance of a page before publication, we would keep a check in the browsers the site targets. A screenshot that an AI can use is not, on its own, a validation of your visitors’ experience.
This caution fits with preparing WordPress and PHP compatibility tests: the check must cover the journeys that matter to the business. A form, a search or a basket deserves more attention than a page that merely displays.
Our view: fewer resources does not mean less waiting
The decisive point lies in the comparisons published by Cloudflare. Its documentation reports lower memory and compute consumption for certain operations, but a longer total time compared with an already-running Chromium. A lighter engine does not necessarily arrive sooner.
So we would not take faster pre-deployment checks for granted. For a team that waits for its tests to finish before publishing, the full duration is what counts. For agents running many independent tasks, resource consumption could weigh more heavily in the decision.
Our position is clear: explore Kitesurf on a limited scope, then decide based on the failures as much as the gains. Cloudflare still describes the project as experimental. We would keep Chromium as the reference for the checks a go-live depends on, until the prototype has shown it fits the need.
A prototype scoped before any adoption
We would organise the trial around three points, with a decision expected at the end: continue for certain uses, fix the setup, or keep the current tools.
- Compare the same journeys. The prototype would cover a few Next.js and WordPress pages, with dynamic JavaScript. We would compare Kitesurf with Chromium driven by Playwright or Puppeteer, asking for the same actions and the same results.
- Measure the service delivered. We would record start-up time, total duration, memory used, rendering fidelity and success rate. The tests would distinguish a cold start from a browser that is already available. A fast run that misses the expected content would count as a failure.
- Protect the trial instance. The announcement states that Kitesurf has no built-in authentication and asks for the deployment to be protected with Cloudflare Access or another access layer. We would start with public pages and fictitious data, in a separate environment, before considering use connected to company tools.




