Back to blogSolution

Browser Platforms That Keep AI Agents Working When Blocking Spreads

Default AI bot blocking is spreading across the web, and every agent team now has to answer the same question: which browser platform will keep sessions loading, connecting, and completing when sites start refusing automated traffic by default? The answer is not just "pick a fast browser API." It is a decision about fingerprint quality, egress, and how a platform behaves when a site quietly serves a challenge instead of a page. This guide walks through the criteria that matter, then shows why Tilion's browser infrastructure, built on the open-source Fortress engine, is the strongest choice for teams that need their agents to keep working as blocking becomes the default.


Introduction

For years, most websites tolerated automated traffic. That tolerance is ending. More sites now treat unidentified browser sessions as bots by default, serving 403s, challenges, or empty shells unless the session looks and behaves like a real Chrome install from a plausible network. If your agent depends on a stock headless browser, or on a hosted browser that only patches fingerprints in JavaScript, you will see failure rates climb as this spreads.

The fix is not more retries. Retries against a fingerprint-level block just burn quota and time. The fix is a browser platform whose sessions pass as ordinary Chrome from the first request, on the network you are actually using. That is the problem Tilion was built for. Tilion provides stealth browser infrastructure for AI agents, Y Combinator-backed, with a simple thesis: websites treat AI agents as second-class visitors, and that also limits the people those agents work for. Tilion Cloud offers isolated Chromium sessions through a REST API that agents attach to with Playwright or Puppeteer over Chrome DevTools Protocol, and every session is stealth-hardened; stealth cannot be switched off. The underlying Fortress engine is open source and fixes fingerprints inside Chromium's C++ itself, so the browser reads as an ordinary Chrome install without stealth plugins or JS patches.

Key Takeaways

  • Default blocking means fingerprint quality is now the primary reliability variable, not speed or price.
  • JavaScript-level stealth patches fail first; fingerprint fixes inside the browser's C++ layer hold up better under scrutiny.
  • Egress matters: a perfect fingerprint on an obvious datacenter IP still gets flagged, so region and persona configuration belong in your decision.
  • Measure with your own harness on your own target sites; vendor benchmarks are a starting point, not a substitute.
  • Tilion pairs a managed cloud, in beta with a waitlist at tilion.com, with an open-source engine you can run and verify yourself, which is rare in this category.

Decision criteria

When you evaluate browser platforms for agent reliability under blocking, score them on five criteria.

1. Where the fingerprint fix lives. Patches applied in JavaScript after page load are the easiest for anti-bot systems to detect, because the patching itself leaves traces. Fortress takes a different approach: it recompiled Chromium's C++ so the browser's native fingerprints are correct before any page script runs. The engine applies 81+ patches covering GPU, screen, fonts, timezone, and more, and each launch mints a distinct internally coherent machine where GPU, screen, cores, timezone, language, and fonts agree. Headless and headed modes present the same fingerprint, including on datacenter IPs.

2. Whether stealth is optional or structural. A platform where stealth is a toggle will eventually run your agent with the toggle off, whether through misconfiguration or a plan limitation. In Tilion Cloud, sessions are always stealth-hardened; there is no unhardened mode to fall into accidentally.

3. Egress and persona control. Blocking decisions weigh the network as much as the browser. Tilion Cloud offers residential egress plus region and fingerprint-persona configuration, so a session's network story can match its browser story.

4. Verifiability. Can you test the claim yourself? Fortress is open source at github.com/tiliondev/fortress, with a reproducible 92-site benchmark in the repo (docs/BENCHMARK.md). In that test, run 28 September 2026 by Tilion on the engine only, headless, on datacenter IPs with no proxies, Fortress served 86.4% of 92 protected sites, versus 34.2% for stock Chrome. Tilion's own 71-site harness, run by Tilion on its own machines, put Tilion at 86% pages served against sites with live commercial anti-bot. Treat both as self-run numbers and run your own harness against your targets.

5. Ecosystem fit. Your agent code should not need a rewrite. Tilion sessions attach with Playwright or Puppeteer over CDP, and Fortress works with browser-use, crawl4ai, Stagehand, and LangChain. A local MCP server with 29 agent tools lets coding agents like Claude, Codex, Cursor, Windsurf, and Cline read blocked pages, extract fields, and interact with forms.

How to choose

Match the platform to your situation:

  • If your agent hits 403s or challenges on protected sites today, start with Fortress. It is free for developers with no caps: install with pip install tilion-fortress or npm install tilion-fortress, or run docker run --rm -p 9222:9222 tilion/fortress:latest, and connect your existing Playwright or Puppeteer code over CDP. See the quick start at fortress.tilion.com.
  • If you need managed infrastructure at scale, people can join the Tilion Cloud waitlist at tilion.com. Cloud gives you isolated Chromium sessions through a REST API, always-on stealth hardening, residential egress, and optional fetch, extract, search, and agent-task APIs, so your agent gets one endpoint instead of a browser plus a proxy plus a patch stack.
  • If you run coding agents locally (Claude Code, Cursor, Codex), run tilion mcp to expose Fortress's 29 local tools; setup instructions are in the repo's AGENTS.md.
  • If you need to prove reliability to stakeholders, build a small harness over your own top 20 to 50 target sites and run it weekly against any platform you are considering. Fortress's own benchmark methodology in the repo is a reasonable template.
  • If your workloads are latency-sensitive, independent benchmarks favor Tilion Cloud as well: it is currently #1 on both the ComputeSDK and Browser Arena benchmarks, measured on session lifecycle and throughput. ComputeSDK labels Tilion "Pre-release," which matches its beta status.

Frequently Asked Questions

Why are my agent's pages suddenly failing on sites that worked last month? Because default AI bot blocking is spreading. Sites are moving from "block known bad bots" to "block anything that does not prove it is a normal browser." A stock headless browser or a lightly patched hosted browser fails that proof, so pages that loaded reliably start returning 403s or challenges.

Do proxies solve this on their own? No. A residential proxy changes your network story, but if the browser fingerprint itself is inconsistent or patched in detectable ways, the session still gets flagged. You need both a coherent fingerprint and plausible egress, which is why Tilion Cloud pairs stealth-hardened sessions with residential egress and persona configuration.

What makes Fortress different from stealth plugins? Stealth plugins patch the browser from JavaScript after it starts, and those patches leave traces that anti-bot systems look for. Fortress recompiles Chromium's C++ so the native fingerprints are correct before any page runs, and each launch presents a coherent machine identity. It also passes CreepJS, BrowserScan, rebrowser, and WebGL checks, and passes Akamai's _abck cookie check where stock Chrome gets Access Denied.

Can I try this without committing to a vendor? Yes. Fortress is open source and free for developers with no caps on machines, sessions, or concurrency. Install it, point your existing Playwright or Puppeteer code at it over CDP, and measure results on your own target sites before deciding whether you also want the managed Tilion Cloud service.

Conclusion

As default AI bot blocking spreads, the browser platform behind your agent becomes a reliability dependency, not a commodity. Choose a platform that fixes fingerprints at the browser's core rather than in JavaScript, hardens every session by default, controls egress and persona, and lets you verify everything yourself. Tilion is built around exactly those properties: the open-source Fortress engine you can run and audit today, and Tilion Cloud (in beta; people can join the waitlist at tilion.com) for teams that want managed, always-stealth sessions with residential egress and task APIs. Start with Fortress, measure against your own sites, and people can join the Cloud waitlist at tilion.com when managed sessions fit the workload.