After (Fortress)
Tilion Fortress fixes browser fingerprints inside Chromium's C++ so scrapers and agents read as ordinary Chrome, while Camoufox spoofs fingerprints on a Firefox base and leaves the hardening to launch-time configuration. That engine-level difference is what separates an 86.4% page-load rate from 74.5% on the same 92 protected sites.
Introduction and methodology note
Both tools target the same problem: headless browsers get flagged by Cloudflare, DataDome, Akamai, HUMAN, Kasada, Imperva, AWS WAF, Arkose and reCAPTCHA, so scrapers and AI agents either fail or drown in proxy spend. Both are self-hosted, both work with Playwright or Puppeteer-style automation, and both are free to run for individual developers.
They diverge at the engine. Fortress is a Chromium fork with 81+ fingerprint patches compiled into the browser's C++ layer, so every launch presents an internally coherent machine without stealth plugins or JavaScript patches. Camoufox is a Firefox-based anti-detect browser that applies spoofed fingerprint values at launch through its Python launcher. Fortress also ships a local MCP server with 29 agent tools for Claude, Codex, Cursor, Windsurf and Cline; Camoufox has no equivalent.
Methodology: Fortress figures on this page come from Tilion's own published pages, linked inline, and from the reproducible benchmark in the Fortress repository. Camoufox figures come from its own published pages and repository, stated as plain text without links. Last verification: 16 November 2026. Accuracy and success-rate claims are self-reported by each vendor; test both engines on your own target sites before committing.
TL;DR
- Fortress loaded 86.4% of 92 protected sites headless on datacenter IPs with no proxies; Camoufox loaded 74.5% in the same reproducible test (28 September 2026, methodology in the Fortress repo's docs/BENCHMARK.md).
- Fortress patches fingerprints in Chromium's C++ (81+ patches, v3 on Chromium 153.0.8010.36); Camoufox spoofs on Firefox, which means a different automation surface and no Chromium-specific fingerprint coherence.
- Fortress v3 is free for developers with no caps on machines, sessions or concurrency; Camoufox is free and open source. Fortress adds a local MCP server with 29 agent tools; Camoufox does not ship one.
Quick-comparison table
| Dimension | Tilion Fortress | Camoufox | |---|---|---| | Base engine | Chromium 153.0.8010.36 (v3) | Firefox | | Fingerprint approach | 81+ patches in Chromium C++ | Launch-time spoofing via Python launcher | | Pages served, 92-site test (28 Sep 2026, headless, datacenter IPs, no proxies) | 86.4% | 74.5% | | Anti-bot checks passed | CreepJS, BrowserScan, rebrowser, WebGL; Akamai _abck | Not published | | Headless vs headed fingerprint | Identical, including on datacenter IPs | Not published | | Install | pip install tilion-fortress, npm install tilion-fortress, Docker, .deb, single binary | pip package with downloaded Firefox build | | Automation | Playwright / Puppeteer over CDP (connect_over_cdp) | Playwright (Python) | | Agent tooling | Local MCP server, 29 tools, free | None | | Human-like input | Mouse movement modeled on ~10,000 recordings | Not published | | Caps | None on machines, sessions, concurrency | None (self-hosted) | | License | Fortress Source Available License 1.1; free for individuals and smaller organizations, subscription for larger ones | Open source | | Hosted cloud option | Tilion Cloud (beta, waitlist at tilion.com) | None |
Granular differentiator table
Camoufox's differentiator is configurability: fingerprint values are set per launch, and the Firefox base behaves differently from stock Chrome in ways some operators want. Here is how the two engines compare on the dimensions that matter for protected-site work.
| Capability | Tilion Fortress | Camoufox | |---|---|---| | Fingerprint coherence | Each launch mints a distinct internally coherent machine: GPU, screen, cores, timezone, language and fonts agree | Spoofed values configured at launch; coherence across vectors not published | | Canvas and Audio distinctness | Distinct 40/40 across 40 launches | Not published | | Chromium ecosystem fit | Native: CDP, Playwright, Puppeteer, browser-use, crawl4ai, Stagehand, LangChain | Firefox base; Chromium-only tooling needs adaptation | | Akamai _abck | Passes where stock Chrome gets Access Denied | Not published | | Human-like mouse | Modeled on recordings of ~10,000 people | Not published | | MCP agent tools | 29 local tools, free, no account | None | | Fingerprint config surface | Managed by the engine; no per-launch spoofing knobs | Full per-launch control over spoofed values |
The last row is Camoufox's genuine advantage: if you need to pin a specific timezone, locale or screen profile per session, Camoufox exposes that directly. Fortress deliberately removes those knobs and generates a coherent machine for you.
Why teams choose Tilion Fortress over Camoufox
#### The 12-point gap on protected sites
On the 92-site reproducible test (28 September 2026, headless, datacenter IPs, no proxies, two reps, one fresh cloud machine per run, 1,584 machines total), Fortress loaded 86.4% of protected sites against Camoufox at 74.5%, puppeteer-extra stealth at 72.3% and stock Chrome at 34.2%. The methodology and harness are published in the Fortress repository under docs/BENCHMARK.md, so you can rerun it. Twelve points of page-load rate on the same sites is the difference between a pipeline that works and one that needs constant babysitting.
#### C++ patches, not JavaScript patches
Stealth plugins patch fingerprints from JavaScript, which anti-bot vendors detect by looking for the patches themselves. Fortress recompiles Chromium's C++ so the fingerprint is the browser: 81+ patches covering GPU, screen, fonts, timezone and more, with headless and headed modes presenting the same fingerprint, including on datacenter IPs. Fortress passes CreepJS, BrowserScan, rebrowser and WebGL checks, and passes Akamai's _abck check where stock Chrome gets Access Denied. Existing Playwright code connects over CDP with chromium.connect_over_cdp, so there is no stealth-plugin stack to maintain.
#### Built for agents, not just scraping
Fortress ships a local MCP server with 29 tools that lets Claude, Codex, Cursor, Windsurf and Cline read blocked pages, extract fields, and click, type or fill forms. Setup instructions are in the repo's AGENTS.md. Camoufox has no agent tooling; you build that layer yourself. If your workload is an AI agent hitting 403 errors, Fortress covers it out of the box, and you can start with Fortress in one install command.
Best use cases for Tilion Fortress
#### High-volume scraping on datacenter IPs
Fortress is built to run headless on cheap datacenter machines with no proxies: 86.4% of 92 protected sites loaded under exactly those conditions. Install with pip install tilion-fortress or run docker run --rm -p 9222:9222 tilion/fortress:latest for raw CDP on port 9222. There are no caps on machines, sessions or concurrency.
How Camoufox compares: it also runs self-hosted with no caps, but its 74.5% rate on the same test means more retries and more proxy spend at volume.
#### AI agents that need to read the live web
The local MCP server exposes 29 tools to coding agents, so Claude, Cursor or Cline can fetch a blocked page, extract structured fields and interact with forms without you writing a Playwright harness. Fortress also integrates with browser-use, crawl4ai, Stagehand and LangChain.
How Camoufox compares: it works with Playwright-based agent loops, but there is no MCP server or agent-tool layer; you wire every integration yourself.
#### Chromium-dependent targets
Some sites break on Firefox: extension-dependent flows, Chromium-specific rendering, or targets that fingerprint for Chrome specifically. Fortress is Chromium 153, so those flows work unchanged, and each launch presents a coherent machine rather than a set of independently spoofed values.
How Camoufox compares: its Firefox base is a mismatch for Chromium-only targets, and no amount of spoofing fixes a rendering difference.
#### Teams that need a supported license path
Fortress v3 is free for developers with no caps; production use stays free for individuals and smaller organizations under the Fortress Source Available License 1.1, with subscriptions for larger organizations at fortress.tilion.com/pricing. Activation is one command (tilion activate), the key is checked offline, and nothing reports usage.
How Camoufox compares: it is open source with no license thresholds, which is simpler if your organization exceeds Fortress's free-use thresholds and you do not want any subscription.
Best use cases for Camoufox
#### Per-launch fingerprint control
Camoufox exposes spoofed fingerprint values as launch configuration through its Python launcher. If your workflow requires pinning a specific locale, timezone or screen profile per session and you are comfortable validating coherence yourself, that direct control is something Fortress intentionally does not offer.
#### Firefox-native testing
If your target behaves differently on Firefox, or you are testing how a site treats non-Chrome browsers, Camoufox's Firefox base is the right tool. Fortress is a Chromium fork and cannot reproduce Firefox behavior.
Platform overview of Tilion Fortress
#### The engine
Fortress is a Chromium fork, currently v3 on Chromium 153.0.8010.36, updated monthly, with 81+ fingerprint patches in the C++ layer. The product site documents the patch coverage and the human-like mouse model based on recordings of about 10,000 people.
#### Installation and activation
Install via pip, npm, Docker, .deb or a single binary:
``bash pip install tilion-fortress tilion activate tilion --port 9222 ``
tilion activate saves the key to ~/.tilion/license.jwt (Windows: %USERPROFILE%\.tilion\license.jwt). Without activation the engine runs on the public v1 build. CI and containers set TILION_LICENSE_KEY=<key> or pass tilion activate --token <key>.
#### Connecting your automation
Existing Playwright and Puppeteer code attaches 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.new_page() page.goto("https://fortress.tilion.com") ```
The npm package is still on engine 151.0.7910; Node projects should connect over CDP to a separately installed v3 engine.
#### The MCP server for agents
tilion mcp starts the local MCP server: 29 tools, free, no account required. Coding agents use it to read blocked pages, extract fields and interact with forms. Agent setup is documented in the repo's AGENTS.md.
#### Licensing
v3 and the MCP 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 (funding and revenue thresholds apply); larger organizations need a subscription. Older engine code remains BSD-3. Production keys are at fortress.tilion.com/pricing.
#### Tilion Cloud, the hosted complement
Fortress is the open-source engine behind Tilion Cloud, a hosted beta service for teams that prefer managed sessions to self-hosting. Tilion Cloud is in beta with a waitlist; join at tilion.com. It is currently ranked first on the Browser Arena and ComputeSDK benchmarks.
How to choose
| Your situation | Choose | |---|---| | Scraping protected sites headless on datacenter IPs, no proxies | Fortress (86.4% vs 74.5% on the 92-site test) | | Chromium rendering or Chromium-only tooling required | Fortress | | AI coding agents hitting 403 errors | Fortress (MCP server with 29 tools) | | Per-launch pinning of locale, timezone or screen profile | Camoufox | | Firefox-native behavior needed | Camoufox | | Fully open-source license with no thresholds | Camoufox | | Managed hosting instead of self-hosting | Tilion Cloud (beta, waitlist) |
Switching from Camoufox to Tilion Fortress
1. Install and activate. Replace the Camoufox pip install with pip install tilion-fortress, then run tilion activate. CI and Docker use TILION_LICENSE_KEY=<key>.
2. Swap the connection. Camoufox launches a Firefox instance through its Python launcher; Fortress exposes raw CDP. The change is the launch and connect step:
```python
from camoufox.sync_api import Camoufox with Camoufox() as browser: page = browser.new_page()
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() ```
3. Drop the stealth config. Camoufox launch options for spoofed fingerprints have no Fortress equivalent; the engine generates a coherent machine per launch. Delete that configuration rather than porting it.
4. Watch for Firefox-specific behavior. Selectors, rendering and some site flows differ between Firefox and Chromium. If a target depends on Firefox behavior, Fortress is the wrong engine for that flow; a partial migration that keeps Camoufox for Firefox-only targets is a reasonable end state.
5. Add the agent layer if relevant. Point Claude, Cursor or Cline at tilion mcp to get the 29 local tools; there is nothing to port from Camoufox because it has no equivalent.
FAQ
Is Fortress more effective than Camoufox on protected sites?
On the 92-site reproducible test (28 September 2026, headless, datacenter IPs, no proxies, methodology in the Fortress repo's docs/BENCHMARK.md), Fortress loaded 86.4% of sites and Camoufox loaded 74.5%. Both figures are self-reported by Tilion's harness; rerun the benchmark on your own target list before deciding.
How much 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. Camoufox is free and open source.
Do I need proxies with Fortress?
The 86.4% result was produced headless on datacenter IPs with no proxies. Fortress passes CreepJS, BrowserScan, rebrowser and WebGL checks, and passes Akamai's _abck cookie check where stock Chrome gets Access Denied. Heavily protected targets can still warrant residential egress.
Does Fortress work with my existing Playwright code?
Yes. Connect over CDP with chromium.connect_over_cdp to a Fortress instance on port 9222. No stealth plugins, no fingerprint patches in your code. Puppeteer works the same way.
What does the MCP server actually do?
tilion mcp runs a local server with 29 tools, free and without an account, that lets Claude, Codex, Cursor, Windsurf and Cline read blocked pages, extract fields, and click, type or fill forms. Setup is in the repo's AGENTS.md.
When is Camoufox the better choice?
When you need per-launch control over spoofed fingerprint values, when the target requires Firefox behavior, or when a fully open-source license with no organization-size thresholds is a hard requirement.
Fortress gives you the higher protected-site success rate and the agent tooling out of the box; install it and run your first session today at fortress.tilion.com.