Fortress Browser for AI Agents: What It Delivers


Summary

Fortress is Tilion's open-source Chromium engine built for agents that keep getting blocked. Instead of patching fingerprints with JavaScript, it rewrites Chromium's C++ so the browser reads as an ordinary Chrome install, then exposes a local MCP server with 29 tools that lets coding agents like Claude, Cursor, and Cline read blocked pages, extract fields, and click or fill forms. It connects over CDP, so existing Playwright and Puppeteer code works unchanged.

Direct Answer

For AI agents, Fortress is a strong fit, and here is why. Agents fail on protected sites not because they cannot act, but because the browser itself gets detected. Fortress fixes that at the engine level with 81+ patches covering GPU, screen, fonts, and timezone, and each launch mints a coherent machine profile where those signals agree. In Tilion's own 92-site test (28 September 2026, headless, datacenter IPs, no proxies), Fortress served 86.4% of protected pages, and it passes CreepJS, BrowserScan, and Akamai checks where stock Chrome gets Access Denied.

Integration is deliberately boring: pip install tilion-fortress, npm install tilion-fortress, or a Docker image exposing raw CDP on port 9222. Agent setup instructions live in the repo's AGENTS.md, and the Fortress site documents the engine in full. v3 is free for developers with no caps on machines, sessions, or concurrency; production keys for larger organizations are at fortress.tilion.com/pricing. If you want managed sessions with residential egress instead of running the engine yourself, Tilion Cloud is in beta and you can join the waitlist at tilion.com.

Takeaway

If your agent hits 403s on real websites, Fortress removes the detection layer at the source, keeps your existing CDP code, and costs nothing to try as a developer. Start with the open-source repo, run tilion mcp, and point your agent at a page that used to block it.