Skip to content
Rush Commerce
Tools & Teardowns3 min read

Cloudflare Kitesurf is open source: add your own auth

Cloudflare Kitesurf is open source under Apache 2.0. The agent browser runs on Workers, speaks CDP for Puppeteer, and ships with no built-in authentication. Protect it first.

Cloudflare Kitesurf is open source. The browser that Cloudflare built for AI agents is now on GitHub under Apache 2.0, and you can deploy it to your own Cloudflare account. Read one line of the changelog before you do: Kitesurf has no built-in authentication. If you deploy it without a gate, you publish a browser that anyone can drive.

What actually happened

Cloudflare's changelog entry is dated November 12, and the blog post followed on November 13. We covered the Kitesurf launch in August. Cloudflare said then that it would open the source. The facts now:

  • License and repository. Apache 2.0, at github.com/cloudflare/kitesurf. The Rust packages it uses keep their own licenses.
  • The stack. Rust packages compiled to WebAssembly: Blitz for HTML, DOM and layout, Stylo for CSS, and Boa for JavaScript only as a last resort when the page script cannot run in Dynamic Workers. Krilla writes PDF output.
  • Where it runs. On Cloudflare Workers, with no browser container. It parses HTML, applies CSS, runs page JavaScript and renders screenshots.
  • How you connect. It supports the Chrome DevTools Protocol. Cloudflare's example uses puppeteer.connect() against ws://127.0.0.1:8787/devtools/browser. The pages do not mention Playwright.
  • Local and deployed. pnpm run dev starts it with wrangler dev. pnpm run deploy puts it in your account.
  • The requirements. A Workers Paid plan, because Kitesurf needs Dynamic Workers to isolate each page.
  • The status. Cloudflare calls it "experimental and under heavy development." Neither page gives a measured performance number. The stated goal is less CPU and memory than Chromium.

Why open source Kitesurf matters for your business

Browser automation is a common first agent job: read supplier prices, fill a vendor portal, capture a competitor page. Until now the choice was a Chromium container that you operate, or a managed API that you rent. Kitesurf adds a third option: an engine whose code you can read, on a platform that scales to zero.

But read the limits before you move work.

  1. Put a gate in front on day one. Cloudflare says to use Cloudflare Access or another authentication layer. Do this before the first deploy, not after.
  2. Test your real target sites. An experimental engine will fail on some pages. Run your ten most important URLs and compare the output with Chromium.
  3. Keep the Puppeteer script portable. CDP is the contract. The same script can go back to Chromium when a page fails.
  4. Know what "open source" covers. You can read and fork the engine. The deployment still depends on Workers and Dynamic Workers. This is open code on one vendor's runtime.
  5. Price it from your own run. Cloudflare gives no cost figure. Measure one week of real jobs.

Key takeaways

  • Kitesurf is on GitHub under Apache 2.0 as of November 12
  • It runs on Cloudflare Workers and accepts Puppeteer over the Chrome DevTools Protocol
  • It has no built-in authentication: add Cloudflare Access or your own layer
  • Self-hosting needs a Workers Paid plan and Dynamic Workers
  • Cloudflare calls it experimental, so keep a Chromium fallback

A browser agent is only as safe as the gate in front of it. We build browser automation with authentication, a Chromium fallback and scripts you can move between engines. See how we build automation you own, or tell us which portal eats your team's hours.

Sources: Cloudflare blog: Kitesurf is now open source, Cloudflare changelog, November 12.

  • #cloudflare
  • #kitesurf
  • #browser-automation
  • #ai-agents
  • #open-source
TR

Tommy Rush — Founder, Rush Commerce

Operator turned builder. 15+ years running operations — now shipping the systems businesses run on. More

Get The Rush Report weekly — one email, zero fluff.