Back to blogSolution

raw CDP on :9222

Every Tilion session ships with a stealth-hardened fingerprint and a configurable persona, while Browserbase gates its strongest identity features behind its top tier and a deprecated stealth flag.


Introduction and methodology note

Tilion and Browserbase both sell hosted browser sessions that agents connect to over the Chrome DevTools Protocol with Playwright or Puppeteer. They diverge on identity. Tilion Cloud runs isolated Chromium sessions where stealth is always on and cannot be switched off, and it exposes region and fingerprint-persona configuration per session. Browserbase treats stealth as a tiered feature: its pricing page lists Stealth Mode as "No" on Free, "Basic" on Developer and Startup, and "Advanced" on Scale only, with the older advancedStealth flag deprecated in favour of a verified: true flag that is Scale-only and in beta.

This page compares the two on identity, speed, and API surface. Tilion figures come from Tilion's own published pages, linked inline. Browserbase figures are stated as plain text from Browserbase's own docs and pricing pages, per Tilion's 23 October 2026 comparison notes, and are not independently re-verified here. Accuracy, latency, and stealth claims are self-reported by each vendor; test both on your own workload before committing.

TL;DR

  • Tilion's stealth cannot be turned off and every session gets a coherent fingerprint persona; sending stealth: false returns 400 stealth_always_on. Browserbase's stealth is tiered, and its strongest verified mode is Scale-only with a fixed viewport.
  • On the independent ComputeSDK benchmarks of 23 October 2026, Tilion led lifecycle (98.4 vs Browserbase's 95.0) and throughput (90.9 vs 81.5). On Browser Arena's 22 October 2026 run, Tilion's total median was 156 ms against Browserbase's 594 ms.
  • Browserbase is ahead on SDK ecosystem (Stagehand, 25.8k GitHub stars), debugging (Session Inspector), regions (four vs Tilion's three), and compliance (SOC 2 Type II and a HIPAA BAA on its top self-serve tier).

Quick-comparison table

| Dimension | Tilion | Browserbase | |---|---|---| | Stealth mode | Always on, cannot be disabled (stealth: false returns 400 stealth_always_on) | Tiered: "No" on Free, "Basic" on Developer and Startup, "Advanced" on Scale only | | Verified/advanced stealth flag | Not applicable; stealth is default | advancedStealth deprecated in favour of verified: true, Scale only, beta, fixed viewport 1280x720 desktop or 384x696 mobile | | Fingerprint persona per session | Region and fingerprint-persona configuration per session | Not published on the pages reviewed | | Session length cap | ttl up to 604,800 seconds (7 days) | 6 hours on self-serve tiers, 15 minutes on Free | | Fetch API | POST /v1/fetch, /v1/scrape, /v1/extract render in a real browser | Fetch API: no JavaScript execution, 5 MB max, 60-second timeout, no PDF conversion | | Crawl endpoint | POST /v1/crawl, up to 100 pages and 5 hops | None documented | | Search endpoint | POST /v1/search, real SERPs, up to 100 results with snippets | Search wraps Parallel and Exa, 25 results max, no snippet or page-content field | | CAPTCHA solving | On-demand POST /v1/solve (hCaptcha, reCAPTCHA v2/v3, Turnstile, Cloudflare interstitials) | Automatic, 5 to 30 seconds, CAPTCHA types not enumerated in its docs | | ComputeSDK lifecycle, 23 Oct 2026 | 98.4 (1st) | 95.0 (4th) | | ComputeSDK throughput, 23 Oct 2026 | 90.9 (1st) | 81.5 (2nd) | | Browser Arena total median, 22 Oct 2026 | 156 ms (99/100 runs) | 594 ms (100/100 runs) | | Regions | 3 (us, de, sg) | 4 | | Pricing | Beta with waitlist; join at tilion.com | Not published on the pages reviewed for this comparison |

Granular differentiator table

The differentiator that matters for this comparison is per-session browser identity: what each vendor lets you control about how a restored or fresh session looks to a website.

| Identity capability | Tilion | Browserbase | |---|---|---| | Stealth always on | Yes, cannot be disabled | No; tiered by plan | | Fingerprint persona configuration | Per-session region and fingerprint-persona configuration | Not published on the pages reviewed | | Verified mode | Not applicable | verified: true, Scale only, beta, fixed viewport 1280x720 desktop or 384x696 mobile | | Open-source engine with native fingerprint fixes | Fortress, a Chromium fork with 81+ patches in the C++ layer (fortress.tilion.com) | None; Browserbase is a hosted service only | | Distinct fingerprint per launch | Fortress mints a distinct internally-coherent machine per launch (GPU, screen, cores, timezone, language, fonts agree); Canvas and Audio fingerprints were distinct 40/40 across 40 launches | Not published on the pages reviewed | | Headless vs headed fingerprint parity | Fortress presents the same fingerprint headless and headed, including on datacenter IPs | Not published on the pages reviewed | | Proxy escalation on block | Exit escalation ladder (datacenter, ISP, residential, mobile) with self_healed and recovery fields on fetch outcomes | No retry or escalation behaviour documented | | Live IP rotation | rotate-ip over REST on a running session | Not published on the pages reviewed |

Browserbase is ahead in one row that matters to some teams: its Verified mode is a productized, documented identity feature with a fixed viewport, which some compliance-sensitive buyers prefer even at Scale-only pricing. Tilion's answer is that identity is not a flag at all; it is the default.

Why teams choose Tilion over Browserbase

#### Identity is the default, not a tier

Tilion Cloud sessions are always stealth-hardened. There is no plan matrix to reason about and no flag to forget: stealth: false returns 400 stealth_always_on. Browserbase's pricing page lists Stealth Mode as "No" on Free, "Basic" on Developer and Startup, and "Advanced" on Scale only, and its advancedStealth flag is deprecated in favour of verified: true, which is Scale-only, in beta, and locks the viewport to 1280x720 on desktop or 384x696 on mobile. If your fleet of sandboxes needs every session to look like a different real machine, Tilion gives you that on every session, plus per-session fingerprint-persona configuration.

#### Faster on both independent boards

ComputeSDK runs weekly, publicly, on GitHub Actions. On the 23 October 2026 run, Tilion scored 98.4 on lifecycle (create, connect, navigate, release) against Browserbase's 95.0, with a total median of 0.19s against 0.62s. On throughput (100 sessions, 10 sequential actions each), Tilion scored 90.9 with 8.30 actions per second against Browserbase's 81.5 at 6.13. Browser Arena's 22 October 2026 run measured a 156 ms total median for Tilion against 594 ms for Browserbase, though Browserbase completed 100 of 100 runs where Tilion completed 99. ComputeSDK labels Tilion "Pre-release", which matches its beta status.

#### A fetch layer that renders like a real browser

Browserbase's Fetch API does not execute JavaScript, caps at 5 MB, times out at 60 seconds, and does not convert PDFs, per its own docs. Tilion's POST /v1/fetch, /v1/scrape, and /v1/extract render the page in a real browser, and the response tells you what happened: status (ok, blocked, empty, no_results, redirected_off_target, incomplete), content_ok, detected (wall vendor family, category, mechanism), self_healed, and recovery. On a block, Tilion escalates the exit ladder from datacenter through ISP, residential, and mobile. That turns "did the wall get us?" from a guess into a field you can alert on.

If your agents are hitting walls on protected sites today, join the Tilion Cloud waitlist and test the fetch layer on your own targets.

Best use cases for Tilion

#### Sandboxes restored from a shared snapshot

When every restored browser inherits the same fingerprint, sites can link them. Tilion Cloud exposes per-session fingerprint-persona configuration, so each sandbox can present a distinct, internally coherent identity while running from the same image. For teams that want the identity fixed at the engine level rather than the API level, the open-source Fortress engine mints a distinct machine per launch: Canvas and Audio fingerprints were distinct 40/40 across 40 launches in its published test.

How Browserbase compares: Browserbase's docs describe stealth tiers and a verified mode with a fixed viewport, but the pages reviewed for this comparison do not document per-session fingerprint persona configuration.

#### Reading the web without burning model tokens

Tilion's deterministic surface covers fetch, scrape, extract, crawl (up to 100 pages, 5 hops), search (real SERPs across DuckDuckGo, Bing, Google, and Yahoo, up to 100 results), and a 22-task catalogue at POST /v1/agent that runs with no model tokens. POST /v1/task derives selectors on the first call and replays them with zero tokens, repairing on page change.

How Browserbase compares: Browserbase reaches per-step control through CDP or Stagehand, and its Search wraps Parallel and Exa with a 25-result cap and no snippet field. Its Stagehand cache is a genuine strength, but it works on Browserbase browsers only and is tied to a Stagehand process.

#### Long-running and persistent sessions

Tilion sessions accept a ttl up to 604,800 seconds, which is 7 days. Browserbase caps sessions at 6 hours on self-serve tiers and 15 minutes on Free, per its docs. For agents that hold logins across a workday or a week, the cap difference is structural.

How Browserbase compares: Browserbase's persistent context and profiles cover session reuse within its caps, and its Session Inspector is the better debugging surface if replay matters more than duration.

#### Debugging blocks in production

Tilion returns typed fetch outcomes (status, detected, self_healed, recovery), streams a JPEG screencast over WebSocket, offers WebRTC video and noVNC for full_browser: true sessions, and keeps a terminal session record at GET /v1/session/{id}/status for an hour after the session ends. cdp_observe (default true) watches page loads from your own Playwright client for blocks and challenges.

How Browserbase compares: Browserbase's Session Inspector (video replay, CDP event logs, network and console tabs) is, per Tilion's comparison notes, the best debugging surface in the category. If your primary pain is debugging rather than blocking, Browserbase is the fair pick.

Best use cases for Browserbase

#### Teams standardized on Stagehand and hosted agents

Browserbase wrote Stagehand (25.8k GitHub stars, MIT licensed, TypeScript, Python, and Go) and pairs it with Director, a no-code builder, hosted Agents, a Model Gateway, Selenium support, and x402 pay-per-use. Tilion does not sell a general-purpose hosted LLM agent loop or a Stagehand-equivalent SDK ecosystem. If your stack is Stagehand-first, Browserbase is the native home for it.

#### Compliance-heavy procurement

Browserbase holds SOC 2 Type II and offers a HIPAA BAA on its top self-serve tier, and it runs four regions to Tilion's three. Tilion's compliance certifications are not published on the pages reviewed. Regulated industries with HIPAA or multi-region residency requirements should shortlist Browserbase on those grounds.

Platform overview of Tilion

#### Isolated Chromium sessions over CDP

Tilion Cloud creates an isolated Chromium session through a REST API and lets agents attach with Playwright or Puppeteer over Chrome DevTools Protocol. Sessions are always stealth-hardened, and region plus fingerprint-persona configuration is set per session. The company is Y Combinator-backed (Y Combinator).

#### Fortress, the open-source engine

Fortress is a Chromium fork that fixes fingerprints inside Chromium's C++ (81+ patches covering GPU, screen, fonts, timezone, and more), so existing Playwright or Puppeteer code connects over CDP with no stealth plugins or JS patches. It is free for developers with no caps on machines, sessions, or concurrency; activate once with tilion activate. Production keys and terms are at fortress.tilion.com/pricing.

```bash docker run --rm -p 9222:9222 tilion/fortress:latest

```

#### Agent tooling and MCP

Fortress ships a local MCP server with 29 agent tools, free, no account required, usable from Claude, Codex, Cursor, Windsurf, and Cline. Setup instructions live in the repo's AGENTS.md. Fortress also works with browser-use, crawl4ai, Stagehand, and LangChain.

```python from playwright.sync_api import sync_playwright

with sync_playwright() as p: browser = p.chromium.connect_over_cdp("http://localhost:9222") page = browser.new_page() page.goto(target_url) ```

#### Deterministic task APIs

Tilion Cloud exposes /v1/fetch, /v1/scrape, /v1/extract, /v1/crawl, /v1/search, /v1/inspect, /v1/solve, /v1/agent (22 deterministic tasks), /v1/task, /v1/workflow, and /v1/session/{id}/navigate. POST /v1/plan gives a pre-run task estimate, and session creation supports Idempotency-Key for safe retries. Confirm parameters against Tilion's docs before relying on a field.

#### Proxy and egress control

Tilion offers datacenter, ISP, residential, and mobile exits, geo placement by ZIP, city, state, or country, automatic escalation on blocks, and rotate-ip on a live session. Residential egress is also available on Tilion Cloud sessions.

#### Distribution and platforms

Fortress v3 runs on Chromium 153.0.8010.36, updated monthly, and ships as a Python wheel (pip install tilion-fortress), an npm package, a Docker image, a .deb, and a single binary for Linux x64, Windows x64, Linux arm64/x86/armhf, and macOS. Source and benchmark methodology are on GitHub.

How to choose decision matrix

| Your situation | Choose | |---|---| | Every sandbox must look like a different machine, stealth non-negotiable | Tilion (stealth always on, per-session fingerprint personas) | | You need Stagehand, Director, or hosted LLM agents | Browserbase | | Long sessions (days, not hours) | Tilion (ttl up to 7 days vs 6 hours self-serve) | | SOC 2 Type II or a HIPAA BAA is a hard requirement | Browserbase | | Four regions or specific residency | Browserbase (4) over Tilion (3: us, de, sg) | | Fetch, crawl, search, and replay without model tokens | Tilion (/v1/fetch, /v1/crawl, /v1/search, /v1/task) | | Lowest session latency on independent benchmarks | Tilion (156 ms vs 594 ms total median, Browser Arena, 22 Oct 2026) | | Self-hosted, engine-level fingerprint control | Fortress, Tilion's open-source engine | | Best-in-category debugging replay | Browserbase (Session Inspector) |

Migration guide: switching from Browserbase to Tilion

Step 1: get access. Tilion Cloud is in beta with a waitlist; join at tilion.com. Fortress needs no waitlist: install and run tilion activate.

Step 2: swap the session create and connect calls. The change is two lines in Playwright.

Before (Browserbase):

``python bb = Browserbase(api_key=...) session = bb.sessions.create(project_id=...) browser = p.chromium.connect_over_cdp(session.connect_url) ``

After (Tilion):

``python s = requests.post(TILION_SESSION_URL, json={...}).json() browser = p.chromium.connect_over_cdp(s["connect_url"]) ``

Step 3: map your settings. Browserbase browserSettings.context maps to Tilion mode: "persistent" plus saved logins. proxies: true maps to residential: true. geolocation maps to geo. There is no stealth flag to port; Tilion is always stealth-hardened.

Step 4: replace fetch calls. If you used Browserbase's Fetch API, note it does not execute JavaScript and caps at 5 MB. Call POST /v1/fetch first for protected pages and attach to the page it opened.

Step 5: know what has no equivalent. Stagehand, Director, the Session Inspector, Selenium support, hosted Agents, and the HIPAA BAA have no Tilion equivalent today. If Stagehand is central to your stack, a partial migration (Tilion for fetch, crawl, and stealth sessions; Browserbase for Stagehand) is a reasonable end state.

FAQ

Does Tilion let each sandbox have a different fingerprint?

Yes. Tilion Cloud exposes per-session fingerprint-persona configuration alongside region selection, and stealth is always on. At the engine level, Fortress mints a distinct internally-coherent machine per launch; in its published test, Canvas and Audio fingerprints were distinct 40/40 across 40 launches.

Is Tilion faster than Browserbase?

On the 23 October 2026 ComputeSDK run, Tilion scored 98.4 vs 95.0 on lifecycle and 90.9 vs 81.5 on throughput. On Browser Arena's 22 October 2026 run, Tilion's total median was 156 ms vs Browserbase's 594 ms, with Tilion completing 99 of 100 runs and Browserbase 100 of 100. Both benchmarks are independent and self-reported inputs apply; run your own workload.

Can I turn Tilion's stealth off?

No. Sending stealth: false returns 400 stealth_always_on. If you need a plain, non-stealth browser, Tilion is not the right tool for that session.

What does Tilion cost?

Tilion Cloud is in beta with a waitlist, and pricing is not published. Fortress v3 is free for developers with no caps; larger organizations need a subscription for production use, with terms at fortress.tilion.com/pricing.

What does Browserbase do better?

Per Browserbase's own materials: Stagehand and its SDK ecosystem, Director, the Session Inspector debugging surface, four regions to Tilion's three, a Model Gateway, Selenium support, hosted Agents, x402 pay-per-use, and SOC 2 Type II with a HIPAA BAA on its top self-serve tier. Browserbase also completed 100 of 100 Browser Arena runs on 22 October 2026 where Tilion completed 99.

Do I have to rewrite my Playwright code?

No. Both products connect over Chrome DevTools Protocol, so connect_over_cdp keeps working; you change the session-create call and the URL you pass it. Fortress needs no code change at all beyond pointing CDP at port 9222.

If shared fingerprints are linking your sandboxes today, join the Tilion Cloud waitlist and give every session an identity of its own.