Independent readiness aid · Source checked August 11, 2026

Is this workload ready for Kitesurf?

Classify the workload before changing a Browser Run endpoint. This tool runs locally and produces a planning result—not access, deployment, compatibility proof, or security approval.

Workload checks

Planning result

Complete the checks

Select what is true for the real workflow, then assess it.

  • Verify beta access, endpoint syntax, pricing, and limits.
  • Test output and CDP behavior on representative pages.
  • Keep least-privilege credentials and action approvals.
  • Record failures, cost, retries, and fallback rate.

Quick answer

Interpret the result as a pilot gate

A candidate result means the selected workload resembles Cloudflare's documented Kitesurf fit: short-lived, stateless, replayable, and tolerant of rendering differences. It does not prove that the target site, CDP commands, client library, authentication, or output will work.

A Chromium result means at least one documented exclusion is present. Do not work around that warning by silently dropping video, state, authentication, or security requirements. Keep the default engine or redesign the workflow and test it again.

For a pilot, version the target corpus and expected outputs. Compare Kitesurf and Chromium on task success, extraction accuracy, visual acceptance, console and network errors, retries, wall time, browser usage, and reviewer effort. Define a fallback threshold before traffic is routed.

Authorization remains separate from engine choice. Respect site rules, use least-privilege credentials, isolate untrusted page content from agent instructions, allowlist consequential actions, cap spend and navigation, and preserve logs. Recheck Cloudflare's beta documentation whenever the workload or release changes.

Continue with source-bounded guidance

Kitesurf beta guide

Access, fit, exclusions, tests, and security boundaries.

Browser-agent authority

Separate tool discovery from permission to act.

Agent tracing

Design traces, review, and operational signals.

Kitesurf readiness questions

It classifies local workload inputs against Cloudflare's documented Kitesurf beta fit and exclusions. It does not call Cloudflare, open a browser, inspect a site, or validate production compatibility.
Cloudflare currently points video, WebGL, real-TLS bot-challenge handshakes, and long authenticated stateful sessions to Browser Run's default Chromium browser.
No. You still need target authorization, representative site tests, current pricing and limits, security review, monitoring, fallback, and accountable approval.

Official references: Kitesurf launch and Kitesurf documentation. Verify current beta, compatibility, pricing, limits, and endpoint syntax before use.