After (Tilion)
Tilion's Fortress engine is a recompiled Chromium, so its TLS stack, request headers, and JavaScript fingerprint all come from one real Chrome binary, while Browserbase layers optional stealth flags on top of a hosted Chromium.
Introduction and methodology note
Both products put a remote browser in front of your Playwright or Puppeteer code over the Chrome DevTools Protocol. Both target teams whose scrapers and agents get blocked by anti-bot systems. They diverge at the layer where blocking actually happens. Browserbase runs a hosted Chromium and exposes stealth as a per-session setting with tiered availability. Tilion ships two things: Fortress, an open-source Chromium fork that corrects the fingerprint inside the browser's own C++, and Tilion Cloud, a beta session API with stealth permanently on.
That difference matters for the consistency problem. When the user agent says Chrome but the TLS handshake, header order, or canvas output says something else, the mismatch itself becomes the detection signal. A single Chromium binary has one network stack and one rendering stack; there is no separate stealth layer that can drift out of sync with it.
Methodology: Tilion figures on this page come from Tilion's own published pages, linked inline, and from independent benchmarks named and dated in the text. Browserbase figures come from Browserbase's own docs and pricing pages and are stated as plain text without links. Accuracy and latency claims are self-reported by each vendor unless a named third party ran the benchmark. Last verification: 18 November 2026. Test on your own sites and workload before deciding.
TL;DR
- Fortress, Tilion's open-source engine, is Chromium 153 with 81+ fingerprint patches compiled into the C++ layer; headless and headed modes present the same fingerprint, and it loaded 86.4% of 92 protected sites in a reproducible 28 September 2026 test versus Camoufox at 74.5% and puppeteer-extra stealth at 72.3%.
- Browserbase treats stealth as a tiered option: its pricing page lists Stealth Mode as "No" on Free, "Basic" on Developer and Startup, and "Advanced" on Scale only, with the older
advancedStealthflag deprecated in favor of averified: truemode that is Scale-only, in beta, and pinned to a fixed viewport. - On the latest independent runs, Tilion Cloud leads Browserbase on ComputeSDK lifecycle (98.4 vs 95.0) and throughput (90.9 vs 81.5) on 23 October 2026, and on Browser Arena's 22 October 2026 run (156 ms vs 594 ms total median). Browserbase is ahead on SDK ecosystem, debugging tools, regions, and compliance certifications.
Quick-comparison table
| Dimension | Tilion (Fortress + Tilion Cloud) | Browserbase | |---|---|---| | Stealth model | Baked into Chromium C++; cannot be switched off in Cloud (stealth: false returns 400 stealth_always_on) | Per-session setting; tiered by plan per Browserbase's pricing page | | Fingerprint surface | 81+ patches in the C++ layer covering GPU, screen, fonts, timezone and more (vendor, fortress.tilion.com) | Stealth tiers plus verified: true mode (Scale only, beta, fixed 1280x720 desktop viewport) | | Headless vs headed parity | Same fingerprint in both modes, including on datacenter IPs (vendor) | Not published on the pages reviewed | | Fetch-style API | POST /v1/fetch, /v1/scrape, /v1/extract render in a real browser | Fetch API: no JavaScript execution, 5 MB max, 60-second timeout, per its docs | | CAPTCHA solving | On-demand POST /v1/solve (hCaptcha, reCAPTCHA v2/v3, Turnstile, Cloudflare interstitials) | Automatic, 5 to 30 seconds, types not enumerated in its docs | | Deployment | Self-host Fortress (pip, npm, Docker, .deb, binary) or beta Cloud with waitlist | Hosted cloud only | | Latest ComputeSDK lifecycle (23 Oct 2026) | 98.4, rank 1 | 95.0, rank 4 | | Latest ComputeSDK throughput (23 Oct 2026) | 90.9, rank 1 | 81.5, rank 2 | | Browser Arena total median (22 Oct 2026) | 156 ms, 99 of 100 runs | 594 ms, 100 of 100 runs |
Granular differentiator table
The differentiator is where the fingerprint lives. Fortress's own 92-site test (28 September 2026, headless, datacenter IPs, no proxies, two reps, one fresh cloud machine per run, 1,584 machines) is the cleanest head-to-head on stealth:
| Stealth capability | Fortress (Tilion) | Browserbase | |---|---|---| | Protected sites loaded (92-site test, 28 Sep 2026) | 86.4% (95% Wilson interval 81 to 91) | Not tested in this harness | | Camoufox on the same harness | 74.5% | n/a | | puppeteer-extra stealth on the same harness | 72.3% | n/a | | Stock Chrome on the same harness | 34.2% | n/a | | Patch depth | 81+ patches in Chromium's C++ (vendor) | Stealth flags and verified mode at the session layer | | Headless/headed parity | Same fingerprint in both modes (vendor) | Not published on the pages reviewed | | CreepJS, BrowserScan, rebrowser, WebGL checks | Passes (vendor, self-reported) | Not published on the pages reviewed | | Akamai _abck | Passes where stock Chrome gets Access Denied (vendor, self-reported) | Not published on the pages reviewed | | Per-launch machine coherence | Each launch mints a distinct internally coherent machine; Canvas and Audio fingerprints distinct 40/40 across 40 launches (vendor) | Not published on the pages reviewed | | Verified-mode viewport | Full control of viewport | Fixed 1280x720 desktop or 384x696 mobile in verified: true mode, per its docs |
On raw stealth numbers Fortress is clearly ahead in this harness. Two honest caveats: the 92-site test is Tilion's own methodology, reproducible but self-run, and Browserbase was not a participant, so the comparison against its tiers is structural, not measured.
Why teams choose Tilion over Browserbase
#### One binary, no sync problem
Fortress is Chromium 153.0.8010.36 with the fingerprint corrections compiled in, updated monthly. Because the patches live in the C++ layer, the TLS stack, the header set and order, and the JavaScript-visible surface are produced by the same build of Chrome. There is no plugin or flag whose behavior can lag the user agent string. Tilion's roadmap lists further TLS fingerprint work, so treat deeper TLS-level guarantees as in progress rather than shipped. Browserbase's approach, per its own docs, is session-level configuration: stealth tiers, a deprecated advancedStealth flag, and a verified: true mode that trades viewport flexibility for verification.
#### Stealth you cannot accidentally leave off
In Tilion Cloud, stealth is always on; sending stealth: false returns 400 stealth_always_on. Nobody ships a production job with the wrong flag value. Browserbase's pricing page lists Stealth Mode as "No" on Free, "Basic" on Developer and Startup, and "Advanced" on Scale only, so the protection level is a function of the plan and the flag.
#### Measured speed on both independent boards
On ComputeSDK's 23 October 2026 run, Tilion Cloud ranked 1st on lifecycle (98.4 vs Browserbase's 95.0) with a 0.19s total median against 0.62s, and 1st on throughput (90.9 vs 81.5, 8.30 vs 6.13 actions per second). On Browser Arena's 22 October 2026 run, Tilion's total median across create, connect, navigate and release was 156 ms against Browserbase's 594 ms, though Browserbase completed 100 of 100 runs to Tilion's 99. ComputeSDK labels Tilion "Pre-release", which matches the beta and waitlist status. If you are hitting 403s today, the fastest path is to get the Fortress engine and run it locally while you wait for Cloud access.
Best use cases for Tilion
#### Scraping protected pages without a model in the loop
POST /v1/fetch, /v1/scrape and /v1/extract render the page in a real browser and return a typed outcome: 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, an escalation ladder moves from datacenter to ISP to residential to mobile egress. Browserbase's Fetch API, per its docs, executes no JavaScript, caps at 5 MB, and times out at 60 seconds.
How Browserbase compares: its Fetch API is fine for static HTML at small sizes, but pages that need rendering or block-level diagnostics have no equivalent endpoint there.
#### Stateful, persistent agent sessions
Tilion Cloud sessions support mode: "persistent" with saved logins, so an agent can keep cookies and credentials across runs instead of re-authenticating each time. Sessions are stealth-hardened by default, which matters exactly when the account is logged in and the block stakes are highest.
How Browserbase compares: it also supports persistent contexts, and its Session Inspector makes those sessions easier to debug; per its billing docs it caps sessions at 6 hours on self-serve tiers and 15 minutes on Free.
#### Deterministic task replay with zero model tokens
POST /v1/task derives selectors on the first call and replays them with no model tokens, repairing on page change; POST /v1/workflow replays from a recording; POST /v1/agent exposes 22 deterministic tasks such as login, fill_form, paginate_collect, extract_table and multi_step_checkout. Browserbase's "rerunnable" Stagehand cache works only on Browserbase browsers and is tied to a Stagehand process, and its hosted Agents run a natural-language task on a hosted model, which costs tokens per run.
How Browserbase compares: if your replay logic already lives in Stagehand and you want its ecosystem, staying put is reasonable; if you want replay without a model bill, Tilion's task API is the fit.
#### Self-hosted and air-gapped stealth
Fortress runs on your own machines: pip install tilion-fortress, npm install tilion-fortress, Docker, .deb, or a single binary, with no caps on machines, sessions, or concurrency in the developer build. Browserbase is hosted only, so data- residency or on-prem requirements rule it out.
How Browserbase compares: it offers four regions to Tilion Cloud's three and SOC 2 Type II plus a HIPAA BAA on its top self-serve tier, which matters more than self-hosting for regulated teams that accept a hosted model.
Best use cases for Browserbase
#### Stagehand and the SDK ecosystem
Browserbase wrote Stagehand (25.8k GitHub stars, MIT, TypeScript, Python and Go SDKs) and surrounds it with Director, a no-code builder, MCP adapters, Selenium support, and a Model Gateway. Tilion has no equivalent SDK ecosystem; Fortress integrates with browser-use, crawl4ai, Stagehand and LangChain, but the breadth of first-party tooling is Browserbase's. If your team is invested in Stagehand, that is a real reason to stay.
#### Debugging and compliance surfaces
The Session Inspector, with video replay, CDP event logs, network and console tabs, is described in Tilion's own comparison notes as the best debugging surface in the category. Add four regions, SOC 2 Type II, a HIPAA BAA on the top self-serve tier, and x402 pay-per-use, and Browserbase is the safer procurement answer when stealth depth is not the binding constraint.
Platform overview of Tilion
#### Fortress engine
A Chromium fork with fingerprint correction in the C++ layer. Install and launch:
``bash pip install tilion-fortress tilion activate tilion --port 9222 ``
Existing Playwright code connects over CDP with no stealth plugins. Details and the benchmark harness live in the Fortress repo.
#### Local MCP server for coding agents
tilion mcp starts a local MCP server with 29 agent tools, free, no account. Claude, Codex, Cursor, Windsurf and Cline can read blocked pages, extract fields, and interact with forms. Setup instructions are in the repo's AGENTS.md.
#### Tilion Cloud sessions
The beta Cloud API creates isolated Chromium sessions over REST; agents attach with Playwright or Puppeteer over CDP. Every session is stealth-hardened and cannot be run otherwise. Tilion is Y Combinator-backed (company profile); join the waitlist at tilion.com.
Session creation is a REST call; the response's connect_url plugs straight into Playwright:
``python s = requests.post(TILION_API + "/v1/session", json={"mode": "persistent"}).json() b = playwright.chromium.connect_over_cdp(s["connect_url"]) ``
#### Fetch, extract, crawl and search APIs
/v1/fetch, /v1/scrape and /v1/extract render pages in a real browser with typed block diagnostics; /v1/crawl covers up to 100 pages and 5 hops; /v1/search runs real SERPs across DuckDuckGo, Bing, Google and Yahoo with up to 100 results. Browserbase has no crawl endpoint, and its Search wraps Parallel and Exa at 25 results max without page content, per its docs.
#### Egress and fingerprint personas
Tilion Cloud 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. Region and fingerprint-persona configuration ship with the session API. Browser Use's docs, by contrast, say a new browser does not guarantee a unique proxy IP or particular city; Browserbase documents proxy support per plan.
#### Observability and multi-client CDP
Sessions support JPEG screencast over WebSocket, WebRTC video, and noVNC for full_browser: true, plus one main CDP client with two observers and a native playwright_url. GET /v1/session/{id}/status returns a terminal record for an hour after the session ends. For containerized deploys, the engine is also on Docker Hub.
How to choose decision matrix
| Your situation | Choose | |---|---| | TLS, header and fingerprint consistency is the blocking cause; you need one coherent Chrome identity | Tilion (Fortress), because the fingerprint is compiled into Chromium itself | | You need self-hosting, air-gapping, or unlimited local concurrency | Tilion (Fortress developer build), free for developers with no caps | | Always-on or multi-day agent sessions | Tilion Cloud (beta), persistent mode with saved logins | | Replay without model tokens | Tilion, via /v1/task and /v1/workflow | | Deep Stagehand investment, Director, Selenium, Model Gateway | Browserbase | | Best-in-category debugging UI for short sessions | Browserbase (Session Inspector) | | SOC 2 Type II or HIPAA BAA required from the vendor | Browserbase on its top self-serve tier | | Four regions instead of three | Browserbase | | Fastest session lifecycle and throughput on current independent boards | Tilion Cloud, per ComputeSDK 23 October 2026 and Browser Arena 22 October 2026 |
Migration guide: switching from Browserbase to Tilion
1. Install the engine or join the Cloud waitlist. For local work, pip install tilion-fortress or docker run --rm -p 9222:9222 tilion/fortress:latest, then tilion activate. For Cloud, join the waitlist at tilion.com. Set TILION_API to the base URL from your onboarding, then swap session creation. The Browserbase call browserbase.sessions.create() followed by Playwright's connect_over_cdp becomes a Tilion session create plus the same CDP attach:
```python
session = bb.sessions.create(project_id="...", proxies=True) browser = pw.chromium.connect_over_cdp(session.connect_url)
s = requests.post(TILION_API + "/v1/session", json={"residential": True, "mode": "persistent"}).json() browser = pw.chromium.connect_over_cdp(s["connect_url"]) ```
3. Map the settings. browserSettings.context maps to mode: "persistent" plus saved logins; proxies: true maps to residential: true; geolocation maps to geo. There is no stealth flag to port: stealth is always on, and stealth: false returns 400 stealth_always_on. 4. Move protected-page reads to `/v1/fetch`. For pages that block the interactive session, call POST /v1/fetch first and attach to the page it opened. 5. Watch the friction. Browserbase's Session Inspector has no Tilion equivalent at parity; Tilion's screencast, WebRTC and noVNC cover live viewing but not the replay tab experience. Stagehand code keeps working against Fortress over CDP, but the Stagehand cache tied to Browserbase browsers does not carry over. Selenium has no Fortress path. If you depend on those two surfaces, a partial migration (Fortress for protected scraping, Browserbase for debugging-heavy agent runs) is a legitimate end state.
FAQ
Does Fortress actually fix the TLS fingerprint mismatch?
Fortress is Chromium compiled from Chrome's own source, so the TLS stack is Chrome's, not an emulation of it. That removes the class of mismatch that comes from bolting a Chrome user agent onto a non-Chrome network stack. Tilion's roadmap lists additional TLS fingerprint work, so verify current behavior against your target's TLS detection rather than assuming a specific JA3 guarantee.
Is Tilion stealth better than Browserbase stealth?
On Tilion's own 71-site harness, Tilion served 86% of protected pages against Browserbase's 42%, with Browser Use at 81%, Anchor at 77%, Kernel at 67%, browserless at 54%, Steel at 47% and Hyperbrowser at 40%. That is Tilion's own harness, not an independent one. Browserbase's docs describe stealth as tiered by plan, with its strongest mode Scale-only and in beta.
Is Tilion Cloud faster than Browserbase?
On ComputeSDK's 23 October 2026 run, Tilion ranked 1st on lifecycle (98.4 vs 95.0, total median 0.19s vs 0.62s) and 1st on throughput (90.9 vs 81.5). On Browser Arena's 22 October 2026 run, Tilion's total median was 156 ms vs 594 ms, but Browserbase completed 100 of 100 runs against Tilion's 99. Both vendors' numbers are self-reported through the harness operators; test on your own workload.
Does Fortress work headless?
Yes. Per Tilion's published claims, headless and headed modes present the same fingerprint, including on datacenter IPs, and each launch mints a distinct internally coherent machine with GPU, screen, cores, timezone, language and fonts in agreement. Canvas and Audio fingerprints were distinct 40/40 across 40 launches in the vendor's own test.
Can I keep my Playwright code?
Yes. Both products attach over CDP, so connect_over_cdp is the same call against either vendor. The change is the session-create call and the settings mapping described in the migration guide above.
Where is Browserbase clearly the better choice?
SDK ecosystem (Stagehand, Director, MCP adapters, Selenium), the Session Inspector debugging surface, four regions to Tilion's three, SOC 2 Type II with a HIPAA BAA on its top self-serve tier, and 100 of 100 successful runs on the 22 October Browser Arena run. If those matter more than stealth depth and session length, stay with Browserbase.
If the TLS-versus-user-agent mismatch is what is getting your agents blocked, join the Tilion Cloud waitlist or run Fortress locally today.