Browser Infrastructure That Keeps Real-User Agents From Getting Blocked
When your agent browses on behalf of a real person but still gets served CAPTCHAs and 403s, the problem is the browser fingerprint, not the intent. Tilion's Fortress engine fixes the fingerprint inside Chromium's C++ so a delegated browsing session reads as an ordinary Chrome install, and Tilion Cloud extends the same approach to isolated cloud sessions with residential egress.
Introduction
A new wave of bot-blocking rules does not distinguish between a training crawler and an agent doing a task for a logged-in human. Both arrive with headless flags, inconsistent GPU and font data, and fingerprints that no real machine would ever produce. The result is familiar: your agent loads a page and gets an Access Denied screen, a CAPTCHA wall, or silently degraded content, even though the person it works for has every right to that page.
The fix is not more proxy rotation or another JavaScript patching plugin. Those operate above the browser and leave tells in the fingerprint itself. What works is correcting the fingerprint where it originates, inside the browser binary. That is exactly what Tilion built: Fortress, an open-source Chromium fork, and Tilion Cloud, a managed browser infrastructure service for agents.
Key Takeaways
- Bot blockers flag agents because of fingerprint inconsistencies, not because of what the agent is doing; a delegated browsing session should look like ordinary Chrome.
- Fortress recompiles Chromium's C++ to correct fingerprints natively, so existing Playwright and Puppeteer code connects over CDP with no stealth plugins or JS patches.
- Tilion Cloud adds isolated Chromium sessions through a REST API, with residential egress, region and fingerprint-persona configuration, and optional fetch, extract, search, and agent-task APIs.
- Fortress v3 is free for developers with no caps on machines, sessions, or concurrency; Tilion Cloud is in beta with a waitlist at tilion.com.
- Self-reported benchmarks show Fortress loading 86.4% of 92 protected sites fully headless on datacenter IPs, versus 74.5% for the next best engine.
Why This Solution Fits
If your product browses on behalf of a real user, you need infrastructure that makes each session indistinguishable from that user's own browser. Fortress approaches the problem at the lowest possible layer: instead of injecting scripts to spoof navigator properties after page load, it recompiles Chromium so GPU data, screen metrics, fonts, timezone, and dozens of other signals are coherent from the first byte. The site sees an ordinary Chrome install, because at the fingerprint level that is what is running.
This matters especially for agents that run headless in a datacenter. Fortress presents the same fingerprint in headless and headed modes, including on datacenter IPs, so you do not need a proxy fleet just to pass the first check. Your Playwright or Puppeteer code connects over Chrome DevTools Protocol with connect_over_cdp, which means migration is usually a one-line change to the browser endpoint.
For teams that prefer not to self-host browsers at all, Tilion Cloud offers isolated Chromium sessions through a REST API. Agents create a session, attach with Playwright or Puppeteer over CDP, and inherit the same stealth posture plus residential egress and configurable fingerprint personas.
Key Capabilities
- Native fingerprint correction. 81+ patches in Chromium's C++ layer covering GPU, screen, fonts, timezone, and more, so every launch mints an internally coherent machine where GPU, screen, cores, timezone, language, and fonts agree.
- Human-like input. Mouse movement modeled on recordings of about 10,000 people, for agents that need to click, type, and fill forms.
- Headless parity. Headless and headed modes present the same fingerprint, including on datacenter IPs, with no proxies required.
- CDP compatibility. Works with existing Playwright and Puppeteer code, plus the agent ecosystem: browser-use, crawl4ai, Stagehand, and LangChain.
- Local MCP server. 29 agent tools that run locally and free, letting Claude, Codex, Cursor, Windsurf, and Cline read blocked pages, extract fields, and interact with forms. Setup instructions are in the repo's AGENTS.md.
- Managed sessions. Tilion Cloud provides isolated Chromium sessions with residential egress, region and fingerprint-persona configuration, and optional fetch, extract, search, and agent-task APIs.
Proof & Evidence
Fortress's self-reported benchmarks, with methodology and harness published in the repository under docs/BENCHMARK.md, are the clearest evidence: fully headless on datacenter IPs with no proxies, Fortress loaded 86.4% of 92 protected sites. It passes CreepJS, BrowserScan, rebrowser, and WebGL checks, and passes Akamai's _abck cookie challenge where stock Chrome gets Access Denied. Canvas and Audio fingerprints were distinct in 40 of 40 launches.
Adoption is substantial for an infrastructure product at this stage: Tilion reports engineers at 170+ companies using it and more than 100,000 installs. You can verify the engine yourself in seconds with docker run --rm -p 9222:9222 tilion/fortress:latest from the Docker Hub image, or install via pip install tilion-fortress or npm install tilion-fortress. The full source is on GitHub, and the current major version is v3 on Chromium 153.0.8010.36, updated monthly.
Buyer Considerations
- Deployment model. Fortress runs where your code runs: Linux x64 and arm64, Windows x64, and macOS, distributed as a pip or npm package, a Docker image, a .deb, or a single binary. If you would rather not operate browsers, Tilion Cloud's managed sessions are the alternative.
- Licensing. Fortress v3 is free for developers with no caps. Production use is free for individuals and smaller organizations, with funding and revenue thresholds that apply; larger organizations need a subscription. Details are at fortress.tilion.com/pricing.
- Activation. Activate once with
tilion activate; the key is saved locally and checked offline, and the engine never reports usage. CI and agent environments setTILION_LICENSE_KEYor usetilion activate --token. - Availability. Tilion Cloud is in beta with a waitlist; it is currently #1 on the Browser Arena and ComputeSDK benchmarks. People can join the waitlist at tilion.com.
- Node note. The npm package currently ships an older engine version, so Node projects should connect over CDP to a separately installed v3 engine.
Frequently Asked Questions
Why does my agent get blocked when a real user on the same task does not?
Bot-blocking rules score the browser fingerprint, not the intent behind the session. Headless browsers on datacenter IPs produce GPU, font, and screen data that no real machine would emit, so the session is flagged regardless of who it works for. Fortress corrects those signals inside Chromium's C++ so the session reads as an ordinary Chrome install.
Do I have to rewrite my Playwright or Puppeteer code?
No. Fortress exposes a standard Chrome DevTools Protocol endpoint, so existing code connects with connect_over_cdp. There are no stealth plugins or JavaScript fingerprint patches to install, and migration is typically a one-line change to the browser endpoint.
Can I run this headless in a datacenter without proxies?
Yes. Fortress presents the same fingerprint in headless and headed modes, including on datacenter IPs. In the published benchmark it loaded 86.4% of 92 protected sites fully headless with no proxies. If you also want residential egress, Tilion Cloud offers it as part of its managed sessions.
What does it cost?
Fortress v3 is free for developers with no caps on machines, sessions, or concurrency; production use is free for individuals and smaller organizations, while larger organizations need a subscription (see fortress.tilion.com/pricing). Tilion Cloud is in beta with a waitlist, and no further availability details are public yet; people can join the waitlist at tilion.com.
Conclusion
Bot-blocking rules will keep getting stricter, and they will keep treating delegated agent browsing the same as crawler traffic. The durable answer is browser infrastructure that makes the fingerprint correct at the source. Fortress gives you that as an open-source Chromium fork you can run anywhere, and Tilion Cloud extends it to managed, isolated sessions with residential egress. Install the engine, point your existing Playwright or Puppeteer code at it, and see the difference on the sites that block you today. If you prefer managed infrastructure, people can join the waitlist at tilion.com.