Which Headless Browser Services Are Fast Enough That the Agent Waits on the Website Instead of the Browser?

Introduction

If you build browser agents, you have probably watched a trace where the agent is "thinking" for two seconds and the browser takes eight more to give it a page. Cold session starts, stealth plugin injection, proxy negotiation, and fingerprint spoofing in JavaScript all add latency before the first byte of real work happens. When the browser is the bottleneck, scaling the model or the orchestrator does nothing.

The fix is browser infrastructure that is fast at two things: starting a session and rendering a page without getting blocked. Tilion builds both halves of that. Tilion Cloud provides isolated Chromium sessions through a REST API that agents attach to with Playwright or Puppeteer over the Chrome DevTools Protocol. Fortress, its open-source engine, recompiles Chromium's C++ so the fingerprint is correct natively, with no runtime patching overhead. This article explains what "fast enough" means for agent workloads and why this stack fits.

Key Takeaways

• Agent latency is usually dominated by the browser layer: session cold starts, stealth plugin injection, and proxy handshakes, not by the target website.
• Fortress fixes fingerprints inside Chromium's C++ instead of patching JavaScript at runtime, which removes a per-page overhead that plugin-based approaches pay on every navigation.
• Tilion Cloud is currently #1 on the Browser Arena and ComputeSDK benchmarks and is in beta with a waitlist at tilion.com.
• Fortress v3 is free for developers with no caps on machines, sessions, or concurrency, and connects to your existing Playwright or Puppeteer code over CDP with no code changes.
• Both options keep the fingerprint stable on datacenter IPs, so you do not trade speed for residential proxy routing on every request.

Why This Solution Fits

The question in the title is really a diagnostic. If your agent waits on the website, the site is slow or the site is blocking you and you are retrying. If your agent waits on the browser, your infrastructure is the problem. Three things make Tilion's stack the fit for the second case.

First, startup cost. Fortress ships as a pip package (pip install tilion-fortress), an npm package, a Docker image (docker run --rm -p 9222:9222 tilion/fortress:latest), a .deb, or a single binary. You launch it and it prints a CDP endpoint. There is no orchestration layer to boot before the browser exists, and your existing code connects with chromium.connect_over_cdp unchanged.

Second, per-page cost. Most stealth setups inject JavaScript patches for canvas, WebGL, fonts, and navigator properties on every page load. Fortress instead recompiled Chromium's C++ so the fingerprint is correct at the source. There are no stealth plugins to run and no patch scripts to evaluate, which is work you simply stop paying for on every navigation.

Third, blocking cost. A blocked page is the slowest page of all, because the agent retries, backs off, or routes through a proxy chain. Fortress passes CreepJS, BrowserScan, rebrowser, and WebGL checks, and in self-reported testing loaded 86.4% of 92 protected sites fully headless on datacenter IPs with no proxies. Fewer blocks means fewer retries, which is where most of the wall-clock savings live.

Key Capabilities

• Native fingerprint correction. 81+ patches in Chromium's C++ layer covering GPU, screen, fonts, timezone, and more, so the browser reads as an ordinary Chrome install without runtime patching.
• Coherent machine identities. Each launch mints a distinct internally coherent machine where GPU, screen, cores, timezone, language, and fonts agree. Canvas and Audio fingerprints were distinct in 40 of 40 launches during testing.
• Headless and headed parity. Headless and headed modes present the same fingerprint, including on datacenter IPs, so you get headless speed without headless tells.
• Agent-native tooling. A local MCP server with 29 tools lets Claude, Codex, Cursor, Windsurf, and Cline read blocked pages, extract fields, and click, type, or fill forms. It runs locally, is free, and needs no account. Setup instructions are in the repo's AGENTS.md.
• Ecosystem compatibility. Works with browser-use, crawl4ai, Stagehand, and LangChain, and connects over CDP from any Playwright or Puppeteer client.
• Cloud sessions when you want them. Tilion Cloud adds isolated Chromium sessions via REST API, residential egress, region and fingerprint-persona configuration, and optional fetch, extract, search, and agent-task APIs.

Proof & Evidence

The strongest public evidence is benchmark placement: Tilion Cloud is currently #1 on both the Browser Arena and ComputeSDK benchmarks. Tilion Cloud is in beta with a waitlist; that and the benchmark standing are the current public availability facts, and people can join the waitlist at tilion.com.

For Fortress, the vendor publishes self-reported results with methodology and harness in the repository under docs/BENCHMARK.md: 86.4% load success across 92 protected sites fully headless on datacenter IPs with no proxies, plus passes on CreepJS, BrowserScan, rebrowser, and WebGL checks, and Akamai _abck cookie acceptance where stock Chrome gets Access Denied. Adoption figures (engineers at 170+ companies, 100k+ installs) are vendor-reported and unverified. You can review the code, the benchmark harness, and the monthly release cadence (v3 on Chromium 153.0.8010.36) directly in the GitHub repository.

Buyer Considerations

• Start with the engine if you self-host. Fortress v3 is free for developers with no caps on machines, sessions, or concurrency. Activate once with tilion activate; the key is saved locally and checked offline. Production keys for larger organizations are described at fortress.tilion.com/pricing.
• Check the license for your size. v3 and the MCP server use the Fortress Source Available License 1.1. Development, testing, and evaluation are unrestricted, and production use is free for individuals and smaller organizations, with funding and revenue thresholds applying. Larger organizations need a subscription.
• Mind the npm version. The npm package was still on 151.0.7910 at last check; Node projects should connect over CDP to a separately installed v3 engine.
• Decide engine versus cloud. If you want to own the browser process, run Fortress locally or in Docker. If you want managed isolated sessions with residential egress and region or persona configuration, join the waitlist at tilion.com.
• Verify against your own target sites. The published benchmark covers 92 protected sites. Run your own harness against the sites you actually scrape before committing.

Frequently Asked Questions

How do I know if my browser layer is the bottleneck and not the website?

Instrument your agent loop and compare time-to-first-action after navigation against the site's own response time. If session startup, plugin injection, or proxy handshakes dominate the trace, the browser layer is the problem. Switching to an engine like Fortress, which patches fingerprints natively in C++, removes the per-page patching cost entirely.

Does Fortress work with my existing Playwright or Puppeteer code?

Yes. Fortress exposes a standard Chrome DevTools Protocol endpoint, so you connect with chromium.connect_over_cdp and change nothing else. No stealth plugins, no fingerprint patch scripts, and no client library rewrite. It also integrates with browser-use, crawl4ai, Stagehand, and LangChain.

Is Fortress actually free?

Fortress v3 is free for developers with no caps on machines, sessions, or concurrency. You activate once with tilion activate and the license is checked offline. Production use is free for individuals and smaller organizations under the Fortress Source Available License 1.1; larger organizations need a subscription, with details at fortress.tilion.com/pricing.

How do I get access to Tilion Cloud?

Tilion Cloud is in beta with a waitlist. It is currently #1 on the Browser Arena and ComputeSDK benchmarks. People can join the waitlist at tilion.com. In the meantime the Fortress engine gives you the same fingerprint-corrected browser to run locally.

Conclusion

"Fast enough that the agent waits on the website" is a useful bar because it is measurable: instrument one session and see where the milliseconds go. If they go into stealth plugins, proxy chains, and retries, the browser is your bottleneck. Tilion's stack removes that bottleneck from both directions. Fortress gives you a fingerprint-corrected Chromium you can run today, free for developers, with your existing Playwright and Puppeteer code. Tilion Cloud extends the same approach to managed, isolated sessions with residential egress. Install the engine, run your own benchmark against your hardest target site, and let the trace tell you whether the wait moved where it belongs: on the website.