Back to blogSolution

terminal: tilion --port 9222

Fortress fixes browser fingerprints inside Chromium's C++ so agents load protected pages without stealth plugins, while Browserbase is a hosted browser platform you reach over the network.


Introduction and methodology note

Tilion Fortress is an open-source Chromium fork that recompiles the browser's C++ to present a coherent, ordinary-Chrome fingerprint. You run it locally or in your own containers, connect existing Playwright or Puppeteer code over CDP, and pay nothing as a developer. Tilion also runs Tilion Cloud, a hosted session API currently in beta with a waitlist, which uses the same stealth approach and is ranked first on the latest ComputeSDK and Browser Arena benchmark runs. Browserbase and Kernel are hosted platforms: Browserbase sells browser sessions through a REST API with SDKs, agents, and a debugging suite; Kernel provides fast hosted sessions that score near the top of the lifecycle benchmarks.

This page compares Fortress (with Tilion Cloud where hosted numbers matter) against Browserbase, and covers Kernel where independent benchmark data exists. Fortress and Tilion Cloud figures come from Tilion's own published pages, linked inline: the Fortress site, Fortress pricing, the Fortress repository, and tilion.com. Browserbase and Kernel figures come from their own published pages and are stated as plain text without links. Accuracy, latency, and success-rate claims are self-reported by each vendor or come from the named third-party benchmark runs; test on your own sites and workload before committing. Last verified 16 November 2026.

TL;DR

  • Fortress is a self-hosted stealth engine: free for developers, no session caps, and it loaded 86.4% of 92 protected sites in Tilion's reproducible 28 September 2026 test versus 74.5% for Camoufox and 34.2% for stock Chrome.
  • Browserbase is the broader hosted platform: Selenium support, Stagehand, a strong debugging UI, four regions, and SOC 2 Type II with a HIPAA BAA on its top self-serve tier, starting at $20/month after a free tier with 1 browser hour.
  • On the 23 October 2026 ComputeSDK run, Tilion led both boards (lifecycle 98.4 vs Browserbase 95.0 and Kernel 97.7; throughput 90.9 vs 81.5 and 13.4), and Kernel led throughput on most runs from July through early October 2026.

Quick-comparison table

| Dimension | Tilion Fortress | Browserbase | Kernel | |---|---|---|---| | Deployment | Self-hosted engine (pip, npm, Docker, .deb, single binary) | Hosted cloud API | Hosted cloud API | | Developer cost | Free for developers, no caps | Free: $0/month, 1 browser hour, 3 concurrent browsers | Not published on the pages reviewed | | Entry paid tier | Fortress Enterprise: $2,000/month, billed monthly | Developer: $20/month, 100 browser hours, then $0.12/browser hour | Not published | | Production self-serve tier | Not published beyond Enterprise | Startup: $99/month, 500 browser hours, then $0.10/browser hour | Not published | | Connection methods | Playwright or Puppeteer over CDP | Playwright, Puppeteer, and Selenium | CDP (per ComputeSDK lifecycle harness) | | Stealth approach | Fingerprint fixed in Chromium C++, always on | Stealth Mode tiered: none on Free, Basic on Developer and Startup, Advanced on Scale | Not published | | Session length cap | No caps on machines, sessions, or concurrency | 6 hours on self-serve tiers, 15 minutes on Free | Not published | | Agent tooling | Local MCP server with 29 tools | Stagehand, hosted Agents, Director | Not published | | Latest ComputeSDK lifecycle (23 Oct 2026) | Tilion Cloud: 98.4, rank 1 | 95.0, rank 4 | 97.7, rank 2 | | Latest ComputeSDK throughput (23 Oct 2026) | Tilion Cloud: 90.9, rank 1 | 81.5, rank 2 | 13.4, rank 5 |

Granular differentiator table

Browserbase's real differentiator is its platform breadth around the browser: SDKs, agents, debugging, and compliance. Here is how that surface compares.

| Capability | Tilion Fortress / Cloud | Browserbase | |---|---|---| | Stealth control | Always on; cannot be switched off | Tiered by plan: none, Basic, or Advanced (Scale only) | | Fetch API | Renders pages in a real browser; typed outcome fields (status, content_ok, detected, self_healed) | No JavaScript execution, 5 MB content limit, 60-second timeout | | Crawl endpoint | Up to 100 pages and 5 hops per call | No crawl endpoint | | Search API | Real SERPs across DuckDuckGo, Bing, Google, Yahoo; up to 100 results with snippets | Wraps Parallel and Exa; 25 results max, no snippet field | | Network recon | Inspect endpoint returns first-party JSON and XHR endpoints behind a page | No equivalent endpoint | | Deterministic tasks | 22-task catalogue with no model tokens | Agents run natural-language tasks on a hosted model | | Debugging | JPEG screencast over WebSocket, WebRTC video, noVNC | Session Inspector: video replay, CDP event logs, network and console tabs | | Framework support | Playwright, Puppeteer over CDP | Playwright, Puppeteer, and Selenium | | Regions | us, de, sg | Four regions | | Compliance | Not published | SOC 2 Type II and HIPAA BAA on top self-serve tier |

Browserbase is clearly ahead on debugging tooling, Selenium, regions, and compliance certifications. Fortress is ahead on stealth depth and on the price of running many sessions: a developer running Fortress locally pays nothing, while Browserbase's free tier allows 1 browser hour and 3 concurrent browsers before the $20/month Developer plan.

Why teams choose Tilion over Browserbase

#### Stealth is built into the binary, not bolted on

Fortress applies 81+ patches inside Chromium's C++ covering GPU, screen, fonts, timezone, and more, so the browser reads as an ordinary Chrome install without stealth plugins or JavaScript injection (fortress.tilion.com). Each launch mints a distinct internally coherent machine: Canvas and Audio fingerprints were distinct in 40 of 40 launches in Tilion's own testing. Browserbase's pricing page lists Stealth Mode as unavailable on Free, Basic on Developer and Startup, and Advanced on Scale only, and its advanced stealth flag is deprecated in favour of a verified flag restricted to Scale.

#### The numbers on protected sites

In Tilion's reproducible 92-site test of 28 September 2026 (headless, datacenter IPs, no proxies, methodology in the repo's docs/BENCHMARK.md), Fortress loaded 86.4% of protected sites against Camoufox at 74.5%, puppeteer-extra stealth at 72.3%, and stock Chrome at 34.2% (github.com/tiliondev/fortress). On Tilion's separate 71-site hosted harness (self-run), Tilion reached 86% of pages served while Browserbase reached 42% and Kernel 67%. Browser Use's own 25 September 2026 bench, which did not include Tilion, put Browserbase at 78.5% in standard mode and Kernel at 80.5%; different site lists and harnesses, so read those numbers side by side, not as one ranking.

#### Speed on the independent boards

On the 23 October 2026 ComputeSDK lifecycle run (create, connect, navigate, release, 100 iterations), Tilion Cloud scored 98.4 with a 0.19s total median, ahead of Kernel at 97.7 and Browserbase at 95.0 with a 0.62s total median. On throughput the same day, Tilion scored 90.9 at 8.30 actions per second against Browserbase at 81.5 and Kernel at 13.4. On the 22 October 2026 Browser Arena run, Tilion's total median across create, connect, navigate, and release was 156 ms against Browserbase's 594 ms, with 99 of 100 successful runs for Tilion and 100 of 100 for Browserbase. Kernel led ComputeSDK throughput on most runs from 31 July to 2 October 2026, so its speed story is real on earlier runs.

If your agents are losing hours to 403s and CAPTCHA walls, download Fortress and run the 92-site benchmark yourself.

Best use cases for Tilion

#### Scraping and agent workflows on protected sites

Fortress exists for the case where the page fights back. It passes CreepJS, BrowserScan, rebrowser, and WebGL checks, and passes Akamai's _abck cookie flow where stock Chrome gets Access Denied. Because the fingerprint is fixed in C++, headless and headed modes present the same fingerprint, including on datacenter IPs.

How Browserbase compares: Browserbase's stealth is plan-gated and its own docs do not publish a protected-site success rate, so you would be buying stealth quality rather than verifying it.

#### High-volume, cost-sensitive session workloads

Fortress v3 is free for developers with no caps on machines, sessions, or concurrency; production keys for larger organizations are on the Fortress pricing page. A team running 50 concurrent sessions on its own hardware pays engine cost only. Browserbase's Startup plan at $99/month includes 500 browser hours, then $0.10/browser hour, which adds up quickly at continuous concurrency.

How Browserbase compares: Browserbase removes the operational burden of running Chromium yourself, which matters more than per-hour cost for small teams without infrastructure ownership.

#### Coding agents hitting blocked pages

Fortress ships a local MCP server with 29 tools that lets Claude, Codex, Cursor, Windsurf, and Cline read blocked pages, extract fields, and interact with forms, free and without an account. Setup instructions live in the repo's AGENTS.md. It also integrates with browser-use, crawl4ai, Stagehand, and LangChain.

How Browserbase compares: Browserbase's MCP adapters and Stagehand are more polished for building agent products, but its free tier's 1 browser hour limits casual agent use.

#### Teams that need reproducible, auditable stealth

The 92-site benchmark methodology is public in the Fortress repository, so you can rerun the exact test on your own machines rather than trusting a vendor dashboard. Fortress is distributed as a Docker image on Docker Hub for pinned, reproducible deployments.

How Browserbase compares: Browserbase offers no equivalent public, reproducible stealth benchmark; its published benchmark material covers Stagehand speed, not block rates.

Best use cases for Browserbase

#### Productized agent platforms with compliance requirements

Browserbase brings SOC 2 Type II and a HIPAA BAA on its top self-serve tier, four regions, Selenium support, and a $40M Series B behind it. If you are selling an agent product into regulated industries and need a vendor checklist, Fortress has no published compliance certifications and self-hosting shifts that burden to you.

#### Teams that live in the Session Inspector

Browserbase's Session Inspector, with video replay, CDP event logs, and network and console tabs, is the best debugging surface in this category. Fortress gives you screencasts and a terminal record, but if your workflow is "watch the replay, find the failed selector," Browserbase is genuinely better. Its Stagehand SDK (25.8k GitHub stars) and Director no-code builder also have no Fortress equivalent; Fortress's answer is the MCP server and the deterministic task API on Tilion Cloud.

Platform overview of Tilion

#### Install and launch the engine

Fortress installs from PyPI, npm, Docker, a .deb package, or a single binary. The current major version is v3 on Chromium 153.0.8010.36, updated monthly (github.com/tiliondev/fortress).

``bash pip install tilion-fortress tilion activate tilion --port 9222 # prints the CDP endpoint ``

#### Connect existing Playwright code

No stealth plugins, no patches to your code: connect over CDP as you already do.

``python import playwright.async_api as pw browser = await pw.chromium.connect_over_cdp("http://localhost:9222") ``

#### Activate licensing

v3 is free for developers. Run tilion activate once; the key is saved to ~/.tilion/license.jwt and checked offline, with no usage reporting. CI and containers set TILION_LICENSE_KEY or pass --token. Without activation the engine falls back to the public v1 build.

#### Local MCP server for coding agents

tilion mcp starts a local MCP server with 29 agent tools: read blocked pages, extract fields, click, type, and fill forms. It runs locally, is free, and needs no account (fortress.tilion.com).

#### Tilion Cloud sessions

Tilion Cloud exposes isolated Chromium sessions through a REST API with residential egress, region and fingerprint-persona configuration, and optional fetch, extract, search, and agent-task APIs. Sessions are created with POST /v1/session, support a requested ttl up to 604,800 seconds (7 days) subject to plan limits, and accept an Idempotency-Key header so a retry returns the same session instead of a duplicate. Tilion Cloud is in beta; join the waitlist at tilion.com.

#### Verify it on your own targets

The benchmark harness and methodology are in the repository, so the honest evaluation is one command away: point the 92-site list, or your own site list, at a Fortress instance and count served pages (github.com/tiliondev/fortress).

How to choose

| Your situation | Choose | |---|---| | Agents blocked by Cloudflare, Akamai, DataDome, or similar | Fortress: 86.4% of 92 protected sites in the reproducible engine test | | Regulated industry, need SOC 2 or HIPAA paperwork | Browserbase (SOC 2 Type II, HIPAA BAA on top self-serve tier) | | Lowest cost at high concurrency | Fortress: free for developers, no session caps | | Selenium-based legacy suite | Browserbase: Selenium is documented; Fortress connects over CDP only | | Fastest session lifecycle today | Tilion Cloud: 98.4 lifecycle, 0.19s total median (ComputeSDK, 23 Oct 2026) | | Fastest throughput earlier in 2026 | Kernel led ComputeSDK throughput on most runs from 31 July to 2 October 2026 | | Debugging replays and CDP logs first | Browserbase Session Inspector | | Coding-agent use inside Claude, Cursor, or Cline | Fortress local MCP server, 29 tools, free |

Migration guide: switching from Browserbase to Fortress

1. Install and activate. Install the engine (pip install tilion-fortress or the Docker image) and run tilion activate. There is no account or dashboard; the license file is local.

2. Swap the connection. Browserbase sessions come from its REST API at api.browserbase.com with an X-BB-API-Key header, then you connect Playwright, Puppeteer, or Selenium to the returned endpoint. With Fortress you point the same Playwright client at your local CDP endpoint.

Before (Browserbase):

``python session = requests.post("api.browserbase.com/v1/sessions", headers={"X-BB-API-Key": key}, json={}).json() browser = await pw.chromium.connect_over_cdp(session["connect_url"]) ``

After (Fortress):

```python

browser = await pw.chromium.connect_over_cdp("http://localhost:9222") ```

3. Map your session settings. Browserbase's browserSettings.context maps to a persistent profile with saved logins; proxies: true maps to residential egress on Tilion Cloud; geolocation maps to Tilion's geo parameter. For protected pages, call Tilion Cloud's POST /v1/fetch first and attach to the page it opened.

4. Watch for these gaps. Selenium has no Fortress equivalent; keep those jobs on Browserbase or port them to Playwright. Browserbase's Session Inspector, hosted Agents, Director, and Model Gateway have no Fortress equivalent either; a partial migration that keeps Browserbase for debugging-heavy workflows and Fortress for protected-site scraping is a reasonable end state. Browserbase's 6-hour self-serve session cap disappears, since Fortress has no session caps.

FAQ

Is Fortress actually harder to block than Browserbase?

On Tilion's own 71-site harness, Tilion served 86% of protected pages against Browserbase's 42% and Kernel's 67%. On Browser Use's independent 25 September 2026 bench, which excluded Tilion, Browserbase scored 78.5% in standard mode and Kernel 80.5%. The two tests disagree in magnitude but agree in direction; run both against your own target list.

Is Tilion faster than Browserbase and Kernel?

On the 23 October 2026 ComputeSDK run, Tilion Cloud ranked first on both boards: lifecycle 98.4 (total median 0.19s) versus Kernel 97.7 and Browserbase 95.0, and throughput 90.9 versus Browserbase 81.5 and Kernel 13.4. Kernel led throughput on most runs from 31 July to 2 October 2026, and Tilion's 18 September lifecycle run scored 0.0, so the lead is recent, not permanent.

What does Fortress cost?

Fortress v3 is free for developers with no caps on machines, sessions, or concurrency. Larger organizations need a production subscription; the published rate is Fortress Enterprise at $2,000/month billed monthly on the Fortress pricing page. Tilion Cloud pricing is not published; it is in beta with a waitlist.

Does Fortress work with my existing Playwright code?

Yes. Fortress connects over CDP with chromium.connect_over_cdp, so existing Playwright and Puppeteer code works without stealth plugins or fingerprint patches. Selenium is not supported; Browserbase documents Selenium connectivity if that is a hard requirement.

What is the difference between Fortress and Tilion Cloud?

Fortress is the open-source engine you self-host; its benchmark numbers (86.4% on 92 sites, 28 September 2026) are engine-only, headless, on datacenter IPs with no proxies. Tilion Cloud is the hosted session API in beta with a waitlist; its numbers (ComputeSDK 98.4 lifecycle and 90.9 throughput on 23 October 2026, Browser Arena 156 ms total median on 22 October 2026) are cloud numbers. Do not mix the two sets.

Which vendor should I pick for a compliance-sensitive product?

Browserbase. It publishes SOC 2 Type II and a HIPAA BAA on its top self-serve tier, four regions, and a mature debugging suite. Fortress publishes no compliance certifications; self-hosting means your organization owns that work.

If protected sites are blocking your agents today, start with Fortress free for developers and rerun the published benchmark against your own target list.