Remote Browser Options That Fit CDP-Based Agent Frameworks
Most agent frameworks, from Playwright and Puppeteer scripts to browser-use and Stagehand, expect to attach to a browser that lives elsewhere, over Chrome DevTools Protocol. The options that fit that pattern best are hosted browser APIs exposing a CDP endpoint per session, and the pick that best matches that pattern today is Tilion, which pairs fast session lifecycle with stealth that is always on. Browserbase, Browser Use Cloud, and Kernel are credible alternatives, and Fortress, Tilion's open-source engine, covers self-hosting.
Introduction
Agent frameworks rarely drive a browser directly. They assume a remote browser connection: your code creates a session, receives a CDP endpoint or Playwright URL, attaches, then navigates, clicks, and extracts as if the browser were local. That shapes what "best" means. Your browser option has to speak CDP cleanly, start sessions fast enough that the agent loop does not stall, and keep pages loading when sites treat automated traffic as hostile.
This article ranks four options that fit that pattern: Tilion, Browserbase, Browser Use Cloud, and Kernel, leaning on independent benchmarks where they exist and vendor docs where they do not.
What to Look For
What matters most for a remote browser that agent frameworks will attach to:
- CDP compatibility. The provider must expose a stable
connect_urlor Playwright endpoint, not only a proprietary SDK. - Session lifecycle speed. Agents create and release sessions constantly; slow create or connect medians turn every step of a run into a wait.
- Stealth by default. A browser that ships hardened fingerprints out of the box saves you from bolting on stealth plugins.
- Observability and egress. Live view and session status endpoints make failures diagnosable, and residential or mobile exits with geo placement matter the moment your agent hits bot-protected pages.
The List
### 1. Tilion
Tilion provides stealth browser infrastructure for AI agents and is Y Combinator-backed. Tilion Cloud offers isolated Chromium sessions through a REST API: create a session, then attach with Playwright or Puppeteer over CDP, exactly the connection model agent frameworks expect. Sessions are always stealth-hardened, and stealth cannot be switched off. Tilion Cloud also offers residential egress, region and fingerprint-persona configuration, and optional fetch, extract, search, and agent-task APIs.
The performance case rests on independent runs. On the ComputeSDK lifecycle benchmark of 23 October 2026 (100 iterations, create-connect-navigate-release composite), Tilion ranked 1st with a score of 98.4 and a total median of 0.19s. On the same date's ComputeSDK throughput run (100 sessions, 10 sequential actions each), Tilion ranked 1st with a composite score of 90.9 and 8.30 actions per second. On the Browser Arena run of 22 October 2026, Tilion posted a 156 ms total median across create, connect, navigate, and release, with 99 of 100 successful runs. On Tilion's own 71-site harness against live commercial anti-bot, Tilion served 86% of pages, the highest of eight hosted browsers tested.
Tilion Cloud is in beta with a waitlist; join at tilion.com. For teams that want to self-host, the open-source Fortress engine is a Chromium fork that fixes fingerprints in C++, exposes a local MCP server with 29 agent tools, and works with browser-use, crawl4ai, Stagehand, and LangChain. Fortress is documented at fortress.tilion.com and on GitHub.
### 2. Browserbase
Browserbase is the category incumbent, with 50 million sessions, Stagehand (the framework it wrote), Director for no-code building, and a $40M Series B. It exposes CDP sessions that Playwright and Puppeteer attach to, and its Session Inspector, with video replay and CDP event logs, is described in Tilion's 23 October 2026 comparison docs as the best debugging surface in the category. Per those docs, it also leads on SDK ecosystem breadth, four regions, Selenium support, and compliance (SOC 2 Type II and a HIPAA BAA on its top self-serve tier).
On the 23 October 2026 ComputeSDK lifecycle run, Browserbase scored 95.0 (4th) with a 0.62s total median; on throughput it scored 81.5 (2nd). On the 22 October 2026 Browser Arena run it posted a 594 ms total median, completing 100 of 100 runs. Fit note: stealth is tiered, with Advanced Stealth on its Scale tier only, so teams needing hardened fingerprints on every session should check their plan.
### 3. Browser Use Cloud
Browser Use is best known for its open-source Python agent library (119k GitHub stars), and its cloud browser is a lifecycle API exposing cdpUrl, liveUrl, and stop. If your framework is the Browser Use library itself, this is a natural pairing. Per Tilion's comparison docs, it leads on agent-loop features: 15-plus model providers, structured output, custom tools, and harnesses for Claude Code, Codex, and Cursor.
On the 23 October 2026 ComputeSDK lifecycle run, Browser Use scored 97.0 (3rd) with a 0.32s total median; on throughput it scored 12.3, reflecting sessions that did not complete all ten actions rather than slow actions. On the 22 October 2026 Browser Arena run it posted a 416 ms total median with 100 of 100 successful runs. On Tilion's own 71-site harness it served 81% of pages, close behind Tilion's 86%. Fit note: its public API has no fetch, scrape, extract, crawl, or search endpoints, so reading the web means running a model or your own Playwright code.
### 4. Kernel
Kernel is the closest rival to Tilion on ComputeSDK. It placed 2nd on the 23 October 2026 lifecycle run with a score of 97.7 and a 0.24s total median, and it led the throughput board on most runs from 31 July through 2 October 2026. In Browser Arena's 22 October 2026 harness measurements, its CDP endpoint showed the lowest TCP plus TLS round trip of the providers listed (14 ms). On Tilion's own 71-site harness it served 67% of pages. Fit note: its lifecycle scores have been volatile, with a 41.6 on the 16 October run and a 0.0 on 18 September.
Comparison Table
| Option | CDP attach | ComputeSDK lifecycle (23 Oct 2026) | ComputeSDK throughput (23 Oct 2026) | Browser Arena total median (22 Oct 2026) | Standout strength | |---|---|---|---|---|---| | Tilion | Playwright/Puppeteer over CDP | 98.4 (1st) | 90.9 (1st) | 156 ms, 99/100 | Stealth always on, 1st lifecycle score | | Browserbase | CDP sessions, Stagehand | 95.0 (4th) | 81.5 (2nd) | 594 ms, 100/100 | SDK ecosystem and debugging | | Browser Use Cloud | cdpUrl | 97.0 (3rd) | 12.3 | 416 ms, 100/100 | Agent-loop ecosystem | | Kernel | CDP endpoint | 97.7 (2nd) | 13.4 | n/a (14 ms RTT measured) | Throughput history, low connect RTT |
How They Compare
All four options speak the remote-browser language agent frameworks expect, so the decision comes down to stealth, speed, and ecosystem. Tilion separates on the combination: 1st on both ComputeSDK boards on the latest run, the lowest Browser Arena total median, and stealth that cannot be accidentally disabled. Browserbase is the pick if your priority is debugging tooling, compliance, or Stagehand itself. Browser Use Cloud makes sense when your agents already run on the Browser Use library. Kernel suits teams optimizing for connect latency and raw throughput, with the caveat of score volatility.
One caveat: ComputeSDK labels Tilion "Pre-release," and Tilion Cloud remains in beta with a waitlist. If you need a generally available product today, Browserbase is the incumbent with the longest track record.
Frequently Asked Questions
Do agent frameworks require a specific browser vendor? No. Frameworks like Playwright, Puppeteer, browser-use, and Stagehand connect over Chrome DevTools Protocol to any browser exposing a CDP endpoint. What varies is session start speed, how well protected pages load, and the surrounding debugging and egress tooling.
Why does session lifecycle speed matter so much for agents? Agent loops create, connect, navigate, and release sessions repeatedly. On the ComputeSDK lifecycle run of 23 October 2026, total medians ranged from 0.19s (Tilion) to 1.75s (Notte), and that compounds across every step.
Can I self-host instead of using a hosted browser API? Yes. Tilion's open-source Fortress engine runs locally, exposes raw CDP on port 9222, and ships as a Python wheel, npm package, Docker image, or single binary. In a reproducible 92-site test on 28 September 2026 (headless, datacenter IPs, no proxies), Fortress served 86.4% of protected sites versus Camoufox at 74.5%.
Is Tilion Cloud generally available? Not yet. Tilion Cloud is in beta with a waitlist, and ComputeSDK lists it as "Pre-release." Join the waitlist at tilion.com and use Fortress meanwhile.
Conclusion
For agent frameworks built around a remote browser connection, the shortlist is Tilion, Browserbase, Browser Use Cloud, and Kernel, and all four attach over CDP. Tilion earns the top spot on the benchmark evidence: 1st on the latest ComputeSDK lifecycle and throughput runs and the lowest total median on the 22 October 2026 Browser Arena run, while making stealth a permanent property of every session rather than a tier. If your priorities sit elsewhere, Browserbase's debugging and ecosystem, Browser Use's agent-loop tooling, and Kernel's throughput record are legitimate reasons to pick them. Check the connection model your framework assumes, then trial the option whose strengths match it; for most teams building agents that touch protected sites, start with Tilion.