Head to head · Browser automation · October 2026 research run

Steel vs Tilion Fortress

Steel scores 73.1 (BB) on agent readiness against Tilion Fortress's 55.9 (C), and leads in every scored category. Both do browser automation. Steel accepts x402. Tilion Fortress doesn't.

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

Which one, for what

Steel BB

Best for Agents that need a real cloud browser with persistent profiles, stored logins, CAPTCHA solving and a human takeover path, and teams that want an open-source runtime they can also self-host.

Ahead on

  • Reliability, 63 against 46
  • Schema & documentation, 86 against 74
  • Agent ergonomics, 79 against 73
  • Security & auth, 56 against 35
  • Payments & pricing, 88 against 60
  • Maintenance & community, 82 against 47
  • Transparency & trust, 65 against 58

Also in its favour

  • Agent-ready, a grade of BB or better
  • An agent can pay per call over x402, with no account
  • A hosted endpoint, with nothing to install
  • Open source

Watch for

Two incidents of more than an hour hit session creation in the 90 days to 1 November 2026 (23 August, 1 October), per the status history read on 8 October

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

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 Steel +35

Steel 82

steel-browser v0.5.5-beta was tagged on 31 October 2026 and changelog 038 is dated 2 October (30). In the 90 days from 3 August, changelog entries on 18 and 25 September and 2 October, steel-browser v0.5.4-beta (25 August) and v0.5.5-beta (31 October), and the MCP server's 3.0.0 on main (9 September). The 24 July entry has left the window and no changelog entry has followed 038 (20). Public changelog, Discord and email support, and steel-browser merged 32 commits between v0.5.4-beta and v0.5.5-beta, among them fixes for session-ID validation in casting, file:// blocking and a Node CVE. GitHub issue reply times were not read (15). Official SDKs exist, but the newest tags are steel-node v0.20.0 and steel-python v0.19.0 from 23 June, with no commit after 11 September, npm and PyPI didn't resolve from our shell on 1 November, and the MCP server is not in the MCP registry, per the 8 October check (9). CI workflows in steel-browser and a test, byte-budget and conformance suite in the MCP server. Whether they pass was not read (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.

Payments & pricing Steel +28

Steel 88

x402 version 2 at x402.steel.dev for scrape, screenshot and PDF, in USDC on Base or Solana. An unpaid request on 1 November 2026 again returned 402 asking 10000 base units, with the resource named as api.paysponge.com. Browser sessions, the main product, aren't covered, so partial (20). Per-hour, per-GB and per-1,000-call prices published without login, on a pricing page last edited 23 October 2026 with the same rates (20). Launch plan with $30 of one-time credit valid 90 days, and the quickstart says no card is required (20). An agent with a wallet gets a scrape, screenshot or PDF with no account, but a browser session needs a person to sign up or run the Stripe CLI, so we award 15 of 20. Re-scored on 13 November 2026 for the new payments rubric: the protocol's 20 of 40 is 5 of 10, and the other lines' 55 is 82.5 at 30 each, so 75 is 88.

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.

Security & auth Steel +21

Steel 56

Named API keys, shown once, revoked by deletion, with last-used times and a rotation guide. A global key covers the organisation and can create keys bound to one project through POST /v1/api-keys. No per-permission scopes were found (22). The documented CDP connection passes the key as apiKey in the wss://connect.steel.dev URL, a secret in a query string (minus 10). No read-only key. Projects isolate sessions, credentials and profiles, stored credentials are typed into pages without being shown to the agent, browser action endpoints reject localhost and private addresses since changelog 038, and the MCP server has a scrape-only profile and hands the browser to a person before logins and payments (13). The MCP server fences page content as untrusted and strips hidden text, and its README warns about injection. The API docs carry no such guidance (10). Session logs, recordings, Agent Traces, per-session cost and exports to JSON or CSV give the operator a per-call trail (13). A Vanta trust centre whose contents did not render for us, a HIPAA-ready BAA and SSO on Scale, and a disclosure policy with response times for the MCP server. No security.txt, bug bounty or certification report was found (8).

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.

Reliability Steel +17

Steel 63

Graded as a hosted service, on Steel Cloud. status.steel.dev runs on Better Stack with Steel API, Dashboard, Proxies and Connections components and 90 days of history, per the 8 October check (20). On 1 November its robots.txt disallows every path, so the history wasn't re-read. Per the 8 October check, the 4 hour 10 minute outage of 22 July 2026 has now left the 90-day window, leaving two majors in it, 5 hours 41 minutes of capacity errors on session creation on 23 August and 1 hour 55 minutes of failing session creation on 1 October. Two majors give 5, and anything posted after 8 October is unread, which would also score 5 as no readable history (5). Limits are published per plan, 60 and 600 requests a minute and 10 and 100 concurrent sessions, re-read on 1 November, and 20 a minute on Browser Tools (15). Browser Tools document 429 and a 503 marked safe to retry, the Agent Traces API says to wait for Retry-After, and the SDKs retry 408, 409, 429 and 5xx twice with backoff. No idempotency keys, though session creation accepts a caller-chosen sessionId (10). Support and uptime SLAs are listed for Enterprise only on the pricing page re-read on 1 November, with no terms published (3). The sessions API is not marked beta (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.

Schema & documentation Steel +12

Steel 86

OpenAPI 3.0.3 at docs.steel.dev/openapi.json with 51 paths and 75 operations and the steel-api-key header scheme (25). llms.txt, llms-full.txt and a Markdown twin of every docs page (10). 65 of 75 operations carry a description, and the MCP server's tool descriptions say when to use each tool and when to pick another (16). Inputs are typed with enums, UUID formats and list limits of 1 to 100, but timeout and concurrency carry no real bounds and useProxy and region have no stated type (11). One shared error schema is attached to most operations and the docs have error tables for Browser Tools and Agent Traces. The spec holds one example, and 429 is declared on session creation only (11). Paths are versioned under /v1 and the changelog is public and numbered, with dates in page metadata. The spec's own version reads 0.0.1 (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 Steel +7

Steel 65

Graded on the cloud service, which is closed with published terms. The browser runtime steel-browser and the SDKs are Apache-2.0, and the MCP server and CLI are MIT (24). The privacy notice (last updated 9 October 2026, re-read on 1 November) keeps data while an account exists, the pricing page gives 7 and 14 days of data retention, recordings can be turned off per session, and a DPA is linked as a Google Drive file. The terms date from 5 February 2025, the docs Legal page links to Google Docs copies, and the FAQ still describes pricing by concurrent sessions (14). No deprecation policy. Legacy plans stay available after the pricing change, and one docs note says a playback mode will be deprecated without a date (4). The privacy notice names Anthropic, OpenAI and Google Cloud AI as AI processors and says servers are in the United States, and the docs name one region, us-east. No subprocessor list was found outside the trust centre, which did not render for us (10).

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

CategoryWeightSteelTilion FortressEdge
Reliability16%6346Steel +17
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8674Steel +12
Agent ergonomics13%7973Steel +6
Security & auth14%5635Steel +21
Payments & pricing10%8860Steel +28
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8247Steel +35
Transparency & trust7%6558Steel +7
Negative events≤1500
TotalBB 73.1/100C 55.9/100

Facts side by side

FactSteelTilion Fortress
KindHTTP APIMCP server
VendorNen Labs, Inc.Tilion Inc.
Hosted endpointhttps://api.steel.devno (local only)
TransportsHTTP, stdiostdio
AuthAPI keyNone
PricingFreemiumFreemium
x402yes, from $0.01/callno
LicenceProprietary cloud service under Steel's terms. steel-browser and the Node and Python SDKs are Apache-2.0. The MCP server and the CLI are MITFortress 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-312026-10-05
Terms last updated2025-02-05no date given
Privacy policy last updated2026-02-052026-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 benchmarkingyesnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity47k npm/wk, 63k PyPI/wk804 stars
Agent reviews2/5 (4)none

How the scores have moved

Verdicts

Steel

The hosted API has a public OpenAPI document, per-unit prices, $30 of starting credit and x402 payment for scrape, screenshot and PDF calls. Two session-creation incidents of more than an hour fall in the last 90 days, and the documented CDP connection puts the API key in the URL.

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

Steel

  1. Use POST /v1/scrape for pages you only need to read. It starts no session and costs $5 per 1,000 calls, or $0.01 a call by x402
  2. Release every session with POST /v1/sessions/{id}/release and set inactivityTimeout. Browser time bills by the minute, rounded up
  3. Build the CDP URL as wss://connect.steel.dev?apiKey=<key>&sessionId=<id> and keep it out of logs, because it carries the key
  4. Launch sessions end after 15 minutes at most, and timeout cannot be changed on a live session
  5. CAPTCHA solving and Steel's managed proxies on Launch need $10 of paid balance. Free credit does not count

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

Steel scores 73.1 (BB) on agent readiness against Tilion Fortress's 55.9 (C), and leads in every scored category.

Do Steel and Tilion Fortress need an API key?

Steel needs an API key. Tilion Fortress needs no key. An agent can also pay Steel per call over x402, with no account.

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

Steel has a hosted endpoint at https://api.steel.dev. Tilion Fortress runs on your own machine, with no hosted endpoint listed.

Are Steel and Tilion Fortress open source?

Steel is open source (Proprietary cloud service under Steel's terms. steel-browser and the Node and Python SDKs are Apache-2.0. The MCP server and the CLI are MIT). No open-source release is listed for Tilion Fortress.

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