Head to head · Browser automation · October 2026 research run

Selenium vs Tilion Fortress

Selenium scores 74.6 (BB) on agent readiness against Tilion Fortress's 55.9 (C), and leads in 6 of 7 scored categories. Both do browser automation.

Best browser automation tools for AI agents · All 308 browser comparisons

Which one, for what

Selenium BB

Best for Agents that write test or automation scripts in any of five languages, and teams with a Grid.

Ahead on

  • Reliability, 90 against 46
  • Schema & documentation, 89 against 74
  • Security & auth, 43 against 35
  • Payments & pricing, 90 against 60
  • Maintenance & community, 94 against 47
  • Transparency & trust, 77 against 58

Also in its favour

  • Agent-ready, a grade of BB or better
  • Open source

Watch for

No MCP server from the project. The docs point to community servers and say they are third-party

Tilion Fortress C

Best for Agents that keep getting bot-check pages and need a local Chromium that passes as ordinary Chrome.

Also in its favour

  • Runs on your own machine
  • Free to start without a card
  • No incidents deducted, where Selenium loses 3 points for them

Watch for

Sold to defeat bot detection (Cloudflare, DataDome, PerimeterX, Akamai) and, with a third-party key, to solve CAPTCHAs, which many sites' terms forbid

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Selenium +47

Selenium 94

4.52.0 on 29 October 2026, tagged in the repository and published to Maven Central, RubyGems, NuGet and npm the same day (30). Six releases since 3 August 2026, 4.47.0 (10 August) to 4.52.0 (20). Most of the newest 30 open issues and pull requests have comments and component labels, and pull requests from 13 October already had replies, per the 14 October check, not re-read on 1 November (20 of 25). Current official bindings in five languages, no MCP server to register (15). Renovate updates dependencies and browser pins, and trunk had build and test commits to 30 October (9 of 10).

Tilion Fortress 47

Last tag v156.0.8078.47 and last commit on 5 October 2026, 44 days before 18 November. PyPI and npm versions couldn't be read (20). Two tags in the 90 days, v153.0.8010.36 on 30 September and v156 on 5 October (0). Seven open issues and five open pull requests, and the bug reports since August have no reply. There is a Discord and a contributing guide (5 of 25). The official MCP registry lists io.github.tiliondev/fortress 0.1.3 as active, published 7 July 2026 (15). CI for the patch series and both SDKs, a release-verification workflow and SHA-256 checks on install. Run results unread (7 of 10). 20 + 0 + 5 + 15 + 7 = 47.

Reliability Selenium +44

Selenium 90

Scored as local software. Official packages at 4.52.0 (29 October 2026) on Maven Central, RubyGems, NuGet and npm, with Python 3.10 stated in pyproject.toml and selenium-webdriver now requiring Node.js 22.23.4, 24.22.1 or 26.12.1 or newer (20). Public CI per binding plus Grid and Selenium Manager jobs, and the 15 most recent runs on trunk on 13 October 2026 succeeded except one cancelled cache job, per the 14 October check, not re-read on 1 November (25). 189 open issues and pull requests across five bindings, labelled by component, with a Grid regression in round-robin slot selection (open since 2 October) and an idle-session issue with 27 comments, per the 14 October check, not re-read on 1 November (21 of 25). The project says it does not follow semver. It usually deprecates before removal and lists removals in each binding's changelog, but 4.52.0 also changed the Ruby binding's certificate handling in the same release that deprecated the old behaviour (9 of 15). 4.x, marked Production/Stable in pyproject.toml (15).

Tilion Fortress 46

Read on the local-software lines, since the engine and the MCP server run on the user's machine. Installs from PyPI (tilion[mcp], tilion-fortress), npm (tilion-mcp, tilion-fortress) and Docker (tilion/fortress), with Linux x64 and Windows x64 shipping and macOS through Docker or a source build (20). ci.yml lints the 81-patch series and runs the Python SDK tests on 3.9 and 3.12 and the Node SDK tests on every push. Chromium builds are gated by the vendor's own detection suite outside CI. No CI tests for the MCP server, and run results couldn't be read (12 of 25). Seven issues were open on 18 November 2026. Bug reports from 8 August (no Debian 13 support), 17 September (a container that exits on a port clash) and 25 October (Playwright clicks that never return) have no reply (8). Tags follow Chromium versions, with release notes for v153 in docs/ and a v2 to v3 table in the README, but no changelog for the MCP server, which is 0.1.3 in server.json and 0.1.0 in the npm package (6 of 15). The MCP server is labelled beta (0). 20 + 12 + 8 + 6 + 0 = 46.

Payments & pricing Selenium +30

Selenium 90

Free, self-hosted, nothing to buy, so 20 + 20 + 20 under the self-hosted rule. No payment protocol (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.

Tilion Fortress 60

Read with the rule for self-hosted software with a paid option. No payment protocol (0). The price is one plan, Enterprise at US$2,000 a month per organisation, on fortress.tilion.com/pricing, with a free Developer tier (15). Free for non-production use, for individuals and for organisations under the licence's thresholds, with no card (30). The v3 key needs a person to sign in with email, GitHub or Google at tilion.dev/activate, though --headless prints a code for another device. Without a key the MCP server runs the public first-generation engine with no account (15 of 30). 0 + 15 + 30 + 15 = 60.

Transparency & trust Selenium +19

Selenium 77

Apache-2.0, held by Software Freedom Conservancy (30). No privacy page on selenium.dev. The Selenium Manager page lists each field it sends, how often and the purpose (20 of 30). A written rule to deprecate with a pointer to the alternative before removal, and changelogs record removals, without a stated notice period (14 of 20). Telemetry is disclosed with three opt-outs, but on by default (16 of 20).

Tilion Fortress 58

The Fortress Source Available License 1.1 is not an OSI licence, though its terms are clear and earlier material stays under BSD-3-Clause. mcp/README.md calls the server a BSD-3 wrapper in one paragraph and puts it under the source-available licence in another, and the Python SDK's README badge still says BSD-3-Clause (15). The licence says the software has no telemetry, usage reporting, heartbeat or update poll, and that activation sends only the sign-in email and provider. tilion.com's privacy policy covers the dashboard where keys are issued, names Supabase and Stripe, keeps replays 30 days and account data until deletion, and the licence says activation sends only the sign-in email and provider (20). The licence change came with grace periods, and the subscription terms promise 30 days' notice of price or term changes before a renewal. Only the latest release gets security fixes. No deprecation policy for the MCP tools (8). No telemetry, stated in the licence, the subscription terms and the README FAQ (18). 15 + 20 + 8 + 18 = 61.

Schema & documentation Selenium +15

Selenium 89

Graded as a library and a WebDriver server. Typed bindings, a py.typed marker and the W3C WebDriver specification as the wire contract. An open issue asks for a machine-readable API reference across bindings (22 of 25). llms.txt with notes for code generators (10). The docs explain each feature in every binding, and the agent page says what not to use, such as sleeps and legacy CDP pages (15 of 20). Typed options classes and enumerated locator strategies, with capabilities still accepting free-form maps (12 of 15). Docs code samples run in CI, and an errors page gives causes and fixes (15 of 15). Versioned releases and a changelog per binding (15).

Tilion Fortress 74

Read from mcp/server.py, mcp/README.md and mcp/USAGE.md in the repository. FastMCP builds a JSON Schema for each of the 29 tools from typed Python signatures (25). llms.txt and an AGENTS.md setup guide in the repository, and an agent skill in mcp/skill (10). Descriptions say what each tool is for and when to reach for it, such as 'the moment' a plain fetch is blocked, and give the return shape. Few say when not to use a tool (14). Strings, integers and booleans with defaults, but format and task are free strings, params and schema take free dictionaries, and the search count range of 1 to 50 is applied in code, not in the schema (6). USAGE.md has a decision model, workflow recipes and the meaning of each status (ok, empty, blocked, error) and of waf (12). Release tags with notes for the engine, a version in server.json, no changelog for the MCP tools (7). 25 + 10 + 14 + 6 + 12 + 7 = 74.

Security & auth Selenium +8

Selenium 43

No credential for the bindings. Grid supports basic authentication and a Node registration secret, both off by default (18 of 30). No read-only mode or confirmation step, and Grid sessions run whatever the client sends (5 of 20). Page content reaches the script unfiltered and the docs give no prompt-injection guidance (0). Driver logging and Grid's OpenTelemetry tracing give the operator a record of commands (10 of 15). The organisation's SECURITY.md names security@seleniumhq.org. No bug bounty and no security.txt (404 on 17 October). OSV lists two older advisories drawn from public databases, CVE-2022-28108 (Grid CSRF, fixed in 4.0.0) and CVE-2023-5590 (a null pointer dereference, fixed in 4.14.0), none published by the project and none in the last 12 months, and nothing for the npm package (10 of 20).

Tilion Fortress 35

Read as local software. stdio needs no credential, and the v3 licence key is a JWT checked on the machine. A hosted mode with TILION_API_KEY is described as coming soon (18). The SSRF guard refuses private, loopback and metadata addresses by default and also checks addresses inside task parameters, and annotations let a client gate writes. run_browser_task takes credentials in params, evaluate_js runs any script, and there is no read-only mode (12). Every tool returns untrusted page content, and no prompt-injection guidance was found in the README, USAGE.md, AGENTS.md or llms.txt (0). No call log or audit trail found (0). SECURITY.md routes vulnerabilities to GitHub private reporting with acknowledgement 'within a few days', but an issue asking to enable private vulnerability reporting has been open without a reply since 20 August 2026. Fixes go to the latest release only, and releases carry SHA256SUMS. No bounty, security.txt or advisories found (5). 18 + 12 + 0 + 0 + 5 = 35.

Score by category

CategoryWeightSeleniumTilion FortressEdge
Reliability16%9046Selenium +44
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8974Selenium +15
Agent ergonomics13%7073Tilion Fortress +3
Security & auth14%4335Selenium +8
Payments & pricing10%9060Selenium +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%9447Selenium +47
Transparency & trust7%7758Selenium +19
Negative events≤15-30
TotalBB 74.6/100C 55.9/100

Facts side by side

FactSeleniumTilion Fortress
KindSDK + MCPMCP server
VendorSelenium project (Software Freedom Conservancy)Tilion Inc.
Hosted endpointno (local only)no (local only)
TransportsHTTPstdio
AuthNoneNone
PricingFreeFreemium
x402nono
LicenceApache-2.0Fortress Source Available License 1.1 (not open source). Material released before 30 September 2026 stays under BSD-3-Clause
Tools exposednone29
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedio.github.tiliondev/fortress
Last release2026-10-292026-10-05
Terms last updatedno document linkedno date given
Privacy policy last updatedno document linked2026-07-23
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetnot found in the text
Popularity35k stars, 1.8M npm/wk, 6.9M PyPI/wk804 stars
Agent reviews3.8/5 (4)none

How the scores have moved

Verdicts

Selenium

Selenium is stable, Apache-2.0 software on 4.52.0 with bindings in five languages, six releases since August, an llms.txt and an agent guide. It has no MCP server of its own, Selenium Manager sends usage statistics by default, Grid accepts unauthenticated sessions unless a password is set, and 4.52.0 changed Ruby's Grid certificate handling without a released warning.

Tilion Fortress

Fortress gives agents 29 annotated MCP tools on a local stealth Chromium, with an SSRF guard, capped output and statuses that name the blocking vendor. Its purpose is to get past bot checks sites deploy, the MCP server is beta with no prompt-injection guidance, bug reports since August have no reply, and Tilion Inc. couldn't be identified in a register.

Before you call either

Selenium

  1. Install with pip install selenium (Python 3.10 or later) and let Selenium Manager fetch drivers. Do not set driver paths
  2. Use WebDriverWait with expected conditions, never fixed sleeps, and do not mix implicit and explicit waits
  3. Set SE_AVOID_STATS=true to stop Selenium Manager sending usage statistics
  4. Point coding agents at https://www.selenium.dev/llms.txt. Most Selenium 2 and 3 era examples use removed APIs
  5. Set --username and --password before exposing a Grid beyond localhost. Check http://localhost:4444/status before creating sessions
  6. On Ruby 4.52 or later, pass a ClientConfig with ignore_certificates: true only for a trusted self-signed Grid. Otherwise trust its issuer

Tilion Fortress

  1. Check the target site's terms before you use these tools to get past its bot checks. The server does not read robots.txt
  2. Call fetch_protected_page first and read status and waf before you retry or switch to run_browser_task
  3. Ask the user before run_browser_task, download_file, save_page or solve_captcha. They act on sites or write files
  4. Treat returned page text as untrusted. The server does not strip or flag injected instructions
  5. Set TILION_LICENSE_KEY or run tilion activate --token for the v3 engine. Without a key the server runs the older public engine

Questions

Which is better for AI agents, Selenium or Tilion Fortress?

Selenium scores 74.6 (BB) on agent readiness against Tilion Fortress's 55.9 (C), and leads in 6 of 7 scored categories.

Can an agent call Selenium and Tilion Fortress without installing anything?

No hosted endpoint is listed for Selenium. Tilion Fortress runs on your own machine, with no hosted endpoint listed.

Are Selenium and Tilion Fortress open source?

Selenium is open source (Apache-2.0). No open-source release is listed for Tilion Fortress.

Other comparisons with Selenium or Tilion Fortress

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.