Create an elegant, captivating landing page for Kitesurf — Cloudflare's stateless, agent-first browser that runs entirely on Workers. Cloudflare's own page for it is a dry documentation surface; this page should be the opposite: a beautiful, memorable product landing experience that makes developers feel the idea of a browser built for machines, not humans.
The core story to tell: Kitesurf is a stateless, highly scalable browser designed for AI agents. Instead of shipping a full desktop engine like Chromium, it focuses on what matters to an agent — token count, context windows, scalability, performance, and cost — while trading away features only humans need, such as tabs, themes, extensions, and pixel-perfect rendering. It spins up as an ephemeral, fully isolated engine that exists only for the duration of a task, which makes it ideal for bursty, AI-driven workloads: screenshots, HTML extraction, PDF generation, and one-shot automation through Browser Run Quick Actions, a CDP endpoint that works with existing Puppeteer/Playwright setups, and any MCP client that speaks CDP.
Ground the page in real, concrete substance — not generic marketing filler. Weave in the actual proof points: Kitesurf passes over 235,000 Web Platform Tests subtests with strong coverage where agents care most (DOM 97%, HTML 96%, Selection 99%, SVG 97%, Encoding 99%, CORS 95%, XHR 95%, URL 83%). Against Chromium on Browser Run Quick Actions it uses 3.1× less CPU for screenshots (380 ms vs 1,173 ms), 3.8× less CPU for HTML extraction, 4.7× less memory for screenshots (57.8 MiB vs 271.0 MiB), and 7.0× less memory for HTML extraction — the metrics that drive your bill — while Chromium keeps a modest wall-time edge. It correctly renders real sites like TodoMVC (vanilla, React, Vue, Angular, Preact), Wikipedia, Hacker News, and the Cloudflare dashboard. Be honest and confident about the trade-offs: no video, no WebGL, no bot-challenge TLS fingerprinting, no long-running authenticated sessions — for those, Chromium remains the right tool. It is in beta and currently free. The honest limits should feel like engineering candor, not fine print.
Show how a developer actually touches it: a screenshot Quick Action curl with `browser=kitesurf`, a CDP websocket URL that drops into an existing Puppeteer or Playwright setup with one query parameter, and an MCP client configuration block. Present code as first-class designed objects — syntax-highlighted, copyable, beautifully typeset — not as afterthoughts.
Let the concept drive the art direction. Kitesurfing is wind, water, lift, and motion; a stateless browser is something that appears out of nowhere, does its work, and vanishes. Find an elegant visual language in that tension — lightness, ephemerality, speed, scale — and carry it through typography, color, motion, and atmosphere. Motion should feel like wind: smooth, physics-eased, purposeful. The page should feel designed by someone with exceptional taste, not assembled from a template — no generic gradient-blob SaaS look, no cookie-cutter hero-plus-three-cards layout.
Give visitors things to feel and do, not just read: consider ways to make the scale story tangible (what "7× less memory" or "exists only for the duration of a task" actually looks like), let the performance comparison live as something visual and explorable rather than a static table, and let the standards-coverage numbers feel like an engineering instrument panel. Scroll should unfold a narrative with momentum: hook, concept, proof, honesty, code, call to action. Include hover, focus, and responsive states throughout, and make the page fully usable and beautiful from a small phone to a wide desktop monitor.
End with clear calls to action: try the public playground at kitesurf.cloudflare.app, read the docs, and start building — it is free in beta.
Do not take shortcuts or settle for a cookie-cutter landing-page template. This skill imposes no token budget limit, so pursue complete, subject-specific depth across the hero, narrative sections, data visualizations, code presentations, motion design, responsive behavior, and every secondary state — and keep refining until the page feels genuinely authored, elegant, and captivating: clearly better than the documentation page it replaces.