# Cloudflare Kitesurf tested: agent browser without Chrome

Canonical: https://www.kartikaydhar.com/blog/cloudflare-kitesurf-agent-browser-tested
Published: 2026-11-15T03:53:10.677+00:00
Updated: 2026-11-15T02:48:33.55035+00:00
Category: Tool Breakdowns

I ran Cloudflare's open-source Kitesurf browser with my Puppeteer script. It read the same titles, links and text as Chrome, but loaded pages more slowly.

Kitesurf is Cloudflare's free, open-source web browser for AI agents, and it has no Chrome inside. Cloudflare says that lets it use "less CPU and memory than a full browser like Chromium", the open-source project Chrome is built on, while scaling on demand across its network. I couldn't test that on one machine. If your team already uses a script to control Chrome, you can point that same script at Kitesurf by changing one line. In my test it read the same titles, links and text as Chrome. The catch: it was slower than Chrome on 5 of 6 page loads, my first build failed, and hosting it on Cloudflare needs a paid plan.

Cloudflare open-sourced Kitesurf on 12 November 2026 under the Apache 2.0 license. I built it from the repo, ran it on my own machine and compared it with headless Chrome, which is Chrome running without a window.

## What I tested

- Version: the cloudflare/kitesurf repo as of 13 November 2026 (commit 4a29038). It has no numbered releases yet.
- Setup: installing the code libraries took 6 seconds. The first build failed. After a one-line fix, the build took about 6 minutes and the local server was up about 7 minutes after I started it.
- Task I ran: one Puppeteer script (Puppeteer is a common code library for controlling a browser from a script) that opened three pages, read each page's title, counted its links, measured its visible text and took a screenshot. I ran it against Kitesurf and against headless Chrome 156, twice, using Puppeteer 25.17.0.
- example.com load time: example.com loaded in 450 and 620 milliseconds in Kitesurf on my two runs, and in 459 and 82 milliseconds in Chrome.
- What worked: titles, link counts and text length matched Chrome on all three pages, in both runs.
- What broke or surprised me: the build failure, which the setup guide doesn't mention, and pages that loaded more slowly than in Chrome.

## What is Kitesurf?

Most tools that let an AI agent browse the web run a full copy of Chrome or Chromium. Kitesurf is a separate browser engine. The README says it "parses HTML, applies CSS, runs page JavaScript, and renders screenshots without Chrome or a browser container."

It runs on Cloudflare Workers, Cloudflare's service for running small programs across its network. Cloudflare first introduced Kitesurf in August 2026. It announced the open-source release on the Cloudflare blog.

It's built from several open-source projects written in Rust, a programming language, and packaged so they run on Cloudflare's network.

Kitesurf speaks CDP, the Chrome DevTools Protocol. That is the remote-control language Chrome uses, and tools like Puppeteer already speak it. So an existing script can switch over.

Both Cloudflare's changelog and the README call it experimental and under heavy development.

## How hard was it to get running?

Image: Illustration: How hard was it to get running?

My setup, redrawn from the build logs.

The README lists the tools you need first: Bazelisk, which fetches Bazel, Google's build tool; Node.js 22 or newer; and pnpm 9.15.4, a tool that installs JavaScript code libraries. Installing the repo's libraries took 6.4 seconds.

The first pnpm run dev, the command that builds Kitesurf and starts it, failed after about a minute. The error was cannot find -lstdc++. In plain words, the step that joins the compiled pieces into one program couldn't find the C++ standard library file it expected. My machine had the library itself but not the development link file that points to it. The README's requirements don't mention this.

I added that link by hand. On Debian or Ubuntu, installing g++, the C++ compiler package, normally brings it along. The second build then compiled Kitesurf's Rust code into a format that runs on Workers. Bazel reported 358 seconds, about 6 minutes, and the server was ready about 7 minutes after I started it. Bazel keeps a cache, so when I started Kitesurf again later, the build step took under a second and the server was ready within 20 seconds.

The local server listens at http://127.0.0.1:8787. Its health page replied kitesurf: OK.

## Did the same Puppeteer script work?

Yes. My script for Chrome launched a local headless Chrome. For Kitesurf I changed that one line to connect to Kitesurf's address instead, ws://127.0.0.1:8787/devtools/browser. Everything else stayed the same.

The script visited three live pages: example.com, the Hacker News front page and Cloudflare's own Kitesurf changelog post.

Image: Illustration: Did the same Puppeteer script work?

What each browser read from the three pages, from my script's output.

### What matched

Every number my script read matched Chrome exactly. Both browsers got the same page titles. They counted 1 link on example.com, 229 on Hacker News and 75 on the changelog. Visible text came to 917 characters, 4,244 characters and 3,068 characters. On my second run the Hacker News front page had changed and came to 4,235 characters, and again both browsers agreed.

### What looked different

The numbers don't tell you how a page looks, so I compared the screenshots too. The Cloudflare changelog looked almost identical in both. Hacker News did not. Kitesurf drew it with bigger text and more space between rows, so about 12 stories fit on the screen against about 17 in Chrome. The "Hacker News" title also ran straight into the "new" link next to it.

The server log also printed a "script terminated for unknown reasons" error each time a page closed. It didn't change any result.

### Speed

These are two runs of three pages, so read them as samples, not a benchmark. On the first run, example.com took 450 milliseconds in Kitesurf and 459 in Chrome. Hacker News took 862 in Kitesurf and 545 in Chrome, and the changelog took 1,408 and 467. On the second run Kitesurf was slower on all three pages: Kitesurf took 620, 805 and 1,399 milliseconds, and Chrome took 82, 562 and 268. Screenshots took between 58 and 303 milliseconds in Kitesurf and between 56 and 85 in Chrome.

The local Kitesurf server used about 650 MB of memory after my second run. I didn't measure Chrome's memory, so that number can't confirm or rule out Cloudflare's lower-memory claim, which is about Kitesurf running on Workers rather than this local test setup.

## What does it cost to run on Cloudflare?

The code is free. Running your own copy on Cloudflare needs the Workers Paid plan, which starts at $5 a month per account. Kitesurf uses Dynamic Workers, a feature that starts a separate small Worker for each page, and Dynamic Workers are only on the paid plan. Usage beyond the plan's included amounts is billed on top, per Cloudflare's Dynamic Workers pricing.

Kitesurf has no login of its own. The README warns that anyone with the address of a deployed copy could browse the web through it, send requests that come from your Cloudflare account and use CPU time you pay for. It tells you to put Cloudflare Access, Cloudflare's sign-in gate, in front of it straight away, and notes that the default address is public and easy to guess.

Cloudflare also offers Kitesurf through Browser Run, its hosted browser service, which runs browsers on Cloudflare's network so you don't run them yourself. Running your own copy is optional.

## How do I try it?

This is a job for an engineer. The first build took me about 7 minutes. A good first test is to point one script your team already runs against Chrome at Kitesurf and compare what comes back.

With Bazelisk, Node.js 22 and pnpm 9.15.4 installed, run the commands below. On a Mac, also install GNU tar first (brew install gnu-tar).

git clone \
  https://github.com/cloudflare/kitesurf.git
cd kitesurf
pnpm install --frozen-lockfile
pnpm run dev

If the build stops with cannot find -lstdc++, install your system's C++ development files (on Debian or Ubuntu, the g++ package) and run pnpm run dev again.

When it's ready, open http://127.0.0.1:8787/health. It should say kitesurf: OK. Then connect Puppeteer to it:

const browser = await puppeteer.connect({
  browserWSEndpoint:
    "ws://127.0.0.1:8787/devtools/browser",
});

There's also a simple page at http://127.0.0.1:8787/. Open it in Chrome, type a web address there and it opens in Chrome's developer tools, with Kitesurf doing the loading.

## What this means for product and GTM teams

Kitesurf is Cloudflare's attempt at a lighter browser for agents that read websites, for jobs like research, monitoring or copying details from web pages into a spreadsheet. It is now open code you can inspect and host yourself.

In my test, switching was a one-line change, and the data an agent would use, titles, links and text, came back the same as Chrome on all three pages. The page images were less consistent: one of my three pages looked noticeably different. If your agent relies on screenshots, compare them on your own pages before switching.

On my machine, Kitesurf was slower than Chrome on 5 of 6 page loads. Cloudflare's case for it rests on running at scale on Workers with less CPU and memory. It publishes standards test results and benchmarks on kitesurf.dev.

I tested two other ways of giving agents a browser earlier: Lightpanda, another browser built without Chrome, and agent-browser, which drives a real Chrome.

## Frequently asked questions

### Is Kitesurf free?

The code is free under Apache 2.0, and running it on your own machine costs nothing. Hosting it on Cloudflare needs the Workers Paid plan, from $5 a month plus usage.

### Does Kitesurf use Chrome?

No. It is its own browser engine built from open-source Rust projects. It speaks Chrome's remote-control language, CDP, so Chrome tools like Puppeteer can connect to it.

### Can I use my existing Puppeteer scripts?

In my test, yes: I changed one line to connect to Kitesurf instead of launching Chrome. The README says some Chrome developer tools features don't work yet.

### Is it safe to deploy?

Only behind a sign-in gate. Kitesurf has no login of its own, so Cloudflare says to protect any deployed copy with Cloudflare Access or similar.

## Sources

- cloudflare/kitesurf on GitHub (README, commit 4a29038, checked 15 Nov 2026)
- Kitesurf is now open source, Cloudflare Blog, 13 Nov 2026
- Kitesurf is now open source, Cloudflare changelog, 12 Nov 2026
- Dynamic Workers pricing, Cloudflare docs (checked 15 Nov 2026)
- Browser Run, Cloudflare docs (checked 15 Nov 2026)
- Workers pricing, Cloudflare docs (checked 15 Nov 2026)
