Back to blogSolution

launch Camoufox as a Firefox binary, drive it with Playwright

Fortress is a Chromium fork you can drive from Puppeteer over the Chrome DevTools Protocol, while Camoufox is a Firefox-based stealth browser, so the two solve bot detection from opposite sides of the browser-engine divide.


Introduction and methodology note

Teams that run Puppeteer and hit sites that only behave correctly in Chrome face a real constraint: Camoufox is built on Firefox, so a Chromium-based stealth option is the actual requirement. Fortress, from Tilion, is that option. It is a Chromium fork that corrects the browser fingerprint inside Chromium's C++ code, so the browser reads as an ordinary Chrome install without stealth plugins or JavaScript patches, and existing Puppeteer code connects over CDP with no rewrite (fortress.tilion.com).

Camoufox is a capable Firefox-based anti-detect browser, and on Tilion's own 92-site reproducible test it scored 74.5% pages served against Fortress's 86.4% (28 September 2026, headless, datacenter IPs, no proxies; methodology in the Fortress repo's docs/BENCHMARK.md, github.com/tiliondev/fortress). That is Tilion's own harness, so treat it as a vendor-run result.

Methodology note: Fortress figures on this page come from Tilion's published pages, linked inline. Camoufox figures come from its own published pages and are stated as plain text with no links. Where a figure is not published on the pages reviewed, the table says "not published." Accuracy and success-rate claims are self-reported by each vendor; test both engines on your own target sites before committing.

TL;DR

  • Fortress is Chromium (currently v3 on Chromium 153.0.8010.36, updated monthly), so Puppeteer attaches over CDP exactly as it does to stock Chrome, and Chrome-only sites behave like Chrome.
  • On Tilion's own 92-site protected-site test (28 September 2026, headless, datacenter IPs, no proxies), Fortress served 86.4% of pages versus Camoufox at 74.5%.
  • Fortress v3 is free for developers with no caps on machines, sessions, or concurrency; production keys for larger organizations are priced at fortress.tilion.com/pricing.

Quick-comparison table

| Dimension | Fortress | Camoufox | |---|---|---| | Browser engine | Chromium 153.0.8010.36 (v3), updated monthly | Firefox-based | | Puppeteer support | Native, raw CDP on port 9222 or tilion CLI endpoint | Not published on the pages reviewed | | Protected-site success (92-site test, 28 Sep 2026) | 86.4% pages served | 74.5% pages served | | Fingerprint patches | 81+ patches in Chromium's C++ layer (vendor claim) | Not published on the pages reviewed | | Headless vs headed fingerprint | Same fingerprint in both modes, including on datacenter IPs (vendor claim) | Not published on the pages reviewed | | Pricing | Free for developers, no caps; production keys for larger organizations, rates not published on the page reviewed | Not published on the pages reviewed | | Distribution | pip (tilion-fortress), npm, Docker, .deb, single binary, macOS .app | Not published on the pages reviewed | | Agent tooling | Local MCP server with 29 tools, free, no account | Not published on the pages reviewed |

The engine row is the decision. If your stack is Puppeteer and your targets require Chrome, a Firefox-based engine is a non-starter regardless of how the rest of the table reads.

Granular differentiator table

| Capability | Fortress | Camoufox | |---|---|---| | Engine base | Chromium fork, fingerprint fixed in C++ | Firefox-based | | Stealth plugin needed | No; no JS fingerprint patches | Not published on the pages reviewed | | 92-site test, pages served (Tilion's harness, 28 Sep 2026) | 86.4% (95% Wilson interval 81 to 91) | 74.5% | | puppeteer-extra stealth comparison in same test | Fortress 86.4% vs puppeteer-extra stealth 72.3% vs stock Chrome 34.2% | Not tested in that run | | Akamai _abck | Passes where stock Chrome gets Access Denied (vendor claim) | Not published on the pages reviewed | | Per-launch fingerprint coherence | Each launch mints a distinct internally coherent machine; Canvas and Audio distinct 40/40 across 40 launches | Not published on the pages reviewed | | Human-like input | Mouse movement modeled on recordings of about 10,000 people (vendor claim) | Not published on the pages reviewed | | Activation | One-time tilion activate, offline check, never reports usage | Not published on the pages reviewed | | MCP server for coding agents | 29 local tools, free | Not published on the pages reviewed |

The 92-site test is the only head-to-head number available, and it is Tilion's own harness. The gap (86.4% vs 74.5%) is meaningful but self-reported; the methodology is public in the repo if you want to reproduce it.

Why teams choose Fortress over Camoufox

#### It speaks CDP, so Puppeteer code does not change

Fortress launches and prints a CDP endpoint, or listens on port 9222 in Docker. Your existing puppeteer.connect() call with the engine's browserURL is the whole integration. No stealth plugin, no puppeteer-extra wrapper, no fingerprint patching in userland. Camoufox is Firefox-based, so a Puppeteer stack has no equivalent path; per its own published pages reviewed for this comparison, no Puppeteer integration is documented.

#### Chrome-only sites behave like Chrome

Because the fingerprint corrections live in Chromium's C++ rather than injected JavaScript, the browser presents a coherent Chrome fingerprint at the engine level: GPU, screen, cores, timezone, language, and fonts agree on every launch (fortress.tilion.com). Sites that gate on Chrome-specific behavior, Widevine, or Chromium rendering quirks get a real Chromium. On Tilion's 92-site test, Fortress loaded 86.4% of protected sites fully headless on datacenter IPs with no proxies, versus Camoufox at 74.5% and puppeteer-extra stealth at 72.3%.

#### It is free for developers with no caps

Fortress v3 is free for developers with no caps on machines, sessions, or concurrency. Activation is a one-time offline check (tilion activate, key saved to ~/.tilion/license.jwt); the engine never reports usage. CI and Docker set TILION_LICENSE_KEY. Production use for larger organizations needs a subscription, with rates at fortress.tilion.com/pricing. Camoufox pricing is not published on the pages reviewed for this comparison.

If your Puppeteer stack is already blocked on Chrome-only targets, you can download Fortress from the project site and point Puppeteer at it in an afternoon.

Best use cases for Fortress

#### Puppeteer scraping behind commercial anti-bot

Fortress passed CreepJS, BrowserScan, rebrowser, and WebGL checks, and passes Akamai (_abck cookie) where stock Chrome gets Access Denied, per Tilion's published results. The 86.4% figure on the 92-site test covers Cloudflare, DataDome, Akamai, HUMAN, Kasada, Imperva, AWS WAF, Arkose, and reCAPTCHA.

How Camoufox compares: on the same Tilion-run test it served 74.5% of pages, and it cannot run your Puppeteer code at all because it is not Chromium.

#### Coding-agent workflows on blocked pages

Fortress ships a local MCP server with 29 agent tools, free, no account required. Claude, Codex, Cursor, Windsurf, and Cline can read blocked pages, extract fields, and click, type, or fill forms. Setup instructions live in the repo's AGENTS.md.

How Camoufox compares: no equivalent MCP server is documented on the pages reviewed.

#### CI and containerized fleets

The Docker image (tilion/fortress:latest) exposes raw CDP on port 9222, so a container is one docker run command. There are no caps on machines, sessions, or concurrency for developers, and the license check is offline, so air-gapped CI works.

How Camoufox compares: Camoufox distribution and CI story is not published on the pages reviewed for this comparison.

#### Agent frameworks that expect Chromium

Fortress works with browser-use, crawl4ai, Stagehand, and LangChain, all of which assume a Chromium-compatible CDP endpoint. Tilion also runs Tilion Cloud, a managed beta of isolated Chromium sessions with residential egress; you can join the waitlist at tilion.com.

How Camoufox compares: Chromium-assuming frameworks need a Firefox adapter or a different automation stack.

Best use cases for Camoufox

#### Teams already standardized on Firefox automation

If your automation is built on Firefox APIs and your targets do not require Chrome, Camoufox does that job and you should not migrate for its own sake. Fortress's advantage in the published comparison is Chrome compatibility and the 92-site result, not a general reason to leave a working Firefox setup.

#### Python-first stacks with no Chrome requirement

Camoufox's published materials target Python automation. If your stack is Python and Playwright against Firefox-tolerant sites, the switching cost of moving to a Chromium engine buys you nothing measurable on sites that already serve you.

Platform overview of Fortress

#### Engine and fingerprinting

Fortress recompiles Chromium's C++ to correct fingerprints natively: 81+ patches covering GPU, screen, fonts, timezone, and more, with headless and headed modes presenting the same fingerprint even on datacenter IPs (fortress.tilion.com). Each launch mints a distinct internally coherent machine; Canvas and Audio fingerprints were distinct in 40 of 40 launches.

#### Installation and activation

Install via pip install tilion-fortress or npm install tilion-fortress, then activate once:

``bash npm install -g tilion-fortress tilion activate ``

The key is saved to ~/.tilion/license.jwt (Windows: %USERPROFILE%\.tilion\license.jwt). Without activation the engine runs on the public v1 engine. The Python wheel is tilion-fortress and the module is tillion_fortress (two "l"s), a naming quirk worth knowing before your first import fails.

#### Puppeteer over CDP

Launch the engine with tilion --port 9222 and connect:

```js import puppeteer from 'puppeteer';

const browser = await puppeteer.connect({ browserURL: 'http://localhost:9222', }); const page = await browser.newPage(); await page.goto('https://fortress.tilion.com/'); ```

The npm package currently bundles the 151 engine; Node projects should connect over CDP to a separately installed v3 engine.

#### Docker and CI

docker run --rm -p 9222:9222 tilion/fortress:latest gives raw CDP on port 9222 (hub.docker.com/r/tilion/fortress). CI sets TILION_LICENSE_KEY=<key> or uses tilion activate --token <key>; an environment key overrides the file, and note that an expired env key can shadow a fresh file on disk.

#### MCP server for agents

tilion mcp starts the local MCP server with 29 tools, free, no account. Agent setup is documented in AGENTS.md.

#### Licensing and platforms

v3 uses the Fortress Source Available License 1.1: reading, modifying, rebuilding, and redistributing are allowed, and production use is free for individuals and smaller organizations, with funding and revenue thresholds that push larger organizations to a subscription. Platforms shipping today: Linux x64, Windows x64, Linux arm64/x86/armhf (no Widevine on ARM variants), and macOS arm64/x64 built from source.

How to choose decision matrix

| Your situation | Choose | |---|---| | Puppeteer stack, sites require Chrome | Fortress | | Puppeteer stack, heavy anti-bot targets | Fortress (86.4% vs 74.5% on Tilion's 92-site test) | | Python + Playwright, Firefox-tolerant targets, working today | Camoufox | | Coding agents (Claude, Cursor, Codex) hitting 403s | Fortress, via its 29-tool MCP server | | Containerized fleets, no per-session cost | Fortress (free for developers, no caps) | | Managed cloud instead of self-hosting | Tilion Cloud beta; join the waitlist at tilion.com |

Migration guide: switching from Camoufox to Fortress

1. Install and activate the engine. npm install -g tilion-fortress (or the pip wheel), then tilion activate. The check is offline and never reports usage.

2. Start the engine and get a CDP endpoint. tilion --port 9222 launches the engine and prints the endpoint. In Docker, use the image above.

3. Swap the automation layer. A Camoufox launch in Python looks like a Playwright call against a Firefox binary. The Fortress equivalent is Puppeteer connecting over CDP:

```python

```

``js // After (Fortress, Puppeteer over CDP) const browser = await puppeteer.connect({ browserURL: 'http://localhost:9222' }); ``

4. Watch for these differences.

  • Language: Camoufox automation in Python becomes Node (or keep Python with Playwright's connect_over_cdp, which Fortress supports equally).
  • Firefox-specific flags and preferences have no equivalent; Chromium flags replace them.
  • The npm package ships the 151 engine; install v3 separately and connect over CDP rather than relying on the bundled binary.
  • The Python module is tillion_fortress, not tilion_fortress.

5. Decide the end state. If some targets are Firefox-only and others need Chrome, a partial migration is reasonable: keep Camoufox for the Firefox-only sites and run Fortress behind Puppeteer for everything else. There is no feature in Fortress that forces an all-or-nothing cutover.

FAQ

Is Fortress actually better at avoiding blocks than Camoufox?

On Tilion's own 92-site reproducible test (28 September 2026, headless, datacenter IPs, no proxies), Fortress served 86.4% of protected sites versus Camoufox at 74.5%, with puppeteer-extra stealth at 72.3% and stock Chrome at 34.2%. The methodology is public in the repo's docs/BENCHMARK.md, and it is a vendor-run test, so verify against your own targets.

Does Fortress work with Puppeteer without code changes?

Yes. The engine exposes raw CDP (port 9222 in Docker, or the endpoint printed by tilion), so puppeteer.connect({ browserURL }) is the entire integration. No stealth plugin or fingerprint patching is needed.

What does Fortress cost?

Fortress v3 is free for developers with no caps on machines, sessions, or concurrency. Production use for larger organizations requires a subscription; rates are not published on the page reviewed and are available at fortress.tilion.com/pricing. Camoufox pricing is not published on the pages reviewed for this comparison.

Is Fortress really Chromium?

Yes. v3 is built on Chromium 153.0.8010.36 and updated monthly, so Chrome-only sites, Widevine-dependent pages, and Chromium rendering behavior are native, not emulated.

Can I keep Camoufox for some sites?

Yes. Fortress and Camoufox can run side by side; point Puppeteer at Fortress for Chrome-required targets and keep Camoufox where Firefox already works. Nothing in Fortress's license or activation model prevents a mixed fleet.

What if I want this without self-hosting?

Tilion Cloud is a managed beta of isolated, always-stealth Chromium sessions, attachable from Puppeteer over CDP. It is in beta; you can join the waitlist at tilion.com.

If Puppeteer is your stack and Chrome is what your targets demand, download Fortress and connect over CDP today.