The Butler
Back to briefings
Cloudflare / Agent browsers

Kitesurf goes open source: choose the browser for the job

· The Butler · 4 minute read

A metallic blue-eyed robot Butler gestures toward a bright library window, wearing a tuxedo and top hat.
Butler editorial illustration, not a product screenshot.

An AI that reads a public page does not necessarily need the same browser machinery as someone spending an afternoon inside a signed-in web application. Cloudflare's Kitesurf puts that distinction in the spotlight.

On November 13, Cloudflare released Kitesurf as open source under Apache 2.0. The browser engine runs on Workers and supports the Chrome DevTools Protocol, which lets tools such as Puppeteer connect to it. The announcement says developers can run the engine locally or deploy their own instance; deployment to Workers requires a paid plan. Cloudflare's announcement.

The interesting opportunity is not replacing every browser. It is giving a narrow automation a smaller tool that does enough, then keeping a fuller browser for the work that genuinely needs it.

Start with a public, repeatable task

A useful first experiment would be capturing a public product page or extracting a short article you have permission to process. Choose something whose correct result you can recognize without asking another model to judge it.

Write down the title, a few expected facts, and a visible detail that should appear in a screenshot. Then compare the output with the ordinary page. A successful request is not enough: missing content can make a neat-looking result misleading.

These are proposed checks, not results from a Butler benchmark. We have not run Kitesurf against a representative collection of websites, so we cannot promise a speedup or lower bill for your workflow.

Know where the smaller engine stops

Cloudflare's Browser Run documentation positions Kitesurf for one-shot tasks and compatible pages, not pixel-perfect Chromium replacement. It lists video, WebGL and long-running authenticated sessions requiring persistent state among the cases that need the default Chromium browser instead. Current Kitesurf limitations.

That gives a practical dividing line. Consider it for a contained page-reading or screenshot job. Do not start by moving your most complicated logged-in workflow, with its saved session and delicate sequence of forms, simply because an engine is now open source.

The same documentation cautions that web-standards test coverage does not establish compatibility with every real website. Our conclusion: your own short list of important pages is a better adoption test than a headline percentage. Compatibility guidance.

Open source changes your responsibility, too

Being able to inspect and modify an engine is useful. Operating your own copy also means choosing when to update it and checking whether a change affects your automations. Cloudflare describes Kitesurf as under heavy development, so treat the version you tested as part of your setup record. Release context.

Keep a simple record: page tested, expected result, actual result, engine version, and whether a full browser was needed. If only three of ten important pages work well, that may still be a useful specialized tool. It is not a reason to pretend the other seven are solved.

For a personal AI project, begin with the workflow rather than the infrastructure. Our learning paths and small project collection can help you define that first useful job. Then choose the browser that completes it reliably, rather than making every job fit the newest browser.

Checked November 15, 2026 using the official announcement and documentation. Product capabilities can change; this article does not claim independent performance testing.