Back to blogSolution

Tilion Fortress vs. Camoufox (2026)

Tilion Fortress fixes the GPU fingerprint inside Chromium's C++ so a headless browser on a bare Linux server reads as a real machine, while Camoufox approaches the same problem from a Firefox codebase.


Introduction and methodology note

Headless Chrome on a server without a GPU falls back to SwiftShader, a software renderer, and the WebGL vendor and renderer strings it reports are a well-known bot signal. Two open-source projects attack that problem differently. Tilion's Fortress engine is a Chromium fork with 81+ patches in the C++ layer covering GPU, screen, fonts, timezone and more, so every launch mints a distinct, internally coherent machine where GPU, screen, cores, timezone, language and fonts agree (fortress.tilion.com). Camoufox is a Firefox-based stealth browser that takes the anti-fingerprinting route from the Mozilla side.

This page compares the two for teams running unattended browsers on Linux servers. On Tilion's own 92-site reproducible test (28 September 2026, headless, datacenter IPs, no proxies), Fortress loaded 86.4% of protected sites versus 74.5% for Camoufox, 72.3% for puppeteer-extra stealth and 34.2% for stock Chrome; the methodology and harness are published in the Fortress repo at github.com/tiliondev/fortress under docs/BENCHMARK.md.

Methodology note: Fortress figures on this page come from Tilion's own published pages and repo, linked inline. Camoufox figures come from its published pages and are stated as plain text without links. The 92-site comparison was run by Tilion on Tilion's harness, so treat it as a self-run result, not an independent benchmark. All pass-rate and fingerprint claims are self-reported by each vendor; test both engines on your own target sites before committing.

TL;DR

  • Fortress patches GPU, canvas, audio, fonts and screen fingerprints in Chromium's C++, so headless and headed modes present the same fingerprint, including on datacenter IPs, and it passes CreepJS, BrowserScan, rebrowser and WebGL checks per Tilion's published results.
  • On Tilion's own 92-site protected-site test (28 September 2026), Fortress served 86.4% of pages versus Camoufox at 74.5%, both fully headless on datacenter IPs with no proxies.
  • Camoufox is the simpler zero-activation option; Fortress v3 is free for developers with no caps but requires a one-time tilion activate, and larger organizations need a production subscription (fortress.tilion.com/pricing).

Quick-comparison table

| Dimension | Tilion Fortress | Camoufox | |---|---|---| | Engine base | Chromium fork, v3 on Chromium 153.0.8010.36, updated monthly | Firefox-based | | GPU fingerprint approach | 81+ patches in Chromium C++ covering GPU, screen, fonts, timezone and more | Not published on the pages reviewed | | Per-launch machine coherence | Distinct internally coherent machine per launch; GPU, screen, cores, timezone, language, fonts agree | Not published on the pages reviewed | | Headless vs headed parity | Same fingerprint in both modes, including on datacenter IPs | Not published on the pages reviewed | | Protected-site rate (Tilion's 92-site harness, 28 Sep 2026) | 86.4% (95% Wilson interval 81 to 91) | 74.5% | | Anti-bot checks passed | CreepJS, BrowserScan, rebrowser, WebGL checks; Akamai _abck cookie where stock Chrome gets Access Denied | Not published on the pages reviewed | | CDP support | Native; connect Playwright/Puppeteer over CDP on :9222 | Not applicable (Firefox protocol) | | Install | pip, npm, Docker (tilion/fortress:latest), .deb, single binary | Not published on the pages reviewed | | License | v3 free for developers, no caps; Fortress Source Available License 1.1; larger organizations need a subscription | Not published on the pages reviewed | | Platforms | Linux x64/arm64/x86/armhf, Windows x64, macOS | Not published on the pages reviewed |

Granular differentiator table

The differentiator that matters for the SwiftShader problem is fingerprint coherence: not just spoofing one value, but making GPU, screen, cores and fonts agree with each other and stay stable within a session.

| Fingerprint dimension | Tilion Fortress | Camoufox | |---|---|---| | WebGL vendor/renderer | Patched in Chromium C++ as part of the GPU layer; passes WebGL checks | Not published on the pages reviewed | | Machine coherence | GPU, screen, cores, timezone, language and fonts agree within each launch | Not published on the pages reviewed | | Per-launch distinctness | Canvas and Audio fingerprints distinct 40/40 across 40 launches | Not published on the pages reviewed | | Headless parity | Headless and headed present the same fingerprint, including on datacenter IPs | Not published on the pages reviewed | | Human-like input | Mouse movement modeled on recordings of about 10,000 people | Not published on the pages reviewed | | Protected-site rate, same harness | 86.4% of 92 sites (Tilion's own test) | 74.5% on the same test |

The honest reading of that last row: it is Tilion's harness, Tilion's site list, and Tilion ran both engines. Camoufox publishes no equivalent head-to-head number on these pages, so 86.4% versus 74.5% is the only directly comparable figure available, and it is self-run.

Why teams choose Tilion Fortress over Camoufox

#### The GPU fingerprint is fixed in the binary, not patched at runtime

Stock headless Chrome on a GPU-less server reports SwiftShader's renderer strings, and JavaScript-level stealth plugins cannot fully reconcile that with the rest of the machine. Fortress recompiles Chromium's C++ so the fingerprint is correct at the source, which is why existing Playwright and Puppeteer code connects over chromium.connect_over_cdp with no stealth plugins or JS patches (fortress.tilion.com). Nothing in the page's JavaScript can see a patching layer, because there is none.

#### Headless on a datacenter IP is the tested configuration

The 92-site test that produced the 86.4% figure ran fully headless, on datacenter IPs, with no proxies, one fresh cloud machine per run, 1,584 machines total, against sites protected by Cloudflare, DataDome, Akamai, HUMAN, Kasada, Imperva, AWS WAF, Arkose and reCAPTCHA. That is exactly the deployment shape of a server fleet: no residential proxy bill, no headed X server. Per Tilion's published results, Fortress also passes the Akamai _abck check where stock Chrome gets Access Denied.

#### It stays a Chromium fingerprint

Fortress is Chromium 153.0.8010.36, updated monthly, so the engine matches what real users run and your Playwright and Puppeteer code works unchanged. Camoufox is Firefox-based, which is a legitimate choice, but it means your automation stack, debugging protocol and fingerprint family all differ from the Chrome majority. If your target sites see mostly Chrome traffic, a coherent Chrome fingerprint is the closer fit.

If you are evaluating engines for a server fleet, you can join the Tilion waitlist at tilion.com to get managed sessions on the same stealth stack.

Best use cases for Tilion Fortress

#### Long-running scraping fleets on cloud VMs

A fresh, internally coherent machine per launch means a fleet of containers each looks like a different physical computer, and the coherence (GPU agreeing with screen, cores and fonts) is what coherence-checking anti-bots test for. Docker deployment is one line: docker run --rm -p 9222:9222 tilion/fortress:latest (hub.docker.com/r/tilion/fortress). How Camoufox compares: it also targets stealth automation, but Tilion's published head-to-head on the same 92-site harness puts it 12 points lower in pages served.

#### AI agents that need to read blocked pages

Fortress ships a local MCP server with 29 agent tools, free, no account required, so Claude, Codex, Cursor, Windsurf and Cline can read blocked pages, extract fields and fill forms (github.com/tiliondev/fortress). Setup instructions for agents are in the repo's AGENTS.md. How Camoufox compares: Camoufox integrates with Python automation frameworks, but it does not ship an equivalent local MCP tool server on the pages reviewed.

#### CI and ephemeral containers

Activation is offline and never reports usage; CI and Docker set TILION_LICENSE_KEY=<key> or pass tilion activate --token <key>, and the engine runs with no caps on machines, sessions or concurrency. How Camoufox compares: Camoufox needs no activation step at all, which is simpler for a quick prototype; the trade-off is the lower pages-served rate on Tilion's own test.

#### Teams already on Playwright or Puppeteer

Because Fortress speaks CDP natively on :9222, swapping engines is a connection-string change, not a rewrite. How Camoufox compares: Camoufox requires its own Firefox-based launch API, so Playwright Chromium code needs adaptation rather than a URL swap.

Best use cases for Camoufox

#### Firefox-fingerprint requirements

If a site's traffic profile or your test matrix calls for a Firefox fingerprint, Camoufox is the Firefox-based option in this comparison and Fortress does not offer a Firefox engine at all. That is a genuine gap on Tilion's side, not a rounding error.

#### Zero-setup experimentation

Camoufox has no activation or license step for the use cases reviewed here, so for a weekend prototype it is the lower-friction path. Fortress v3 is also free for developers, but it requires the one-time tilion activate before the v3 engine runs; without activation it falls back to the public v1 engine.

Platform overview of Tilion Fortress

#### Chromium fork with native C++ patches

Fortress is a Chromium fork, currently v3 on Chromium 153.0.8010.36, with 81+ patches covering GPU, screen, fonts, timezone and more (fortress.tilion.com). Because the fixes live in the binary, no runtime injection is needed.

#### CDP-first automation

Existing Playwright and Puppeteer code connects over Chrome DevTools Protocol with no stealth plugins:

```python import asyncio, playwright.async_api as pw

async def main(): browser = await pw.chromium.connect_over_cdp("http://localhost:9222") page = (await browser.contexts[0].pages()) if browser.contexts else await (await browser.new_context()).new_page() await page.goto("https://tilion.dev") ```

#### Install options

Python (pip install tilion-fortress), Node (npm install tilion-fortress), Docker (tilion/fortress:latest), .deb, or a single binary. The Python wheel exposes tilion_fortress (two ls in the module name), a detail worth knowing before your first import fails.

#### Licensing and activation

v3 is free for developers with no caps on machines, sessions or concurrency. Activate once with tilion activate; the key is saved to ~/.tilion/license.jwt and checked offline, never reporting usage. Production keys for larger organizations are at fortress.tilion.com/pricing.

#### Local MCP server for agents

tilion mcp starts a local MCP server with 29 tools, free, no account required, letting coding agents read blocked pages and interact with forms (github.com/tiliondev/fortress).

#### Published benchmark methodology

The 92-site test (86.4% pages served, 95% Wilson interval 81 to 91) is reproducible: methodology and harness are in the repo at docs/BENCHMARK.md, with two reps per site and a fresh cloud machine per run (github.com/tiliondev/fortress). Tilion also reports a 71-site harness where Tilion Cloud served 86% of protected sites; that is a separate, self-run test of the cloud product, not of the Fortress engine.

How to choose

| Your situation | Choose | |---|---| | Headless Chrome on GPU-less Linux servers getting flagged on GPU/WebGL checks | Tilion Fortress: GPU fingerprint fixed in C++, headless parity tested on datacenter IPs | | You need a Firefox fingerprint specifically | Camoufox; Fortress does not ship a Firefox engine | | Zero-activation prototype this afternoon | Camoufox, or Fortress on the public v1 engine before activating | | Highest pages-served rate on Tilion's own 92-site harness | Fortress (86.4% vs Camoufox 74.5%, 28 September 2026) | | Existing Playwright/Puppeteer CDP codebase | Fortress: connect over CDP, no code rewrite | | Coding-agent workflows (Claude, Cursor, Codex) | Fortress: local MCP server with 29 tools | | Larger organization needing production use | Fortress with a production key from fortress.tilion.com/pricing; Camoufox licensing terms per its own pages |

Migration guide: Switching from Camoufox to Tilion Fortress

The migration is small because Fortress speaks CDP: you keep Playwright or Puppeteer and change how the browser is obtained.

1. Install the engine. pip install tilion-fortress, or run the Docker image: docker run --rm -p 9222:9222 tilion/fortress:latest. 2. Activate v3. Run tilion activate once (or set TILION_LICENSE_KEY in CI). Without activation you get the public v1 engine. 3. Point your client at the CDP endpoint. Before, a typical headless setup on a GPU-less server launches Chromium with software rendering flags such as --disable-gpu or --use-gl=swiftshader, and the WebGL strings give the bot away. After:

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

4. Watch for these differences. Fortress mints a distinct coherent machine per launch, so do not reuse one browser context across sessions expecting the same fingerprint; launch fresh. The npm package was still on Chromium 151.0.7910, so Node projects should connect over CDP to a separately installed v3 engine rather than relying on the bundled version. 5. Know what has no equivalent. There is no Firefox engine, so a strict requirement for a Firefox fingerprint is a reason to keep Camoufox for that part of the stack; a partial migration (Fortress for Chrome-shaped targets, Camoufox for Firefox-shaped ones) is a legitimate end state.

FAQ

Does Fortress actually fix the SwiftShader GPU problem, or hide it?

It fixes it in the binary. The GPU layer is patched in Chromium's C++ as part of 81+ patches, and each launch mints a machine where GPU, screen, cores, timezone, language and fonts agree, per Tilion's published results at fortress.tilion.com. There is no JS patch layer for a page to detect.

Is the 86.4% vs 74.5% comparison independent?

No. It comes from Tilion's own 92-site reproducible test (28 September 2026, headless, datacenter IPs, no proxies), with the harness published in the Fortress repo. Camoufox publishes no competing head-to-head on the pages reviewed, so treat the gap as self-reported and test on your own targets.

Does headless mode look different from headed mode?

Per Tilion's published results, headless and headed modes present the same fingerprint, including on datacenter IPs. That is the specific claim relevant to unattended servers.

What does Fortress cost?

v3 is free for developers with no caps on machines, sessions or concurrency, under the Fortress Source Available License 1.1. Larger organizations need a production subscription; rates are at fortress.tilion.com/pricing. Tilion Cloud, the managed version, is in beta with a waitlist at tilion.com.

Which platforms are supported?

Linux x64 is shipping, along with Linux arm64, x86 and armhf (no Widevine on those), Windows x64, and macOS arm64/x64 built from source. Docker and a single binary are also available.

Can my AI agent use it directly?

Yes. tilion mcp starts a local MCP server with 29 tools, free, no account required, and agent setup instructions are in the repo's AGENTS.md. Fortress also documents compatibility with browser-use, crawl4ai, Stagehand and LangChain.

If your servers are getting flagged on GPU checks today, join the Tilion waitlist at tilion.com or start with the free Fortress engine from the Fortress repo.