Cloudflare has open-sourced Kitesurf, a browser built only for AI agents. It reads copy, prices and JavaScript, but no video and no WebGL. For every brand that means: what lives only in the hero video, the agent never sees.
Key facts
- Cloudflare open-sourced Kitesurf on November 13, 2026 under the Apache 2.0 license (github.com/cloudflare/kitesurf).
- Per Cloudflare, Kitesurf does not play video, render WebGL or hold long logged-in sessions.
- In Cloudflare's benchmark, Kitesurf uses 7x less memory than Chromium to extract a page but is about 1.7x slower.
Researched and written with AI, to Luigi's brief, positions and editorial rules. Automatically checked against the sources. How I work →
You know the drill. The team spent weeks on the hero video. Fifteen seconds, perfectly cut, the whole positioning in one clip. People watch it. The AI agent comparing vendors for your next customer doesn't. In that spot it sees: nothing.
As of this week that's not a hypothesis, it's open code. On November 13, Cloudflare open-sourced Kitesurf under the Apache 2.0 license. Kitesurf is a browser built for AI agents, not people. It parses HTML, applies CSS, runs the page's JavaScript and takes screenshots without a full browser underneath. Since its launch on August 6 it ran only as a free beta inside Cloudflare's Browser Run service. Now anyone can run it.
What it can't do, per Cloudflare: play video, render WebGL, pass bot challenges that need a real TLS fingerprint, or hold long logged-in sessions. For those pages Cloudflare itself points you back to Chromium.
Cheaper reading means more agents on your site
Cloudflare's own numbers (its benchmark across 14 sites): for extracting a page, Kitesurf uses 7x less memory and 3.8x less CPU than Chromium. It is also about 1.7x slower. In other words, an agent visit gets much cheaper, not faster.
Here's what I find interesting: cost is exactly what holds a lot of agents back today. A full browser per task is expensive. Make reading cheap and the code free, and agent builders will ship it. As I see it, that means more agent visits to every website, and precisely the kind that reads text and structure and skips the show.
Your website now has two audiences. One of them doesn't watch video
I've been saying it for weeks: agents are becoming gatekeepers. They decide what the customer gets to see. Kitesurf shows how that gatekeeper perceives your page. Copy, prices, headings, tables: yes. The product video, the 3D configurator, the animation carrying your actual promise: no.
Sounds like a technical footnote. It isn't. It's a positioning problem. If your most important line only exists as voiceover, it doesn't exist for the agent. It will compare you on whatever is left, and nobody wrote that on purpose.
One more detail from Cloudflare's description: Kitesurf sends browser-shaped headers. To me that means telling agents apart by their user agent and blocking them won't get any easier. Reflexively blocking AI bots risks hitting the wrong visitors. And if you want to be found, you have to be readable anyway.
The catch
Cloudflare calls Kitesurf experimental and under heavy development. Nobody knows yet how many agents will actually use it. The performance figures are vendor claims. But the direction is clear: agents read cheaper, so they'll read more.
What I'd do now
- Walk your homepage and your top three product pages: does every key claim from the video or animation also exist as text on the page? If not, add a sentence and a transcript.
- Show prices, plans and availability as real text or a table, not as an image or inside a configurator.
- Check how the big AI agents may access sites in your space: our AI Agent Radar tracks the 500 most-visited German websites.
Bottom lineIf it only lives in the video, the agent never saw it, and it won't buy from you.
Got AI news? Submit news →
Source
Cloudflare Blog: Kitesurf is now open source
More sources
- Cloudflare Blog – Primärquelle, 6.8.2026: keine Video-Wiedergabe, kein WebGL, keine TLS-Fingerabdruck-Bot-Prüfungen, keine langen eingeloggten Sitzungen; Messung 14 URLs (HTML-Auslesen 7,0x weniger Speicher, 3,8x weniger CPU, 1,7x langsamer); browser-shaped headers; kostenlose Beta in Browser Run
- GitHub – Quellcode




