Back to blogSolution

After: Fortress

Fortress fixes browser fingerprints inside Chromium's compiled C++ so agents read as ordinary Chrome users, while Camoufox applies its fingerprints at runtime on a Firefox base. That difference is what the numbers below measure.


Introduction and methodology note

Fortress is Tilion's open-source stealth browser engine: a Chromium fork recompiled so that GPU, screen, fonts, timezone, and dozens of other fingerprint surfaces are corrected natively rather than patched from JavaScript. It ships a local MCP server with 29 agent tools, and existing Playwright or Puppeteer code connects over CDP with one line. Camoufox is an open-source stealth browser built on Firefox, aimed at the same problem: scrapers and AI agents getting blocked by bot-detection systems.

Both projects exist because Cloudflare, DataDome, Akamai, and similar vendors fingerprint headless browsers and serve agents a wall. Where they diverge is the browser engine (Chromium vs Firefox), where the fingerprint fix lives (compiled C++ vs runtime injection), and the agent surface around the browser (Fortress ships an MCP server and CLI; Camoufox is a Python library).

Methodology: every Fortress figure on this page comes from Tilion's own published pages and repositories, linked inline at first mention. Camoufox figures come from its own published materials, stated as plain text without links. The headline benchmark (86.4% vs 74.5% pages served) was run by Tilion's team on 28 September 2026 using the harness published in the Fortress repository, so treat it as a vendor-run result and reproduce it against your own target sites before committing. Accuracy and pass-rate claims are self-reported by each vendor.

TL;DR

  • Fortress loaded 86.4% of 92 protected sites in a reproducible headless test on datacenter IPs with no proxies; Camoufox loaded 74.5% in the same run, puppeteer-extra stealth 72.3%, and stock Chrome 34.2%.
  • Fortress works with the Playwright and Puppeteer code you already have over CDP, plus a free local MCP server with 29 tools for Claude, Codex, Cursor, Windsurf, and Cline; Camoufox has no published MCP equivalent.
  • Fortress v3 is free for developers with no caps on machines, sessions, or concurrency; larger organizations need a production subscription.

Quick-comparison table

| Dimension | Tilion Fortress | Camoufox | |---|---|---| | Browser base | Chromium 153.0.8010.36 (v3) | Firefox | | Fingerprint approach | Fixed in Chromium's C++ at compile time | Runtime injection | | 92-site protected test, pages served | 86.4% | 74.5% | | Playwright/Puppeteer compatibility | Connect over CDP, existing code works | Playwright Firefox API | | MCP server for agents | Yes, 29 tools, local, free | Not published | | Headless fingerprint parity | Same fingerprint headless and headed | Not published | | CAPTCHA solving | Passes Akamai _abck; no built-in solver | Not published | | Free for developers | Yes, v3, no caps | Yes, open source | | Production licensing | Source Available License 1.1; subscription for larger orgs | Open source | | Platforms | Linux x64/arm64/x86/armhf, Windows x64, macOS | Linux, Windows, macOS |

Granular differentiator table

The real differentiator is how each engine survives bot detection, so this table sticks to the 28 September 2026 reproducible test from the Fortress repository: headless, datacenter IPs, no proxies, 92 protected sites across Cloudflare, DataDome, Akamai, HUMAN, Kasada, Imperva, AWS WAF, Arkose, and reCAPTCHA, two repetitions, one fresh cloud machine per run, 1,584 machines total.

| Check | Tilion Fortress | Camoufox | |---|---|---| | Pages served, 92 sites | 86.4% (95% Wilson interval 81 to 91) | 74.5% | | CreepJS | Passes | Not published | | BrowserScan | Passes | Not published | | rebrowser checks | Passes | Not published | | WebGL checks | Passes | Not published | | Akamai _abck cookie | Passes where stock Chrome gets Access Denied | Not published | | Canvas fingerprint distinctness | Distinct 40/40 across 40 launches | Not published | | Audio fingerprint distinctness | Distinct 40/40 across 40 launches | Not published | | Fingerprint patches | 81+ in Chromium's C++ layer | Not published | | Human-like mouse movement | Modeled on recordings of about 10,000 people | Not published |

Camoufox is cheaper to adopt if your bar is "free and open source with no license step at all": it has no activation and no production-key conversation. Fortress wins the measured outcome on Tilion's harness by 11.9 percentage points under identical headless, datacenter-IP conditions, and it publishes the methodology so you can rerun it.

Why teams choose Fortress over Camoufox

#### The fingerprint fix survives JavaScript-level probes

Camoufox injects its fingerprint configuration at runtime, which means detection scripts that inspect the browser from the inside are probing a patched environment. Fortress recompiles Chromium so the fingerprint is the environment: 81+ patches in the C++ layer covering GPU, screen, fonts, timezone, and more, per the Fortress product site. Headless and headed modes present the same fingerprint, including on datacenter IPs, which matters when your agent fleet runs in CI.

#### Your existing Playwright and Puppeteer code keeps working

Fortress is a Chromium fork, so the swap is one line: chromium.connect_over_cdp("http://localhost:9222") against a running engine, with no stealth plugins and no JS fingerprint patches to maintain. Camoufox requires driving Playwright's Firefox API instead of Chromium, which means revisiting launch code, extension behavior, and any Chromium-specific assumptions. The Fortress quick start is pip install tilion-fortress, npm install tilion-fortress, or docker run --rm -p 9222:9222 tilion/fortress:latest (Docker image).

#### Agents get a tool surface, not just a browser

Fortress ships a local MCP server with 29 tools, free, no account required, that lets Claude, Codex, Cursor, Windsurf, and Cline read blocked pages, extract fields, and click, type, or fill forms. Setup instructions live in the repo's AGENTS.md. It also integrates with browser-use, crawl4ai, Stagehand, and LangChain. Camoufox publishes no MCP server, so agent frameworks talk to it through plain Playwright calls.

If your agents are currently eating 403s on protected sites, you can get a Fortress production key and test the engine against your own target list before changing any application code.

Best use cases for Fortress

#### Coding agents hitting 403 errors

Run tilion mcp and point Cursor, Claude, or Cline at the local server. The agent gets 29 tools for reading blocked pages and interacting with forms, and the underlying engine passes CreepJS, BrowserScan, rebrowser, and WebGL checks. This is the audience Fortress was built for: developers whose coding agents stall on bot walls.

How Camoufox compares: it can serve the same role through Playwright if your agent framework drives Firefox, but there is no published MCP integration, so the wiring is yours.

#### Scraping protected sites headless at scale

The 92-site test was run exactly the way scrapers run: headless, datacenter IPs, no proxies. Fortress served 86.4% of pages under those conditions, where stock Chrome served 34.2%. Each launch mints a distinct internally coherent machine, with GPU, screen, cores, timezone, language, and fonts agreeing, and Canvas and Audio fingerprints were distinct in 40 of 40 launches.

How Camoufox compares: it is a legitimate choice for the same job and scored 74.5% in the same run, so the gap is real but not a blowout; test both against your specific targets.

#### Travel and rate-comparison agents

Tilion's documented example use case is travel agents comparing fares, rates, and bookings, which means many parallel sessions against sites with aggressive anti-bot. Fortress has no caps on machines, sessions, or concurrency for developers, so a fan-out of 50 sessions is a launch-count problem, not a licensing one.

How Camoufox compares: it imposes no session caps either, so the constraint here is purely the measured block rate on your target sites.

#### Teams that need Chromium behavior

If your target pages depend on Chromium rendering, Widevine, or Chrome-specific APIs, Fortress is the only option of the two; Camoufox is Firefox-based and cannot close that gap.

Best use cases for Camoufox

#### Zero-friction open-source adoption

Camoufox is fully open source with no activation step, no license file, and no production-key conversation. If your organization cannot or will not sign up for a source-available license with revenue thresholds, Camoufox is the simpler procurement, full stop.

#### Firefox-native fingerprint requirements

Some detection setups and some sites behave differently on Firefox, and a Firefox-based fingerprint is a different point in the detection space, not a worse one. If your testing shows Firefox passes where Chromium gets flagged, Camoufox is the right tool regardless of the aggregate benchmark.

Platform overview of Fortress

#### Engine and fingerprint core

Fortress v3 runs on Chromium 153.0.8010.36 and is updated monthly. Its 81+ patches live in Chromium's C++ layer, covering GPU, screen, fonts, timezone, and other surfaces, per the Fortress site. The current major version line and changelog are maintained in the GitHub repository.

#### Installation and activation

Install via pip, npm, Docker, a .deb package, or a single binary. Activate once with tilion activate; the key is saved to ~/.tilion/license.jwt and checked offline, with no usage reporting. Without activation the engine runs on the public v1 engine.

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

#### Connecting from Playwright

Existing Playwright code connects over CDP with no stealth plugins:

```python from playwright.sync_api import sync_playwright

with sync_playwright() as p: browser = p.chromium.connect_over_cdp("http://localhost:9222") page = browser.contexts[0].new_page() page.goto("https://fortress.tilion.com/") ```

#### MCP server for agents

tilion mcp starts a local MCP server with 29 tools, free, no account required. Claude, Codex, Cursor, Windsurf, and Cline use it to read blocked pages, extract fields, and click, type, or fill forms. Agent wiring instructions are in AGENTS.md.

#### CLI and fleet management

The CLI covers activation (tilion activate [--headless] [--token <jwt>]), license status (tilion license status [--json]), platform downloads (tilion get linux-x64), and engine launch with a chosen port. CI and Docker environments set TILION_LICENSE_KEY=<key>; note that an environment key overrides the file, and an expired environment key can shadow a fresh file on disk.

#### Licensing and pricing

v3 is free for developers with no caps on machines, sessions, or concurrency, under the Fortress Source Available License 1.1: reading, modifying, rebuilding, and redistributing are allowed, as is development and evaluation. Production use is free for individuals and smaller organizations, with funding and revenue thresholds; larger organizations need a subscription, with production keys published at fortress.tilion.com/pricing. Older engine code remains under BSD-3.

If you want the same stealth engine as a managed cloud service with residential egress and region configuration, Tilion Cloud is in beta; you can join the waitlist at tilion.com.

How to choose: decision matrix

| Your situation | Choose | |---|---| | Chromium rendering or Widevine required | Fortress (Camoufox is Firefox-based) | | Existing Playwright/Puppeteer Chromium code you don't want to rewrite | Fortress, connect over CDP | | Agent framework (Claude, Cursor, Cline) needs browser tools | Fortress, via the 29-tool MCP server | | Strict open-source-only procurement | Camoufox | | Maximum measured block-rate reduction on protected sites | Fortress, 86.4% vs 74.5% on the published 92-site run | | Firefox fingerprints test better against your targets | Camoufox | | Managed cloud with residential egress and regions | Tilion Cloud (beta waitlist), not either self-hosted engine |

Switching from Camoufox to Fortress

1. Install and activate the engine. pip install tilion-fortress, then tilion activate. In CI, set TILION_LICENSE_KEY instead of relying on the license file.

2. Swap the launch code. Camoufox launches a Playwright Firefox instance through its own context manager:

```python

from camoufox.sync_api import Camoufox

with Camoufox(headless=True) as browser: page = browser.new_page() page.goto(url) ```

Fortress runs as a standalone engine and your Playwright code attaches over CDP:

```python

from playwright.sync_api import sync_playwright

with sync_playwright() as p: browser = p.chromium.connect_over_cdp("http://localhost:9222") page = browser.contexts[0].new_page() page.goto(url) ```

3. Watch for these differences. Camoufox fingerprint options passed to its constructor have no direct equivalent; Fortress mints its own coherent machine identity per launch. If you relied on specific Camoufox locale or screen settings, verify the pages you care about still render correctly, since Fortress controls those surfaces internally.

4. Know what has no equivalent. Fortress has no built-in CAPTCHA-solving service and no built-in proxy rotation; the roadmap lists residential and mobile egress, keystroke and scroll variance, and TLS fingerprint work as future items. If your pipeline depends on those, a partial migration, Fortress for the pages that need Chromium stealth and Camoufox retained for the rest, is a legitimate end state.

5. Add the MCP server if agents are involved. tilion mcp gives your coding agents 29 local tools with no extra cost; there is nothing to migrate, just a new capability to wire in.

FAQ

Is Fortress actually better than Camoufox at avoiding blocks?

On Tilion's own 28 September 2026 run of 92 protected sites, headless on datacenter IPs with no proxies, Fortress served 86.4% of pages and Camoufox served 74.5%, with puppeteer-extra stealth at 72.3% and stock Chrome at 34.2%. The methodology is published in the repo's docs/BENCHMARK.md, so rerun it on your target list before deciding.

Does Fortress work with my existing Playwright code?

Yes. It is a Chromium fork exposing raw CDP on port 9222, so chromium.connect_over_cdp() is the only change. No stealth plugins, no JS patches, and no Firefox API migration.

How do AI agents use Fortress?

Two ways: attach your agent's Playwright or Puppeteer client over CDP, or start the local MCP server with tilion mcp and give Claude, Codex, Cursor, Windsurf, or Cline its 29 tools for reading blocked pages and interacting with forms. Setup is documented in the repo's AGENTS.md.

What does Fortress cost?

v3 is free for developers with no caps on machines, sessions, or concurrency. Production use is free for individuals and smaller organizations under the Fortress Source Available License 1.1; larger organizations need a subscription, and production keys are published on the Fortress pricing page.

Does Fortress solve CAPTCHAs?

It passes Akamai's _abck cookie check where stock Chrome gets Access Denied, but there is no built-in CAPTCHA-solving service. If your flow needs programmatic solving, that stays your responsibility or moves to Tilion Cloud's on-demand solve API when the beta opens.

Where does Tilion Cloud fit in?

Tilion Cloud is the managed counterpart: the same stealth approach as a hosted service. It is in beta with a waitlist and is currently ranked first on the Browser Arena and ComputeSDK benchmarks; Fortress is the self-hosted, open-source engine you can run today.

Fortress is free to run and takes one line to wire into the Playwright code you already have. Get a production key or download the engine and test it against your own target sites this week.