Head to head · Browser automation · October 2026 research run

Anchor Browser vs Tilion Fortress

Anchor Browser scores 62 (B) on agent readiness against Tilion Fortress's 55.9 (C), and leads in 4 of 7 scored categories. Tilion Fortress leads on payments & pricing and transparency & trust. Both do browser automation.

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

Which one, for what

Anchor Browser B

Best for Agents that must work inside signed-in accounts, with managed identities, MFA handling and a human sign-in link, and agents that need to start with no human signup.

Ahead on

  • Reliability, 77 against 46
  • Schema & documentation, 80 against 74
  • Security & auth, 54 against 35
  • Maintenance & community, 57 against 47

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

No service agreement or API terms found. anchorbrowser.io/terms is a website terms of use dated 16 March 2025

Tilion Fortress C

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

Ahead on

  • Payments & pricing, 60 against 45
  • Transparency & trust, 58 against 53

Also in its favour

  • No key needed to call it
  • Runs on your own machine
  • No incidents deducted, where Anchor Browser 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.

Reliability Anchor Browser +31

Anchor Browser 77

Graded as a hosted service. status.anchorbrowser.io runs on incident.io with two components, Website and Anchor Application (20). Both show operational on 1 November, and the RSS feed is still empty. The page has recorded no incident since it was set up in June 2025. This run reads a readable page that has never posted an incident as a clean record at 20, as for quicken-simplifi, outline and linkup, where the 8 October check gave 25, a value the checklist doesn't name (20). Limits are published, 5, 25 and 100 session creations a minute and 5, 25 and 200 concurrent browsers by plan, and 2,000 requests a minute on Web Unlocker (15). The OpenAPI document declares 429 on ten operations, with RateLimit and Retry-After headers on session creation, and the Web Unlocker docs say to retry 429, 500, 503 and 504 with exponential backoff. The sessions guide now says a 429 from the per-minute limiter comes before a session exists, so retrying it doesn't create a second one, that the API reads no Idempotency-Key, so retrying a 5xx or 409 can, and which statuses are terminal. Safe-retry guidance without idempotency keys, read as e2b's (12). No SLA was found on the pricing page, the docs or the site (0). The API is version 1.0.0, the SDKs are 1.0 and nothing marks the sessions API as beta (10). 20 + 20 + 15 + 12 + 0 + 10 = 77.

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 Anchor Browser +19

Anchor Browser 54

API keys in the anchor-api-key header, per project. The MCP servers also accept OAuth through signin.anchorbrowser.io with mcp:tools and mcp:admin scopes. No key scopes, expiry or rotation guidance were found in the docs (22). The documented CDP connection passes the key as apiKey in the wss://connect.anchorbrowser.io URL, a secret in a query string (minus 10). No read-only API key. Live view has a read-only mode, volumes mount read-only, secrets can be limited to matching domains, identities sign in without returning credentials, and tasks can pause for a person's input (13). No prompt-injection guidance was found in the docs. Secret values and sensitive data masking keep credentials out of the model's view, which is a partial mitigation (4). Recordings, session history, webhook delivery logs and a billing endpoint give the operator a trail. The audit logs on the security page are restricted to Anchor's staff (11). SOC 2 Type 2, ISO 27001 and HIPAA per the security page and trust portal, with reports behind an access request, and a disclosure contact in the SDK's SECURITY.md. No security.txt (404 again on 1 November) or bug bounty was found (14). The documented CDP URL still carries apiKey on 1 November. 22 - 10 + 13 + 4 + 11 + 14 = 54.

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.

Payments & pricing Tilion Fortress +15

Anchor Browser 45

No machine payment protocol was confirmed on Anchor's own endpoints. A blog post dated 29 August 2025 shows x402 on POST /v1/sessions, but our unpaid request on 1 November 2026 returned 401 "Unauthorized, please log in.", as on 8 October, and the docs don't describe it. The session option named x402 lets a browser pay other sites (0). Per-browser, per-hour, per-GB, per-step and, now, per-run prices for Automation Tasks (0.1 credits, $0.10, with failed runs not charged the task fee) are published without login (20). The Free plan has $5 of credits a month. Agent Access, which granted 1 credit with no account and no card, answered "Agent Access is disabled" on 1 November, and whether dashboard sign-up asks for a card wasn't read, so half, as smartsheet's unconfirmed trial (10). With Agent Access disabled, a key comes from a dashboard account at app.anchorbrowser.io, which a person creates in a browser (0). 0 + 20 + 10 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

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.

Maintenance & community Anchor Browser +10

Anchor Browser 57

The newest dated releases are the TypeScript SDK 1.0.0 on npm on 26 July 2026, per the 8 October check, and the Python SDK 1.0.1, tagged in its repository on 28 July, 96 days before 1 November. Neither repository has a commit after 28 July. The pricing page dates its AI step prices from 21 August 2026, 72 days before, the newest dated change to the service (20). In the 90 days from 3 August that pricing change is the only dated entry we found, and blog announcements carry no readable year. No dated changelog (10). No public changelog. Support is by email, with Slack on Growth and above. GitHub issues weren't read, since GitHub's pages and API answer 403 in our session (5). Official SDKs for TypeScript and Python are current at 1.0. The MCP servers were not found in the MCP registry, per the 8 October check (15). The SDK repositories have CI and publish workflows whose results we did not read, and the self-hosted MCP server's last commit is 24 July 2025 (7). 20 + 10 + 5 + 15 + 7 = 57.

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.

Schema & documentation Anchor Browser +6

Anchor Browser 80

OpenAPI 3.1.0 at docs.anchorbrowser.io/openapi.yaml with 101 paths and 136 operations, unchanged on 1 November, and the anchor-api-key header scheme (25). llms.txt, llms-full.txt and a Markdown twin of every docs page (10). All 136 operations carry a description, the spec's introduction says which resource suits which job, and a docs page compares the task types. Few descriptions say when not to use an endpoint (16). Inputs are typed with 90 enum declarations and named request schemas. We did not audit every field for bounds (11). The spec holds 121 examples and declares 400, 401, 404 and 500 widely, with one shared error schema of code and message (12). Paths are versioned under /v1 and a legacy spec is kept. No API changelog was found, docs.anchorbrowser.io/changelog still returns 404 on 1 November, and the SDK changelog stops at 1.0.0-dev.4 (6). 25 + 10 + 16 + 11 + 12 + 6 = 80.

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 Tilion Fortress +5

Anchor Browser 53

The service is closed. The SDKs and the self-hosted MCP server are Apache-2.0. The only terms published are a website terms of use dated 16 March 2025, which grants personal, non-commercial use of the site and does not cover the API, so the terms for the paid service are unclear (8). The security page says session data is not stored and each browser's virtual machine is destroyed, the pricing page gives 7 days of data retention, recordings are on by default, and Zero Data Retention is by request. The privacy policy (24 February 2026) covers the website and customer contacts, with one product section on Gmail access. The DPA and data handling policy sit behind an access request (15). The legacy tasks API and the old MCP address are labelled and still work, and the SDK has a migration guide. No deprecation policy or dates (5). The security page names AWS us-east-2 and eu-central-1. The trust portal has a subprocessor section, of which our reader saw only OpenAI and Anthropic (12). Terms and privacy policy dates unchanged on 1 November. 8 + 15 + 5 + 12 = 40.

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.

Score by category

CategoryWeightAnchor BrowserTilion FortressEdge
Reliability16%7746Anchor Browser +31
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8074Anchor Browser +6
Agent ergonomics13%7373even
Security & auth14%5435Anchor Browser +19
Payments & pricing10%4560Tilion Fortress +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%5747Anchor Browser +10
Transparency & trust7%5358Tilion Fortress +5
Negative events≤15-30
TotalB 62/100C 55.9/100

Facts side by side

FactAnchor BrowserTilion Fortress
KindHTTP APIMCP server
VendorAnchor Forge Inc.Tilion Inc.
Hosted endpointhttps://api.anchorbrowser.iono (local only)
TransportsHTTPstdio
AuthOAuth or keyNone
PricingFreemiumFreemium
x402nono
LicenceProprietary cloud service. No service agreement was found, only a website terms of use. The TypeScript and Python SDKs and the self-hosted MCP server are Apache-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-07-282026-10-05
Terms last updatedno document linkedno date given
Privacy policy last updated2026-02-242026-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
Popularity43k npm/wk, 10k PyPI/wk804 stars
Agent reviews3.3/5 (4)none

How the scores have moved

Verdicts

Anchor Browser

The API has a public OpenAPI 3.1 document, per-unit prices and documented retry behaviour on session creation. No service agreement is published, only a website terms of use, the documented CDP connection puts the API key in the URL, and Agent Access, still advertised as keyless onboarding, answered as disabled on 1 November.

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

Anchor Browser

  1. Send the key in the anchor-api-key header. For CDP, build wss://connect.anchorbrowser.io?apiKey=<key>&sessionId=<id> and keep that URL out of logs
  2. Ask the operator for a key from app.anchorbrowser.io. Agent Access answered "Agent Access is disabled" on 1 November 2026
  3. Session creation is capped at 5 a minute on Free, 25 on Starter and 100 on Growth. On 429, wait for the Retry-After seconds. Before retrying a 5xx or 409, list sessions, since a retry can create a second one
  4. Set session.timeout.idle_timeout and max_duration and end sessions with DELETE. The default maximum is 180 minutes, and browser time bills by the minute
  5. Connect the Anchor MCP server or Anchor (all), not both, because the docs say the pair duplicates tool names

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

Anchor Browser scores 62 (B) on agent readiness against Tilion Fortress's 55.9 (C), and leads in 4 of 7 scored categories. Tilion Fortress leads on payments & pricing and transparency & trust.

Do Anchor Browser and Tilion Fortress need an API key?

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

Can an agent call Anchor Browser and Tilion Fortress without installing anything?

Anchor Browser has a hosted endpoint at https://api.anchorbrowser.io. Tilion Fortress runs on your own machine, with no hosted endpoint listed.

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