Kitesurf Cloudflare
#87 in Developer Tools
« A browser designed entirely for AI agents and running directly on Cloudflare's infrastructure. It was designed to browse and interact with the web on behalf of a user
»
Verified Tool
Kitesurf: Cloudflare strips the browser down to what AI agents actually use
Kitesurf is a stateless browser Cloudflare built for AI agents: it runs entirely on the Workers serverless platform, with no Chromium anywhere in the stack. Access goes through Browser Run and costs nothing during the beta, within per-account limits. On common automation jobs it uses 3 to 7 times less memory than Chromium. A public playground lets you check any page before writing a single line of code.
Pros
- 3 to 7 times lighter than Chromium on resources
- Works with Puppeteer, Playwright and CDP unchanged
- Isolated, disposable sessions built for bursty workloads
- Public playground for code-free testing
- Free for the whole beta period
Cons
- Pages come back 1.7 to 1.8 times slower than Chromium
- No video, WebGL or persistent logged-in sessions yet
- Aimed at developers already comfortable with the Cloudflare stack
Twelve weeks to rebuild a browser from scratch
Kitesurf started as a port of Obscura, an open source Rust headless engine, onto Workers. The prototype worked well enough that Cloudflare says it committed to building its own browser just twelve weeks before launch (the team is based in Lisbon, and the board-sport name is no accident).
Under the hood sits a pragmatic mix: the Blitz rendering engine, Firefox's Stylo CSS parser and the Boa JavaScript engine, compiled to WebAssembly and executed inside V8 isolates. The result passes over 235,000 subtests from the Web Platform Tests suite, with strong coverage of the DOM, HTML, SVG and network requests, the parts a headless browser actually exercises.
Kitesurf vs Chromium: cheaper sessions, longer waits
On Cloudflare's test corpus, Kitesurf uses 3.1 to 3.8 times less CPU and 4.7 to 7 times less memory than Chromium, while taking 1.7 to 1.8 times longer per page. The bet is simple: an agent grabbing a screenshot or scraping HTML does not care about 60 fps animations, it counts tokens and compute bills.
Picture your agent capturing 500 product pages in one burst: each page gets its own isolated instance, gone as soon as the task ends. Wikipedia, Hacker News, TodoMVC and the Cloudflare blog all render correctly. Beyond that, the division of labor is stated openly.
| Agent task | Recommended engine |
|---|---|
| Screenshots, HTML extraction | Kitesurf |
| PDF generation on compatible sites | Kitesurf |
| Form filling, JavaScript execution | Kitesurf |
| Video or WebGL rendering | Chromium via Browser Run |
| Long-lived authenticated sessions | Chromium via Browser Run |
| Bot challenges with TLS fingerprints | Chromium via Browser Run |
Getting started with Kitesurf: one API parameter
Kitesurf switches on by adding browser=kitesurf to any Browser Run CDP or Quick Action endpoint, with the rest of your code untouched. Existing Puppeteer and Playwright scripts keep working, and so do agents speaking CDP, handy if your automations already run through MCP servers.
Want to validate a page first? The public playground grants each navigation 20 seconds of CPU and 60 seconds of wall-clock time. The beta is free behind per-account limits, and Cloudflare has said nothing about what comes after, so keep the official docs open before shipping anything to production.
- Enable Browser Run from a Cloudflare account
- Add browser=kitesurf to a CDP or Quick Action endpoint
- Confirm site compatibility in the playground
- Fall back to Chromium for unsupported pages
Frequently asked questions
Is Cloudflare Kitesurf free?
Yes, Kitesurf costs nothing while in beta, behind per-account limits. Browser Run, the service hosting it, has a free tier with capped daily usage and paid plans with higher ceilings. No post-beta pricing has been announced, so the official page remains the reference once the beta ends.
Will Kitesurf be open source?
Cloudflare has stated it plans to open source Kitesurf so anyone can deploy their own instance. No firm date has been given so far. Until then, the browser is only reachable through Cloudflare's infrastructure, via Browser Run and the public playground.
Can Kitesurf handle logins or get past anti-bot protections?
No, not at this stage. Persistent authenticated sessions are unsupported, and Kitesurf cannot negotiate bot challenges that rely on a conventional browser's TLS fingerprint. Cloudflare recommends its hosted Chromium in Browser Run for those specific scenarios.
How is Kitesurf different from Browser Run's default Chromium?
Kitesurf targets cost and scale, while Chromium targets maximum compatibility. The former burns far less CPU and memory but renders pages slower and without pixel-perfect fidelity. Both live inside Browser Run, and a single parameter switches between them.
Verdict: Thousands of screenshots and HTML extractions without a ballooning compute bill: that is where Kitesurf already earns its keep. Teams running web agents on Cloudflare should try it while the beta is free, with Chromium still one parameter away for demanding pages.
★ Featured AI Tools ★
AI Alternatives for
Kitesurf Cloudflare
Paid
Free
Free
Free
Free-Trial
Paid
Paid
