Runs entirely on Cloudflare Workers

A browser built for agents,
not people.

Kitesurf strips away the browser features AI never needed—so every agent gets an isolated, standards-aware browser without hauling around Chromium.

Try a real page See the numbers

3–7×less CPU & memory

235k+WPT subtests passed

0servers to manage

agent-session.ks Isolate ready

Agent objective

“Open the product page, extract the key benefits, and return structured data.”

01Launch ephemeral browser12 ms

02Navigate & render pageready

03Query DOM via CDP42 nodes

04Return agent-ready result1.8 kB

{
"browser": "kitesurf",
"format": "structured",
"session": "disposed"
}

Illustrative workflow. Use the playground below for a live Kitesurf run.

Live product

Send a page to Kitesurf

Choose an action and continue in Cloudflare’s public playground—no API token required.

The difference

Chromium is a desktop.
Kitesurf is a tool.

Agents don’t need tabs, themes, extensions, synced profiles, or perfect 60 fps rendering. They need the web’s useful primitives—on demand.

Ephemeral by design

One task. One isolate. Zero baggage.

Every session starts clean, runs only as long as the task needs, and disappears when the work is done.

Agent WasmDOMCSS

Agent native

Speaks CDP

Existing Puppeteer, Playwright, and Chrome DevTools Protocol clients can opt in with one parameter.

Edge scale

Born on Workers

Stateless components and V8 isolation make bursty browser workloads disposable and parallel by default.

Resource calculator

See what “lighter” looks like.

Official median results across a 14-URL corpus. Adjust concurrent sessions to model resource footprint.

Agent task

Screenshot HTML extraction

Concurrent sessions100

10500

At this concurrency, Kitesurf avoids

20.8 GiB of aggregate browser memory footprint

Median per taskKitesurfChromium

CPUCompute consumed

380 ms

1,173 ms

MemorySession footprint

57.8 MiB

271.0 MiB

Wall timeEnd-to-end latency

1,148 ms

637 ms

Purposeful trade-off: Kitesurf minimizes the CPU and memory that drive infrastructure cost; warm Chromium still wins on wall time.

Source: Cloudflare Kitesurf documentation . Medians of five Browser Run Quick Action runs; Chromium used a warm pool.

Connect your agent

Same tools.
Much lighter browser.

Point any CDP-compatible agent at Kitesurf. The public playground endpoint works without a Chrome install or API token.

View integration docs

MCP config

{
  "mcpServers": {
    "kitesurf": {
      "command": "npx",
      "args": [
        "-y",
        "chrome-devtools-mcp@latest",
        "--wsEndpoint=wss://kitesurf.cloudflare.app/devtools/browser"
      ]
    }
  }
}

Choose the right browser

Use Kitesurf where it shines.

A focused engine is valuable because it makes explicit trade-offs. Here’s the honest fit.

Reach for Kitesurf

One-shot screenshots and HTML extraction
AI research and structured web retrieval
Bursty, parallel agent workloads
Fresh, fully isolated browser sessions

Use Chromium for now

Video playback or WebGL rendering
Pixel-perfect visual reproduction
Long-running authenticated sessions
Sites requiring real TLS fingerprints

The web is your agent’s interface

Give it the browser
it actually needs.

Launch Kitesurf playground Read the docs

A browser built for agents,not people.