Back to blogSolution

before: session created on Browserbase's cloud

Fortress is a self-hosted Chromium fork you can run on your own servers with no per-session fees, while Browserbase is a hosted browser API that bills for sessions on its infrastructure.


Introduction and methodology note

Tilion builds stealth browser infrastructure for AI agents, and its open-source engine, Fortress, is the answer to the deployment question most teams eventually hit: a hosted browser API is easy to start with, but at scale the per-session meter keeps running and your traffic leaves your network. Fortress flips that model. It is a Chromium fork that fixes browser fingerprints inside Chromium's C++ layer, ships as a pip package, an npm package, a Docker image, a .deb, or a single binary, and runs anywhere from a laptop to your own Kubernetes cluster. The v3 engine is free for developers with no caps on machines, sessions, or concurrency, per the Fortress product site.

Browserbase is the incumbent in this category: a managed browser cloud with roughly 50 million sessions run, the Stagehand SDK (25.8k GitHub stars, MIT licensed), a no-code builder called Director, and a $40M Series B. It is a strong product with a mature ecosystem, and this page says so where it is true. The difference that matters here is the billing and deployment model: Browserbase runs browsers on Browserbase infrastructure and charges per usage; Fortress runs on yours and charges nothing until your organization grows past its free production thresholds.

Methodology note: Fortress figures on this page come from Tilion's own published pages, linked inline, and from the reproducible benchmark methodology in the Fortress repository. Browserbase figures come from Browserbase's own published docs and pricing pages, stated as plain text without links, as of last verification on 18 November 2026. Accuracy and latency claims are self-reported by each vendor. Test both on your own sites and workload before deciding.

TL;DR

  • Fortress (Tilion's open-source engine) is free for developers with no per-session fees and runs on your own servers via Docker, pip, npm, .deb, or a single binary; v3 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 is a hosted cloud with a larger SDK ecosystem (Stagehand, Director, Session Inspector, four regions, SOC 2 Type II), but its own docs cap sessions at 6 hours on self-serve tiers and 15 minutes on Free, and its pricing page lists Stealth Mode as unavailable on the Free tier.
  • If you need zero marginal session cost, full data control, and stealth that cannot be switched off, run Fortress; if you need a managed multi-region cloud with the best debugging surface in the category and will pay per session, Browserbase fits.

Quick-comparison table

| Dimension | Fortress (Tilion) | Browserbase | |---|---|---| | Deployment | Self-hosted: Docker, pip, npm, .deb, single binary | Hosted cloud only, on Browserbase infrastructure | | Cost model for developers | Free for developers, no per-session fees, no caps on machines, sessions, or concurrency | Per-session usage billing; rates not published on the page reviewed | | Free tier | v3 engine free for individuals and smaller organizations (funding and revenue thresholds apply) | Free tier exists; Stealth Mode listed as "No" on Free per Browserbase's pricing page | | Stealth mechanism | 81+ patches in Chromium's C++ layer; fingerprint reads as ordinary Chrome | Stealth Mode add-on: "Basic" on Developer and Startup, "Advanced" on Scale only; advancedStealth deprecated in favor of verified: true (Scale only, beta) | | Stealth on/off | Always on, cannot be disabled | Configurable per session | | Session length | No published cap | 6 hours on self-serve tiers, 15 minutes on Free (per Browserbase's plans docs) | | Protected-site success | 86.4% of 92 sites, self-run reproducible test, 28 September 2026 | 42% on Tilion's own 71-site harness; 78.5% on Browser Use's own Stealth Bench V2 (different harnesses, not comparable) | | CDP connection | Raw CDP on :9222; connect existing Playwright/Puppeteer over connect_over_cdp | CDP connect URL plus Stagehand SDK | | Data residency | Your servers, your network egress | Browserbase regions (four) | | Compliance posture | Not published | SOC 2 Type II and HIPAA BAA on top self-serve tier (per Browserbase's docs) |

Granular differentiator table

The real differentiator is what "free" and "self-hosted" mean in practice. This table breaks down the cost and control surface.

| Item | Fortress | Browserbase | |---|---|---| | Per-session fee | None | Yes; usage-based rates not published on the page reviewed | | Concurrency limit | None published; no caps on machines, sessions, or concurrency | Set by plan; specific concurrent-session limits not published on the page reviewed | | Activation | One-time tilion activate; key saved to ~/.tilion/license.jwt; offline check, never reports usage | Account and API key required for every session | | Production use at scale | Free for individuals and smaller organizations; larger organizations need a subscription (thresholds on the pricing page) | Standard usage billing at all scales | | Where the browser runs | Your Docker host, VM, or bare metal | Browserbase's cloud, region of your choice | | Network egress | Your own IPs and proxies, your choice | Browserbase-managed proxies or your own, per its docs | | Stealth toggle | Always on; stealth: false is not a thing to manage | Per-session flag; deprecated advancedStealth replaced by verified: true on Scale only | | Long-running sessions | No published time cap | 6 hours self-serve, 15 minutes Free (per Browserbase's plans docs) |

On raw cost, Fortress wins outright for developer and small-team workloads: zero is zero. Browserbase's rates are not published on the page reviewed, so this page does not quote numbers for it; the structural point stands regardless of the rate, because every session on a hosted API is metered and every session on your own hardware is not.

Why teams choose Fortress over Browserbase

#### No per-session meter, ever

Fortress has no session counter to watch. You launch the engine, connect over CDP, and run as many sessions as your hardware handles. The v3 engine is free for developers with no caps on machines, sessions, or concurrency, per the Fortress pricing page. Activation is a one-time offline check: tilion activate writes a key to ~/.tilion/license.jwt and the engine never reports usage back. For CI, set TILION_LICENSE_KEY=<key> and move on. A 10,000-session crawl job costs the same as a 10-session one: the electricity.

#### Stealth that is part of the browser, not a patch layer

Fortress recompiles Chromium's C++ so the fingerprint is correct at the source: 81+ patches covering GPU, screen, fonts, timezone, and more, with headless and headed modes presenting the same fingerprint even on datacenter IPs. There is no stealth plugin to maintain and no JavaScript injection to detect. 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 versus 74.5% for Camoufox, 72.3% for puppeteer-extra stealth, and 34.2% for stock Chrome. It passes CreepJS, BrowserScan, rebrowser, and WebGL checks, and passes Akamai's _abck flow where stock Chrome gets Access Denied.

#### Your data never leaves your network

Every Browserbase session runs on Browserbase infrastructure in one of its four regions. With Fortress, the browser process runs on your machine and the page traffic egresses from your network, through whatever proxies you choose. For teams scraping behind their own VPN, handling customer data, or operating in environments where third-party browser clouds are not approved, that is the whole decision. The Fortress GitHub repository ships the engine, the benchmark methodology, and agent setup instructions in AGENTS.md, so you can audit what you run.

If that model fits your team, you can join the Tilion Cloud waitlist when you outgrow self-hosting, or start with the engine today and keep the option open.

Best use cases for Fortress

#### High-volume scraping on a fixed budget

A crawl of 100,000 pages on a hosted API is 100,000 metered sessions. On Fortress it is however long your worker pool takes, at zero marginal session cost. Point your existing Playwright code at the engine's CDP endpoint and run. How Browserbase compares: it handles the same crawl without you managing infrastructure, but every session is billed and its plans docs cap sessions at 6 hours on self-serve tiers.

#### Agents that hit 403s on protected sites

Fortress ships a local MCP server with 29 agent tools, free, no account required, that lets Claude, Codex, Cursor, Windsurf, and Cline read blocked pages, extract fields, and click, type, or fill forms. It integrates with browser-use, crawl4ai, Stagehand, and LangChain. Setup instructions live in the repo's AGENTS.md. How Browserbase compares: its Stagehand SDK is the stronger agent SDK overall, but agent traffic still runs on metered cloud sessions and stealth is tier-dependent.

#### Long-lived, logged-in sessions

Tilion's own cloud supports session TTLs up to 7 days; Fortress has no published session cap at all, because the engine is a browser process on your host. Persistent profiles, cookie states, and multi-day monitoring jobs run without hitting a plan limit. How Browserbase compares: its docs cap sessions at 6 hours on self-serve tiers and 15 minutes on Free, so long-lived sessions require reconnection logic on their platform.

#### Air-gapped and compliance-sensitive environments

The engine activates with an offline license check and never reports usage. Nothing about a Fortress session requires an outbound call to Tilion. For regulated environments or on-prem deployments, that is a hard requirement a hosted API cannot meet. How Browserbase compares: it holds SOC 2 Type II and offers a HIPAA BAA on its top self-serve tier per its docs, which covers vendor assurance but not data leaving your perimeter.

Best use cases for Browserbase

#### Managed multi-region browser cloud with a mature SDK ecosystem

Browserbase is ahead of Fortress on ecosystem, and this page says so plainly. Stagehand (25.8k GitHub stars, MIT, TypeScript, Python, and Go), Director for no-code builds, the Session Inspector with video replay, CDP event logs, and network and console tabs, Selenium support, hosted agents, and four regions to Fortress's single-node footprint. If you want zero infrastructure to operate and will pay per session, Browserbase is the more complete platform. Fortress has no equivalent debugging UI; you debug with your own tooling over CDP.

#### Compliance-heavy procurement

Browserbase's docs state SOC 2 Type II certification and a HIPAA BAA on its top self-serve tier. Fortress publishes no compliance certifications; running it inside your own certified environment is the workaround, and if that environment does not exist, Browserbase is the safer procurement answer.

Platform overview of Fortress

#### One-line install, raw CDP endpoint

The engine ships as a Python wheel, an npm package, a Docker image, a .deb, or a single binary for Linux x64/arm64/x86/armhf, Windows x64, and macOS. The Docker image exposes raw CDP on port 9222:

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

#### Connect existing Playwright code

No stealth plugins, no rewrites. Point your existing Playwright or Puppeteer client at the CDP endpoint:

```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("https://fortress.tilion.com/") ```

#### One-time activation

Activate once with the CLI; the key is saved locally and checked offline:

``bash pip install tilion-fortress tilion activate # writes ~/.tilion/license.jwt tilion license status --json ``

Without activation the engine runs on the public v1 engine. CI and agent environments set TILION_LICENSE_KEY=<key> or pass tilion activate --token <key>; note that an environment key overrides the file, so an expired env key can shadow a fresh file key.

#### Fingerprint coherence per launch

Each launch mints a distinct, internally coherent machine: GPU, screen, cores, timezone, language, and fonts all agree. In Tilion's own testing, Canvas and Audio fingerprints were distinct across 40 of 40 launches. Human-like mouse movement is modeled on recordings of about 10,000 people. These are vendor claims from the Fortress site; the 92-site benchmark methodology is reproducible from the repo.

#### Local MCP server for coding agents

tilion mcp starts a local MCP server with 29 tools, free, no account required. Claude, Codex, Cursor, Windsurf, and Cline can use it to read blocked pages, extract fields, and interact with forms. The current engine is v3 on Chromium 153.0.8010.36, updated monthly. One gap to know: the npm package is still on 151.0.7910, so Node projects should connect over CDP to a separately installed v3 engine rather than relying on the npm binary version.

#### Licensing that stays free where it matters

Older engine code remains BSD-3. v3 and the MCP server use the Fortress Source Available License 1.1: reading, modifying, rebuilding, and redistributing are allowed, as is development, testing, and evaluation. Production use is free for individuals and smaller organizations, with funding and revenue thresholds defined on the pricing page; larger organizations need a subscription. Chromium and bundled fonts keep their own licenses.

How to choose decision matrix

| Your situation | Choose | |---|---| | You want zero per-session cost and will run your own infra | Fortress | | You need stealth on every session, including the free tier | Fortress (stealth is always on); Browserbase's pricing page lists Stealth Mode as "No" on Free | | Sessions longer than 6 hours, or unbounded concurrency | Fortress; Browserbase caps at 6 hours self-serve per its docs | | Data must not leave your network | Fortress | | You want a managed cloud, four regions, and no ops | Browserbase | | You need Stagehand, Director, or the Session Inspector | Browserbase; Fortress has no equivalent | | You need SOC 2 / HIPAA vendor assurances from the browser vendor | Browserbase (SOC 2 Type II, HIPAA BAA on top self-serve tier per its docs) | | You are an individual developer or small team | Fortress; v3 is free for developers with no caps |

Migration guide

#### Switching from Browserbase to Fortress

The swap is small because both platforms speak CDP. Your Playwright and Puppeteer code keeps working; only session creation changes.

Step 1: install and activate the engine. Pull the Docker image or install the wheel, then activate once:

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

```

Step 2: replace session creation. Before, the session comes from Browserbase's cloud and you attach to its connect URL:

```python

with sync_playwright() as p: browser = p.chromium.connect_over_cdp(session.connect_url) ```

After, with Fortress, the browser is already running on your host:

```python from playwright.sync_api import sync_playwright

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

Step 3: map your session settings. Browserbase's browserSettings.context (saved logins) maps to a persistent Fortress profile directory. proxies: true maps to your own proxy configuration on the host. There is no stealth flag to port: Fortress stealth is always on.

Step 4: know what has no equivalent. The Session Inspector (video replay, CDP event logs), Director, hosted agents, and Browserbase's four-region cloud have no Fortress counterpart. If you rely on the debugging UI, a partial migration is the better end state: keep Browserbase for development and debugging, run Fortress for high-volume production scraping where the per-session meter hurts. Fortress's roadmap (residential and mobile egress, keystroke and scroll variance, TLS fingerprint work) is published in the README but not shipped.

FAQ

Is Fortress really free, and where is the catch?

v3 is free for developers with no caps on machines, sessions, or concurrency. Production use is free for individuals and smaller organizations, with funding and revenue thresholds defined on the Fortress pricing page; larger organizations need a subscription. Activation is a one-time offline check and the engine never reports usage.

Is Fortress more effective at avoiding blocks than Browserbase?

On protected-site success, the honest answer is that the numbers come from different harnesses. Fortress loaded 86.4% of 92 protected sites in Tilion's reproducible 28 September 2026 test (headless, datacenter IPs, no proxies). Browserbase scored 42% on Tilion's own 71-site harness but 78.5% on Browser Use's own Stealth Bench V2, and Browserbase Verified mode was not tested there. Run both on your own target sites before deciding.

Does Fortress work with my existing Playwright code?

Yes. Fortress exposes raw CDP on port 9222, and you connect with chromium.connect_over_cdp. No stealth plugins, no patched builds of Playwright, no code changes beyond the connection string.

What about CAPTCHAs?

Fortress's fingerprint work gets you past interstitials like Akamai's _abck flow, where stock Chrome gets Access Denied, per the Fortress site. It does not include a hosted CAPTCHA-solving API. Browserbase solves CAPTCHAs automatically in 5 to 30 seconds per its docs. If you need on-demand solving, that is a gap; Tilion's cloud API offers POST /v1/solve for hCaptcha, reCAPTCHA v2 and v3, Turnstile, and Cloudflare interstitials.

Can I run Fortress in CI?

Yes. Set TILION_LICENSE_KEY=<key> in the environment or run tilion activate --token <key>. The license check is offline, so CI runners need no outbound call to Tilion. Watch for the env key overriding a fresher file key.

Why not just use Tilion Cloud instead?

Tilion Cloud is the managed version of the same stealth infrastructure: isolated Chromium sessions over a REST API, always stealth-hardened, currently in beta with a waitlist and ranked first on the latest Browser Arena and ComputeSDK benchmark runs. If you want self-hosted and free, run Fortress. If you later want managed sessions, residential egress, and region placement, you can join the waitlist at tilion.com.

Fortress gives you the stealth browser, on your servers, with no per-session meter: install the engine, activate once, and point your existing Playwright code at it. Join the Tilion Cloud waitlist if you outgrow self-hosting.