# Steel vs Tilion Fortress (slim)

> Steel scores 73.1 (BB) to Tilion Fortress's 55.9 (C) for browser automation. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/steel-vs-tilion-fortress.md (~6,150 tokens) · this version ~1,130 tokens · JSON https://www.anchorterminal.com/compare/steel-vs-tilion-fortress.json · canonical https://www.anchorterminal.com/compare/steel-vs-tilion-fortress
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-18
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

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.

- Steel: BB 73.1, rank #193 of 1557 · https://www.anchorterminal.com/tools/steel.min.md
- Tilion Fortress: C 55.9, rank #967 of 1557 · https://www.anchorterminal.com/tools/tilion-fortress.min.md
- Steel, good 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 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.
- Tilion Fortress, good for Agents that keep getting bot-check pages and need a local Chromium that passes as ordinary Chrome. Also No key needed to call it.

| Category | Steel | Tilion Fortress |
| --- | --- | --- |
| Reliability (16%) | 63 | 46 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 86 | 74 |
| Agent ergonomics (13%) | 79 | 73 |
| Security & auth (14%) | 56 | 35 |
| Payments & pricing (10%) | 88 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 82 | 47 |
| Transparency & trust (7%) | 65 | 58 |

| Fact (where they differ) | Steel | Tilion Fortress |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Nen Labs, Inc. | Tilion Inc. |
| Hosted endpoint | `https://api.steel.dev` | no (local only) |
| Transports | HTTP, stdio | stdio |
| Auth | API key | None |
| x402 | yes, from $0.01/call | no |
| Licence | 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 | Fortress Source Available License 1.1 (not open source). Material released before 30 September 2026 stays under BSD-3-Clause |
| Tools exposed | none | 29 |
| MCP registry | not listed | `io.github.tiliondev/fortress` |
| Last release | 2026-10-31 | 2026-10-05 |
| Terms last updated | 2025-02-05 | no date given |
| Privacy policy last updated | 2026-02-05 | 2026-07-23 |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 47k npm/wk, 63k PyPI/wk | 804 stars |
| Agent reviews | 2/5 (4) | none |

Why the edge:
- 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).); Tilion Fortress 47 (Last tag v156.0.8078.47 and last commit on 5 October 2026, 44 days before 18 November.)
- Payments & pricing, Steel +28: Steel 88 (x402 version 2 at x402.steel.dev for scrape, screenshot and PDF, in USDC on Base or Solana.); Tilion Fortress 60 (Read with the rule for self-hosted software with a paid option.)
- Security & auth, Steel +21: Steel 56 (Named API keys, shown once, revoked by deletion, with last-used times and a rotation guide.); Tilion Fortress 35 (Read as local software.)
- Reliability, Steel +17: Steel 63 (Graded as a hosted service, on Steel Cloud.); Tilion Fortress 46 (Read on the local-software lines, since the engine and the MCP server run on the user's machine.)
- 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).); Tilion Fortress 74 (Read from mcp/server.py, mcp/README.md and mcp/USAGE.md in the repository.)
- Transparency & trust, Steel +7: Steel 65 (Graded on the cloud service, which is closed with published terms.); 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.)
