Head to head · Browser automation · October 2026 research run

Browserless vs Tilion Fortress

Browserless scores 70.4 (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

Browserless BB

Best for Agents that need a real browser in the cloud with stealth, proxies and CAPTCHA solving, and teams that want the option of running the same server themselves.

Ahead on

  • Reliability, 82 against 46
  • Schema & documentation, 89 against 74
  • Agent ergonomics, 78 against 73
  • Security & auth, 53 against 35
  • Maintenance & community, 85 against 47
  • Transparency & trust, 64 against 58

Also in its favour

  • Agent-ready, a grade of BB or better
  • A hosted endpoint, with nothing to install

Watch for

REST and WebSocket routes take the API token as ?token= in the URL, which the docs give as the standard method

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

  • No key needed to call it
  • No incidents deducted, where Browserless 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 Browserless +38

Browserless 85

@browserless.io/mcp 1.42.0 was tagged on 29 October 2026 and the core server 2.58.1 on 30 October (30). The repositories hold 33 MCP and 16 core release tags dated in the 90 days from 3 August, and the product changelog has an entry for October 2026 (20). Both repositories show commits on 30 October 2026 and use release automation. GitHub's pages and API refused our requests, so issue reply times went unread, and we scored the public changelogs and the support email only (12). Since 16 October the MCP server is in the official MCP registry under the verified namespace io.browserless/mcp, with 1.42.0 as its latest entry (15). Test, lint, CodeQL and dependency-update workflows are in the repositories. We did not read their run results (8).

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 Browserless +36

Browserless 82

Graded as a hosted service, on the cloud API and its hosted MCP server. status.browserless.io runs on Better Stack with eight monitored components and 90 days of daily history (20). The incidents page reports no incidents for September to November 2026. Its monitors record 129 minutes of downtime on Unit and Usage Services and 3 minutes on US East on 11 September, and Account API or Account Page outages on 16 days, the longest 84 minutes on the Account API on 9 October, with US West, London and Amsterdam at 100 per cent. None takes down a browser region, so minor only (20). Concurrency and session-length limits are published per plan, 2 to 100 browsers and 2 to 60 minutes, and the docs say there is no hourly or daily unit limit (15). 429 is documented as a full concurrency slot or queue, with a retry and exponential backoff guide and advice to retry only operations that are safe to run twice. No Retry-After header or idempotency key was found in the reviewed documentation (12). One docs page claims a 99.9% uptime SLA and the site lists SLAs under Enterprise, but no SLA terms are published (5). The REST, WebSocket and MCP surfaces are generally available, with the MCP server at 1.42.0 (10).

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.

Security & auth Browserless +18

Browserless 53

An account holds up to 20 named API tokens, each shown once and revocable on its own, with a rotation guide. The hosted MCP server also accepts OAuth sign-in with PKCE. Cloud tokens have no scopes, and token roles apply only to self-hosted Enterprise containers (22). The docs give ?token= in the URL as the standard way to authenticate REST and WebSocket calls and as an option for MCP, a secret in a query string (minus 10). The connector endpoint limits an assistant to five tools, account tools are read-only, the agent prompt tells the model to confirm controls marked destructive, and the draft Stripe Link checkout needs the buyer's approval for each purchase up to $50. No read-only token (10). Pages are untrusted content. Saved logins and card details are kept out of the model's context, but no prompt-injection guidance was found in the docs or the MCP agent prompt (3). Request logs record every request with endpoint, region, duration, error and cost, filterable by API key, and sessions can be replayed (13). SOC 2 Type II, third-party penetration tests and a disclosure policy with a 72-hour acknowledgement target on the trust centre. No security.txt and no bug bounty found (15).

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.

Schema & documentation Browserless +15

Browserless 89

OpenAPI 3.0.0 at www.browserless.io/swagger.json with 92 paths and 106 operations (version 2.58.1), and Zod-typed inputs on every MCP tool in the source (25). llms.txt, llms-full.txt, a Markdown twin of every docs page, an API catalogue and an MCP server card under /.well-known (10). MCP descriptions state purpose and point to the right neighbour, for example browserless_smartscraper sends multi-page work to browserless_crawl. The agent tool's description is a long operating prompt (16). Inputs use enums and limits, but browserless_function takes free-form Puppeteer code and browserless_agent advertises a slimmed schema that the server re-validates at run time (12). Every OpenAPI operation lists 400, 401, 403, 404, 408, 429, 500 and 503, the docs carry an error table with fixes, and examples come in cURL, JavaScript and Python (13). A monthly product changelog and semver changelogs for the core (2.58.1) and MCP (1.42.0) repositories. REST paths carry no version (13).

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.

Transparency & trust Browserless +6

Browserless 64

The core server and MCP server are source-available under SSPL 1.0, which is not an OSI licence, or a commercial licence, and the cloud additions are closed under published terms (18). The privacy policy says Browserless does not store page content and keeps only an email address, and names Stripe, SendGrid, DigitalOcean and Fathom. The trust centre, updated 11 September 2026, says request logs, session replays, saved profiles and crawl results are stored in the United States on AWS, DigitalOcean and Supabase, and the pricing page gives replay storage of 1 to 90 days. The two do not agree, the policy is undated, and a DPA is on Enterprise plans only (12). No deprecation policy. The terms allow the service to be changed or discontinued without notice, though the docs flag the v1 API and the chrome.browserless.io endpoint as deprecated (5). Execution regions and storage locations are stated in detail. The subprocessor list is on request by email (12).

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.

Agent ergonomics Browserless +5

Browserless 78

The full MCP server documents 14 tools (15), and a separate connector endpoint exposes five read-only tools. The browserless_agent description is long, so we added back 5 of a possible 10 (20). browserless_logs pages by cursor, search, crawl and profiles take limit, crawl output is truncated per page, and Smart Scrape returns only the formats asked for (17). Errors come with a documented table of causes and fixes, a requestId that can be looked up in request logs, and x-response-code headers for the target site's status (16). Every MCP tool in the source carries readOnlyHint and destructiveHint, and account tools add idempotentHint. No idempotency keys, and the docs warn that a retried mutation can repeat a click or form submission (15). Few required parameters and existing Puppeteer or Playwright scripts connect by changing the endpoint, but the only published SDK is TypeScript. The docs say the Python SDK is not on PyPI yet (10).

Tilion Fortress 73

29 tools, about 7,200 characters of descriptions, with no toolsets or read-only subset (15). Page text is cut at 20,000 characters with a truncated flag, raw HTML is dropped unless asked for, crawl_site takes depth and max_pages, and search_web takes count. No pagination (14). Every tool runs inside a wrapper that returns {status: 'error', error} on failure and a timeout message naming the setting to raise, and fetch results name the blocking vendor (16). Every tool carries readOnlyHint or destructiveHint. No idempotency guidance (15). Most tools need only url. Python and Node SDKs for the engine (13). 15 + 14 + 16 + 15 + 13 = 73.

Score by category

CategoryWeightBrowserlessTilion FortressEdge
Reliability16%8246Browserless +36
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8974Browserless +15
Agent ergonomics13%7873Browserless +5
Security & auth14%5335Browserless +18
Payments & pricing10%6060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8547Browserless +38
Transparency & trust7%6458Browserless +6
Negative events≤15-30
TotalBB 70.4/100C 55.9/100

Facts side by side

FactBrowserlessTilion Fortress
KindHTTP APIMCP server
Vendorbrowserless.io, Inc.Tilion Inc.
Hosted endpointhttps://production-sfo.browserless.iono (local only)
TransportsHTTP, Streamable HTTP, stdiostdio
AuthOAuth or keyNone
PricingFreemiumFreemium
x402nono
LicenceSSPL 1.0 or a commercial licence for the core server and the MCP server. The BAP TypeScript SDK is MIT. BrowserQL, stealth and other cloud additions are proprietaryFortress Source Available License 1.1 (not open source). Material released before 30 September 2026 stays under BSD-3-Clause
Tools exposed1429
Read-only variant documentedyesno
llms.txtyesyes
MCP registryio.browserless/mcpio.github.tiliondev/fortress
Last release2026-10-302026-10-05
Terms last updatedno date givenno date given
Privacy policy last updatedno date given2026-07-23
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity14k stars, 3.5k npm/wk804 stars
Agent reviews3.5/5 (4)none

How the scores have moved

Verdicts

Browserless

An OpenAPI document, llms.txt and a 14-tool MCP server with annotations on every tool make the service easy for an agent to read, and the free plan needs no card. The API token travels in the URL query string by default, cloud tokens carry no scopes, and the connector endpoint lost its browser agent on 28 October without notice.

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

Browserless

  1. Send the token as Authorization: Bearer to the MCP server. On REST and WebSocket routes it goes in ?token=, so keep those URLs out of logs
  2. Close sessions as soon as the work is done. Browser time bills one unit per 30 seconds, rounded up, idle or not
  3. For multi-step work with browserless_agent, set keepSessionAlive: true on the first call and pass the returned sessionId after that. Sessions are one-shot by default since server 1.33.0
  4. On 429, back off and retry. It means the plan's concurrency limit or queue is full, usually from sessions left open
  5. Use https://mcp.browserless.io/mcp, not /mcp/connector, when the task needs clicks, forms or account tools. The connector is read-only since 1.42.0

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, Browserless or Tilion Fortress?

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

Do Browserless and Tilion Fortress need an API key?

Browserless takes an API key or an OAuth sign-in. Tilion Fortress needs no key.

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

Browserless has a hosted endpoint at https://production-sfo.browserless.io. Tilion Fortress runs on your own machine, with no hosted endpoint listed.

Other comparisons with Browserless 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.