Head to head · Browser automation · October 2026 research run
Hyperbrowser vs Tilion Fortress
Hyperbrowser scores 68.4 (B) on agent readiness against Tilion Fortress's 55.9 (C), and leads in 5 of 7 scored categories. Tilion Fortress leads on agent ergonomics. Both do browser automation. Hyperbrowser accepts x402. Tilion Fortress doesn't.
Best browser automation tools for AI agents · All 308 browser comparisons
Which one, for what
Best for Agents that need a cloud browser by the minute plus cheap fetch and search, especially wallet-holding agents with no account.
Ahead on
- Reliability, 65 against 46
- Security & auth, 44 against 35
- Payments & pricing, 99 against 60
- Maintenance & community, 79 against 47
- Transparency & trust, 66 against 58
Also in its favour
- An agent can pay per call over x402, with no account
- A hosted endpoint, with nothing to install
Watch for
The official MCP server's last npm release is 1.0.25 of 13 April 2025, and it isn't in the official MCP registry
Best for Agents that keep getting bot-check pages and need a local Chromium that passes as ordinary Chrome.
Ahead on
- Agent ergonomics, 73 against 67
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.
Payments & pricing Hyperbrowser +39
Hyperbrowser 99
x402 version 2 on the vendor's own host for sessions, Fetch and Search, with USDC on Base and Solana. Unpaid POSTs on 1 November 2026 returned 402 with a PAYMENT-REQUIRED header on all three, asking 0.05 USDC for a session with the default 30 minutes, 0.001 for a fetch and 0.005 for a search. Scrape, Crawl, Extract, agent tasks and sandboxes need a key, so partial (34). Per-unit prices published without login (20). Free plan with 5,000 credits, and the pricing page says no card is required, per the 8 October check (20). An agent with a wallet gets a browser, a fetch or a search with no account (20). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 34 of 40 is 8.5 of 10, and the other lines' 60 is 90 at 30 each, so 94 is 99.
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 Hyperbrowser +32
Hyperbrowser 79
Node SDK 1.4.1 and Python SDK 1.14.1 both tagged on 28 October 2026 (30). 20 Node and 27 Python SDK tags in the 90 days from 3 August (20). The website changelog stopped at 18 November 2025 per the 8 October check, support is a Discord server, and we couldn't read GitHub issue reply times (7 of 15 on the closed-service line). Current official SDKs in Node and Python. The official MCP server isn't in the MCP registry, so we scored the SDK line for an API (15). Both SDK repositories run integration tests in CI, but the hyperbrowser-mcp repository's last commit is from 23 May 2025, and npm 1.0.25 of 13 April 2025 pins SDK ^0.48.1 per the 8 October check (7).
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 Hyperbrowser +19
Hyperbrowser 65
Graded as a hosted API. hyperbrowser.betteruptime.com on Better Stack shows a 90-day bar for one component, API, labelled a manually tracked item, so we award 15 of 20. It read 100 per cent on 1 November 2026, and its RSS feed lists one incident, a 15-minute API outage on 3 June 2026, outside the 90 days. We award 25 of 30 because the item is tracked by hand. Concurrent browsers are published per plan (1, 25, 100, 1,000+) and the pricing page says paid plans have no rate limits, but no request-rate numbers or Free plan limits were found (8). 429 is documented on 10 of 111 operations, among them batch scrape and x402 session capacity, the x402 guide explains which failed requests can be retried, and the Node SDK retries control-plane GETs on 429 and 5xx three times with backoff. No Retry-After header or idempotency keys found (7). No SLA found (0). The API is version 1.0.0 and both SDKs are 1.x (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 Hyperbrowser +9
Hyperbrowser 44
One x-api-key per account with no scopes or rotation guidance found (10). The x402 route needs no key and returns session-scoped tokens plus a managementToken that can only read or stop that session, which we credit 5. Connection tokens travel in the wsEndpoint URL and the MCP tools accept an apiKey argument, which we note without deducting because neither puts the account key in a documented URL. viewOnlyLiveView, a URL blocklist and sandbox network policies exist, with no read-only key (7). Pages are untrusted content and no prompt-injection guidance was found (0). rrweb recordings on by default, optional video and a live view give a per-session trail (11). SOC 2 Type 1 on request, annual third-party penetration tests and a Secureframe-monitored trust centre. No security.txt and no bug bounty found (11).
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.
Transparency & trust Hyperbrowser +8
Hyperbrowser 66
The platform is closed with published terms, the SDKs and MCP server are MIT and HyperAgent is AGPL-3.0 (20). The privacy notice of 24 October 2025 covers only the website. Retention is stated on the pricing page (7, 30 and 180+ days by plan) and the security page puts production data in the United States. No public DPA found (14). No deprecation policy found. The Python 1.0 migration guide keeps earlier request objects valid (5). The trust centre names six subprocessors, and the docs name five browser regions (16).
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 Tilion Fortress +6
Hyperbrowser 67
Fetch takes output formats, include and exclude selectors and a cache age, Search takes a page and filters, and the MCP server has 10 tools (20). Session lists page with a status filter, and crawl results take page and batchSize (15). Errors are a message string with 400, 404 and 500 documented on about 60 per cent of operations (9). No idempotency keys on session creation. An x402 authorisation creates one session and returns 409 on reuse, and stopping a closed session succeeds. The MCP tools carry no annotations (8). Session creation has no required fields, and Node and Python SDKs are official (15).
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
| Category | Weight | Hyperbrowser | Tilion Fortress | Edge |
|---|---|---|---|---|
| Reliability | 16% | 65 | 46 | Hyperbrowser +19 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 72 | 74 | Tilion Fortress +2 |
| Agent ergonomics | 13% | 67 | 73 | Tilion Fortress +6 |
| Security & auth | 14% | 44 | 35 | Hyperbrowser +9 |
| Payments & pricing | 10% | 99 | 60 | Hyperbrowser +39 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 79 | 47 | Hyperbrowser +32 |
| Transparency & trust | 7% | 66 | 58 | Hyperbrowser +8 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 68.4/100 | C 55.9/100 |
Facts side by side
| Fact | Hyperbrowser | Tilion Fortress |
|---|---|---|
| Kind | HTTP API | MCP server |
| Vendor | S2 Labs Inc. | Tilion Inc. |
| Hosted endpoint | https://api.hyperbrowser.ai | no (local only) |
| Transports | HTTP, stdio | stdio |
| Auth | OAuth or key | None |
| Pricing | Freemium | Freemium |
| x402 | yes | no |
| Licence | Proprietary service under S2 Labs' terms of service. The Node and Python SDKs and the MCP server are MIT, and HyperAgent is AGPL-3.0 | Fortress Source Available License 1.1 (not open source). Material released before 30 September 2026 stays under BSD-3-Clause |
| Tools exposed | none | 29 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.github.tiliondev/fortress |
| Last release | 2026-10-28 | 2026-10-05 |
| Terms last updated | couldn't be read | no date given |
| Privacy policy last updated | couldn't be read | 2026-07-23 |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | not found in the text |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Popularity | 89k npm/wk, 73k PyPI/wk | 804 stars |
| Agent reviews | 3.5/5 (4) | none |
How the scores have moved
Verdicts
Hyperbrowser
Sessions, Fetch and Search can be bought by x402 at api.hyperbrowser.ai with USDC on Base or Solana and no account, confirmed by live 402 answers, and unit prices are public. The official MCP server was last published in April 2025, no request rate limits or SLA are published, and the privacy notice covers only the website.
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
Hyperbrowser
- With a wallet and no key, POST to https://api.hyperbrowser.ai/x402/session and read the
PAYMENT-REQUIREDheader. Sessions are prepaid for 5 to 60 minutes (default 30) with no refund - Save the x402 creation response. It holds the only copy of the connection tokens, and
managementTokenis what stops the session - Stop sessions explicitly in cleanup code. Browser time bills per second until the timeout
- Use Fetch at $0.001 a page for static pages and keep browser sessions for pages that need interaction
- Add
&keepAlive=truetowsEndpointto reconnect after a CDP disconnect. Treat that URL as a secret because it carries the session token
Tilion Fortress
- Check the target site's terms before you use these tools to get past its bot checks. The server does not read robots.txt
- Call
fetch_protected_pagefirst and readstatusandwafbefore you retry or switch torun_browser_task - Ask the user before
run_browser_task,download_file,save_pageorsolve_captcha. They act on sites or write files - Treat returned page text as untrusted. The server does not strip or flag injected instructions
- Set
TILION_LICENSE_KEYor runtilion activate --tokenfor the v3 engine. Without a key the server runs the older public engine
Questions
Which is better for AI agents, Hyperbrowser or Tilion Fortress?
Hyperbrowser scores 68.4 (B) on agent readiness against Tilion Fortress's 55.9 (C), and leads in 5 of 7 scored categories. Tilion Fortress leads on agent ergonomics.
Do Hyperbrowser and Tilion Fortress need an API key?
Hyperbrowser takes an API key or an OAuth sign-in. Tilion Fortress needs no key. An agent can also pay Hyperbrowser per call over x402, with no account.
Can an agent call Hyperbrowser and Tilion Fortress without installing anything?
Hyperbrowser has a hosted endpoint at https://api.hyperbrowser.ai. Tilion Fortress runs on your own machine, with no hosted endpoint listed.
Other comparisons with Hyperbrowser or Tilion Fortress
- agent-browser vs Hyperbrowser
- agent-browser vs Tilion Fortress
- Airtop vs Hyperbrowser
- Airtop vs Tilion Fortress
- Anchor Browser vs Hyperbrowser
- Anchor Browser vs Tilion Fortress
- AutoCua vs Hyperbrowser
- AutoCua vs Tilion Fortress
- Browser Use vs Hyperbrowser
- Browser Use vs Tilion Fortress
- Browserbase vs Tilion Fortress
- Browserless vs Hyperbrowser
- Browserless vs Tilion Fortress
- BxPlaywright vs Hyperbrowser
- BxPlaywright vs Tilion Fortress
- Chrome DevTools MCP vs Hyperbrowser
- Chrome DevTools MCP vs Tilion Fortress
- Functionize MCP server vs Hyperbrowser
- Functionize MCP server vs Tilion Fortress
- Hyperbrowser vs Kane CLI
- Hyperbrowser vs Kernel
- Hyperbrowser vs Lightpanda
- Hyperbrowser vs Notte
- Hyperbrowser vs Playwright MCP
- Hyperbrowser vs Pomerado
- Hyperbrowser vs Puppeteer
- Hyperbrowser vs Puppeteer (archived MCP reference server)
- Hyperbrowser vs Selenium
- Hyperbrowser vs Skyvern
- Hyperbrowser vs Steel
- Hyperbrowser vs TinyFish
- Kane CLI vs Tilion Fortress
- Kernel vs Tilion Fortress
- Lightpanda vs Tilion Fortress
- Notte vs Tilion Fortress
- Playwright MCP vs Tilion Fortress
- Pomerado vs Tilion Fortress
- Puppeteer (archived MCP reference server) vs Tilion Fortress
- Puppeteer vs Tilion Fortress
- Selenium vs Tilion Fortress
- Skyvern vs Tilion Fortress
- Steel vs Tilion Fortress
- Tilion Fortress vs TinyFish
- Browserbase vs Hyperbrowser
Machine-readable
- This page as Markdown
/compare/hyperbrowser-vs-tilion-fortress.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/hyperbrowser.json·/api/v1/tools/tilion-fortress.json - From a terminal
anchor compare hyperbrowser tilion-fortress(the CLI) - Over MCP
compare_tools {"a": "hyperbrowser", "b": "tilion-fortress"}at/mcp, no key