Skip to content
CrawlfolioSourced research on web data for AI
Menu

Explainer

Cloudflare Kitesurf is open source. Should you self-host it?

Cloudflare Kitesurf is Apache 2.0 now, but self-hosting needs Workers Paid and your own auth. When to self-host, use Browser Run or stay on Chromium.

Close-up of fine sand shaped by the wind into long flowing ripples and soft ridges
Photo: Jan Kopřiva / Unsplash · Unsplash License

Cloudflare open-sourced Kitesurf, its lightweight browser engine for AI agents, under Apache 2.0 on November 12, 2026. Cloudflare changelog. If your agent renders pages for screenshots, HTML or CDP automation, you now have three choices: Kitesurf through Browser Run, Kitesurf on your own Cloudflare account, or plain Chromium.

My short answer: use it through Browser Run while it’s free, keep Chromium as the fallback, and self-host only if you need to change the engine. Below are the costs, the security step most coverage skipped, and what still breaks.

Short on time?

Short on time? Here's my take.

Most agent builders
Kitesurf through Browser Run, Chromium as fallback
Free in beta and nothing to deploy: add browser=kitesurf to the call. Medium confidence, because the beta's per-account limits aren't published.
You need logins, video, WebGL or pages behind bot challenges
Stay on Chromium
Cloudflare's own docs say Kitesurf doesn't support these yet. Use Browser Run's default Chromium or another cloud browser. High confidence.
You want to patch the engine or keep it in your own account
Self-host, behind Cloudflare Access with a service token
Budget for an unknown Dynamic Workers line, which could add $0 to $398 a month at 100,000 pages. Medium confidence.
Speed matters most
Chromium
Kitesurf is slower in wall time in every dataset Cloudflare published. High confidence, on vendor data only.

Prices verified . Sponsors cannot buy a verdict or a position.

What did Cloudflare open-source on November 12? #

Kitesurf’s engine source code, under Apache 2.0, with a warning that it is “experimental and under heavy development”. The changelog is dated November 12 and the blog post November 13. The repo says bundled fonts, data and dependencies “keep their own licenses”, with details in its NOTICE file.

Kitesurf isn’t Chromium. Cloudflare’s blog describes an Engine, PageScript and PageRenderer built from Rust projects: Blitz for HTML, DOM and layout, Stylo for CSS, Boa for JavaScript in Wasm as a last resort, Linebender for text and 2D, and Krilla for PDF.

It has been public as a service longer. Cloudflare launched it on August 6, 2026 as a free Browser Run beta and promised to open-source it “once we’re ready”. The September 28 update added WebMCP support and described driving it through CDP, Playwright, Puppeteer or MCP. If MCP is how your agent drives a browser, my browser automation MCP server comparison covers the other options.

The repo had 1.7k stars, 88 forks, 17 open issues and 34 open pull requests when I read it. The blog says contributors must open an issue and “get vouched by a maintainer before opening a pull request”.

Is self-hosted Kitesurf really off Cloudflare? #

No. “A Workers Paid plan is required to run Kitesurf on Cloudflare”, says the changelog, and the blog explains why: “Kitesurf uses Dynamic Workers to create isolated Workers for pages”. Cloudflare describes Dynamic Workers as “a lightweight alternative to containers for securely sandboxing code you do not trust”.

You can run the repo locally for development with pnpm install --frozen-lockfile and pnpm run dev, which starts Wrangler at 127.0.0.1:8787, then pnpm run deploy. The first build compiles the Rust core. Cloudflare blog.

The repo lists Bazelisk, Node.js 22+ and pnpm 9.15.4 among the requirements.

There’s no documented way to run it off Cloudflare. A Docker image is an open request (#128), and a November 13 changelog entry says Browser Run Quick Actions now work under wrangler dev, but “The Kitesurf browser is not supported yet” there.

What must you lock down first? #

The front door. The engine has no authentication of its own, and the README is blunt: “Do not deploy Kitesurf without authentication in front of it.” It says to “Protect the Worker URL with Cloudflare Access immediately”, because “Between steps 1 and 2, the engine is public”.

Preview version URLs are public too.

An open URL is a billing and abuse problem. The README warns that strangers could “Use CPU time and Dynamic Workers that your account pays for” and “Send outbound requests that come from your Cloudflare account”.

CDP clients authenticate with an Access service token under a “Service Auth” policy, and “The token gives the same access as a signed-in user”. Store it like a password. Help Net Security’s write-up quotes the Workers Paid requirement but doesn’t mention authentication at all.

A rusty iron gate standing ajar in a sunlit doorway, its bars casting long shadows across a tiled floor
A gate only helps when it is shut: until an Access policy sits in front of the Worker URL, anyone who finds it can walk in on your bill. Photo: Hieu Do Quang / Unsplash · Unsplash License

What will Kitesurf cost you? #

On Browser Run, nothing for now: “Kitesurf is in beta and available for free, behind per-account limits”, and the docs don’t give the limits. Browser Run’s limits page lists Paid-plan numbers, such as 200 concurrent browsers and 30 Quick Action requests a second, but nothing for Kitesurf. Self-hosting costs more than you’d guess, mostly because of one unknown.

Here is my estimate for 100,000 screenshots a month, using Cloudflare’s November 16 benchmark medians as if they were billed time.

Route Monthly cost (my estimate) Arithmetic
Kitesurf on Browser Run $0 during beta Free behind unpublished per-account limits
Chromium on Browser Run (Quick Actions) About $8.06 100,000 x 1.59 s = 159,000 s = 44.2 h, rounds to 44 h; (44 - 10 included) x $0.09 = $3.06, plus $5 Workers Paid
Self-hosted Kitesurf, Dynamic Worker IDs reused About $6.09 $5 base + CPU: 100,000 x 843 ms = 84.3M ms, minus 30M included = 54.3M x $0.02 per million = $1.09
Self-hosted, 1 Dynamic Worker per page About $204 Adds (100,000 - 1,000 included) x $0.002 = $198
Self-hosted, 2 per page (page + renderer) About $404 Adds (200,000 - 1,000) x $0.002 = $398

Prices verified 2026-11-16 from Workers pricing, Dynamic Workers pricing and Browser Run pricing. Browser Run bills what the X-Browser-Ms-Used header reports, which may differ from benchmark wall time. Access costs are not included.

The spread comes from Dynamic Workers. The README says a separate worker starts for each page and renderer, and Dynamic Workers cost $0.002 per worker per day after 1,000 a month.

Whether IDs are reused isn’t documented, so the extra is anywhere from about $0 to $398. At 10,000 pages it’s $18 or $38.

So at list prices, self-hosting isn’t cheaper than Chromium on Browser Run, and it costs more than free beta Kitesurf. My Browser Run pricing breakdown has the Chromium billing detail, including concurrency charges for longer sessions.

Is Kitesurf faster than Chromium? #

No, it’s lighter, not faster. The docs measured 14 URLs (median of 5) against a warm Chromium pool and put Kitesurf at 1.8x slower in wall time for screenshots and 1.7x for HTML extraction.

The kitesurf.dev benchmarks page ran 38 pages on November 16. Here are both datasets side by side:

Measure (Cloudflare’s own data) Kitesurf Chromium Cold Chrome
Screenshot wall time, docs (14 URLs) 1,148 ms 637 ms (warm pool) n/a
Screenshot memory, docs 57.8 MiB 271.0 MiB (warm pool) n/a
Screenshot wall time, Nov 16 (38 pages) 2.39 s 1.59 s 999 ms
Screenshot CPU, Nov 16 843 ms 2.54 s 772 ms
Screenshot memory, Nov 16 49 MiB 396 MiB 330 MiB
HTML wall time, Nov 16 1.77 s 1.10 s 873 ms

Read from Cloudflare’s pages on 2026-11-16. The docs rows compare against a warm Chromium pool; the November 16 rows compare against Browser Run’s Chromium. The benchmarks page lists failures on both sides and a Kitesurf p95 of 31.3 s on one site.

My arithmetic: 2.39 / 1.59 = 1.50x slower on screenshots and 1.77 / 1.10 = 1.61x on HTML. Memory is the real win, 8.1x less than Browser Run on the November run. CPU is mixed: 3.0x less than Browser Run, but more than cold Chrome on screenshots.

Byteiota’s claim of “screenshots at 7x lower memory than Chromium” overstates it. Cloudflare’s docs table gives 271.0 / 57.8 = 4.7x for screenshots and about 6.9x only for HTML extraction.

What still breaks? #

A fair amount, by Cloudflare’s own list. The docs say Kitesurf doesn’t yet support video playback, WebGL, bot-challenge handshakes with real TLS fingerprints, or long-running authenticated sessions that need persistent state. It’s stateless and not pixel-perfect, and the README says it “provides a CDP endpoint, not a full Chrome implementation”.

On standards, the latest web-platform-tests run, dated November 16 when I read it, passed 98.3% of subtests (1,517,208 of 1,543,968) but only 77.3% of test files (9,093 of 11,764). Weak areas include performance-timeline at 40.7%, hr-time at 45.1% and wasm at 58.3%.

The open issues from November 14-16 show early-days problems:

  • #129: “Engine drops connections when several pages are created in parallel”.
  • #134: CDP evaluation in a same-origin iframe never returns.
  • #133: localStorage values don’t survive a reload.
  • #130 and #131: Windows build problems.

Interest is modest so far. The August launch reached 221 points on Hacker News; the open-source post got 3. HN search.

The plain top of a white building with ribbed wall panels and a single diagonal shadow under a flat grey-blue sky
A pared-down build is lighter to run, but every missing part is a page it may not handle, so check the gaps above against the sites your agent visits. Photo: Mahdi Naserinejad / Unsplash · Unsplash License

So which should you pick? #

Kitesurf on Browser Run for mostly static pages, and Chromium for anything Kitesurf can’t handle or when speed matters. Here is my pick by situation:

Your situation Pick Why
Screenshots or HTML of mostly static pages Kitesurf on Browser Run Free in beta, far less memory, no deploy
Logins, video, WebGL, bot challenges Chromium Kitesurf doesn’t support these yet
You need the lowest latency Chromium Slower wall time in both Cloudflare datasets
You want to modify the engine or keep it in your account Self-hosted Kitesurf Apache 2.0, but needs Workers Paid, Access and a Dynamic Workers budget
You can’t run on Cloudflare Another cloud browser No documented off-Cloudflare path

For the broader trade-off, see self-hosted vs managed browsers and my cloud browser roundup for AI agents. If you only need page text, search vs fetch vs browser may save you the browser altogether.

What I would do #

I’d point a copy of my screenshot and HTML jobs at ?browser=kitesurf on Browser Run, compare X-Browser-Ms-Used and failure rates against Chromium for a week, and route anything that fails back to Chromium. Omitting the parameter gives you Chromium, so the fallback is one line.

I wouldn’t self-host yet. I’d wait until Cloudflare says how Dynamic Workers are counted per page, or measure it on a small deploy that sits behind Access from the first minute. The agent browser hub maps the other cloud browser options for AI agents.

FAQ

Is Kitesurf free?

On Browser Run, yes for now. Cloudflare's docs say Kitesurf is in beta and free behind per-account limits, which it doesn't publish. Self-hosting needs a Workers Paid plan, which has a $5 a month minimum, plus CPU time and Dynamic Workers usage.

Can I run Kitesurf without Cloudflare?

Not in any documented way. It runs on Cloudflare Workers and needs Dynamic Workers. The repo runs locally under Wrangler for development, and a Docker image is only a feature request (issue #128).

Does Kitesurf work with Playwright and Puppeteer?

Through Browser Run, Cloudflare's docs say existing Playwright and Puppeteer setups already work via CDP. For a self-hosted engine, the README's only worked example is Puppeteer and it doesn't mention Playwright. It also notes that Kitesurf provides a CDP endpoint, not a full Chrome implementation.

Is Kitesurf faster than Chrome?

No. On Cloudflare's own numbers it uses far less memory but takes longer: about 1.7-1.8x slower in wall time in the docs, and 1.5-1.6x slower than Browser Run Chromium on the November 16 benchmarks page.

Is it safe to deploy Kitesurf?

Not without authentication. The README says 'Do not deploy Kitesurf without authentication in front of it' and tells you to protect the Worker URL with Cloudflare Access immediately, because the engine is public until you do.

What license is Kitesurf under?

Apache 2.0, per Cloudflare's November 12 changelog and the GitHub repo. Cloudflare still calls the engine experimental and under heavy development.

Sources

19 sources, accessed .

Official pricing, docs, changelogs and status pages 13

  1. Cloudflare changelog: Kitesurf is now open source (2026-11-12) developers.cloudflare.com · accessed
  2. Cloudflare blog: Kitesurf is now open source (2026-11-13) blog.cloudflare.com · accessed
  3. Cloudflare docs: Kitesurf on Browser Run developers.cloudflare.com · accessed
  4. Kitesurf benchmarks (run 2026-11-16) kitesurf.dev · accessed
  5. Kitesurf web-platform-tests results (latest run 2026-11-16) kitesurf.dev · accessed
  6. Cloudflare blog: Kitesurf launch (2026-08-06) blog.cloudflare.com · accessed
  7. Cloudflare blog: Kitesurf update (2026-09-28) blog.cloudflare.com · accessed
  8. Cloudflare changelog index (Quick Actions local dev, 2026-11-13) developers.cloudflare.com · accessed
  9. Cloudflare docs: Dynamic Workers pricing developers.cloudflare.com · accessed
  10. Cloudflare docs: Dynamic Workers developers.cloudflare.com · accessed
  11. Cloudflare docs: Workers pricing developers.cloudflare.com · accessed
  12. Cloudflare docs: Browser Run pricing (verified 2026-11-16) developers.cloudflare.com · accessed
  13. Cloudflare docs: Browser Run limits developers.cloudflare.com · accessed

GitHub code, issues and releases 3

  1. GitHub: cloudflare/kitesurf github.com · accessed
  2. Kitesurf README raw.githubusercontent.com · accessed
  3. Kitesurf open issues github.com · accessed

Community discussions 1

  1. Hacker News search: Kitesurf stories hn.algolia.com · accessed

News and press 1

  1. Help Net Security: self-host Kitesurf (2026-11-16) helpnetsecurity.com · accessed

Other blogs 1

  1. Byteiota: Cloudflare Kitesurf is open source byteiota.com · accessed