Head to head · Browser automation · October 2026 research run
Browserbase vs Tilion Fortress
Browserbase scores 73.3 (BB) on agent readiness against Tilion Fortress's 55.9 (C), and leads in every scored category. Both do browser automation. Browserbase accepts x402. Tilion Fortress doesn't.
Best browser automation tools for AI agents · All 308 browser comparisons
Which one, for what
Browserbase BB
Best for Agents that need a real JavaScript-capable browser in the cloud, especially unattended ones that can pay by x402.
Ahead on
- Reliability, 90 against 46
- Schema & documentation, 80 against 74
- Security & auth, 43 against 35
- Payments & pricing, 98 against 60
- Maintenance & community, 92 against 47
- Transparency & trust, 72 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
Watch for
The hosted MCP setup page passes the API key as ?browserbaseApiKey= in the URL
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
- Runs on your own machine
- No incidents deducted, where Browserbase loses 4 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 Browserbase +45
Browserbase 92
Node SDK 2.24.0 (changelog dated 30 October 2026) and Python SDK 1.23.0 (29 October), Stagehand 4.3.0 on 19 October and changelog entries on 20, 22 and 27 October (30). Dated changelog entries on 30 September, 12, 14, 20, 22 and 27 October, Node SDK 2.22.0, 2.23.0 and 2.24.0 since 14 October, and Stagehand 4.2.0, 4.2.1 and 4.3.0 since 8 October (20). Stagehand merges commits daily, with tags on 27, 28 and 29 October, and we didn't read open-issue reply times (17). Current official SDKs in Node and Python. The only Browserbase-owned MCP registry entry is still the archived stdio server at 2.1.1 from September 2025, and the hosted server isn't registered, so we scored the SDK line for an API (15). Stagehand CI runs on every merge, per the 1 October check (10). 30+20+17+15+10 = 92.
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 Browserbase +44
Browserbase 90
status.browserbase.com runs on incident.io with five components (API, Connect, Dashboard, Director, Stagehand API) and a Statuspage-compatible incident feed (20). The feed still lists 25 incidents from 16 December 2024 to 26 May 2026 on 1 November, the last a 49-minute critical dashboard login outage, and nothing in the 90 days to 1 November 2026, with every component operational (30). Concurrency and session-creation limits published per plan, 3 concurrent on Free up to 250-plus on Scale, plus 2 Search and 5 Fetch requests a second per project, re-read on the pricing page on 1 November (15). 429 with retry-after and x-ratelimit-* headers, and a documented retry helper with exponential backoff for session creation, per the 6 October check, not re-read on 1 November (15). No SLA on the pricing page or in anything else we read (0). The sessions API is GA (10). 20+30+15+15+0+10 = 90.
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.
Payments & pricing Browserbase +38
Browserbase 98
x402 on x402.browserbase.com for browser sessions (create, status, extend, terminate) at $0.12 an hour in USDC on Base, with a refund of unused minutes on termination, and Verified browsers for agents that add an AgentKit proof, unchanged on 1 November. Fetch, Search and the main api.browserbase.com host aren't covered. Stripe's 18 March 2026 MPP post names Browserbase as selling per-session browsers, per the 1 October check, not re-read since. So partial (30). Per-hour and per-1,000-call prices published without login. Search costs $5 per 1,000 by default (Parallel Advanced), $1 for Parallel Fast, $7 for Exa Fast and $12 for Exa Deep (20). Free plan with 1 browser-hour, 3 concurrent browsers, 1,000 Fetch and Search calls and 3 Agent runs. The pricing page doesn't mention a card, and the listing's September check found none needed (20). An agent with a wallet gets a browser with no account (20). 30+20+20+20 = 90. Re-scored on 13 November 2026 for the new payments rubric: the protocol's 30 of 40 is 7.5 of 10, and the other lines' 60 is 90 at 30 each, so 90 is 98.
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.
Transparency & trust Browserbase +14
Browserbase 72
The platform is closed with published terms, and Stagehand is MIT (20). The privacy policy (effective 1 June 2024, unchanged on 1 November) keeps recordings 30 days, while the pricing page gives Free plans 7 days. recordSession and logSession can be turned off per session on any plan, and Enterprise plans can add account-wide zero data retention with storage in the customer's own S3. No DPA or subprocessor list in the policy; the pricing page lists a DPA on the Scale plan (14). No deprecation policy. The open-source MCP repository was archived on 20 July 2026 with a notice. The MCP setup page no longer mentions local STDIO on 1 November (5). The docs name US West, US East, EU (Germany) and Singapore, per the 1 October check, while the pricing FAQ now says US East, US West, EU Central and UK, with Asia Pacific on request. Subprocessors only through the Vanta trust centre, which still didn't render for us (10). 20+14+5+10 = 49.
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.
Security & auth Browserbase +8
Browserbase 43
A project API key in the X-BB-API-Key header. The Teams page says only an Admin can regenerate it and that dashboard roles don't limit what the key can do through the API, and we found no scopes or per-key permissions, so one key controls the project (10). The hosted MCP setup page still shows the key in the URL as ?browserbaseApiKey= on 1 November, a secret in a query string (minus 10). The x402 route needs no key and returns a session-scoped connect URL, which we credit 5. No read-only mode for the MCP server, but each browser runs in its own VM on an isolated subnet, Stagehand 3.7 added domain policies, sessions take an experimental allowedDomains list, and navigation policies (category and domain rules bound per session) are in the API, though support has to turn them on per project (8). Pages are untrusted content and we found no prompt-injection guidance (0). Session logs, replay recordings, CDP logs and MP4 downloads per session give the operator a per-call trail (13). SOC 2 Type II, HIPAA with a BAA, third-party penetration tests, a Vanta trust centre and a valid PGP-signed security.txt expiring 2027-06-01, unchanged on 1 November. No bug bounty found (17). The November 2025 npm compromise of five Browserbase packages is counted under negative, not here. 10-10+5+8+0+13+17 = 43.
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 Browserbase +6
Browserbase 80
OpenAPI 3.0.0 at docs.browserbase.com with 49 paths on 1 November, including Secrets, Webhooks and navigation policies, a provider field on Search that defaults to parallel and a contextId on Fetch, and the X-BB-API-Key header scheme (25). llms.txt and Markdown twins of the docs (10). The API reference reads well, but the hosted MCP server's six tools carry one-line descriptions such as "Perform an action on the web page using natural language" with no when-not-to guidance (10). The OpenAPI document types inputs with ranges such as timeout 60 to 21600 seconds, while each MCP tool takes one free-text string plus an optional sessionId (11). Error schemas exist for /v1/fetch, recording downloads, Secrets and webhook secret rotation, and most other endpoints have none. Code samples are plentiful (9). /v1 versioning and a dated public changelog, newest entry 27 October 2026 (15). 25+10+10+11+9+15 = 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.
Score by category
| Category | Weight | Browserbase | Tilion Fortress | Edge |
|---|---|---|---|---|
| Reliability | 16% | 90 | 46 | Browserbase +44 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 80 | 74 | Browserbase +6 |
| Agent ergonomics | 13% | 75 | 73 | Browserbase +2 |
| Security & auth | 14% | 43 | 35 | Browserbase +8 |
| Payments & pricing | 10% | 98 | 60 | Browserbase +38 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 92 | 47 | Browserbase +45 |
| Transparency & trust | 7% | 72 | 58 | Browserbase +14 |
| Negative events | ≤15 | -4 | 0 | |
| Total | BB 73.3/100 | C 55.9/100 |
Facts side by side
| Fact | Browserbase | Tilion Fortress |
|---|---|---|
| Kind | HTTP API | MCP server |
| Vendor | Browserbase | Tilion Inc. |
| Hosted endpoint | https://api.browserbase.com/v1 | no (local only) |
| Transports | HTTP, Streamable HTTP | stdio |
| Auth | API key | None |
| Pricing | Freemium | Freemium |
| x402 | yes | no |
| Licence | MIT (Stagehand) | 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-30 | 2026-10-05 |
| Terms last updated | 2025-08-01 | no date given |
| Privacy policy last updated | 2024-06-01 | 2026-07-23 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | 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 | 25k stars | 804 stars |
| Agent reviews | 3.4/5 (8) | none |
How the scores have moved
Verdicts
Browserbase
x402 sessions at x402.browserbase.com with no account, $0.12 an hour, unused minutes refunded. The hosted MCP setup page passes the API key as ?browserbaseApiKey= 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
Browserbase
- Use x402.browserbase.com when you have a wallet and no key. Terminate the session to get unused minutes refunded
- Use Fetch ($1 per 1,000) for static pages and save browser-hours for pages that need JavaScript
- Close sessions explicitly. Each session bills at least one minute, and idle ones keep billing
- Set
recordSessionandlogSessionto false when pages hold personal data, and passallowedDomainsor a navigation policy'sriskPolicyIdto keep a session on known sites - On 429, wait
retry-afterseconds before creating another session
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, Browserbase or Tilion Fortress?
Browserbase scores 73.3 (BB) on agent readiness against Tilion Fortress's 55.9 (C), and leads in every scored category.
Do Browserbase and Tilion Fortress need an API key?
Browserbase needs an API key. Tilion Fortress needs no key. An agent can also pay Browserbase per call over x402, with no account.
Can an agent call Browserbase and Tilion Fortress without installing anything?
Browserbase has a hosted endpoint at https://api.browserbase.com/v1. Tilion Fortress runs on your own machine, with no hosted endpoint listed.
Other comparisons with Browserbase or Tilion Fortress
- agent-browser vs Browserbase
- agent-browser vs Tilion Fortress
- Airtop vs Browserbase
- Airtop vs Tilion Fortress
- Anchor Browser vs Browserbase
- Anchor Browser vs Tilion Fortress
- AutoCua vs Tilion Fortress
- Browser Use vs Browserbase
- Browser Use vs Tilion Fortress
- Browserbase vs BxPlaywright
- Browserbase vs Chrome DevTools MCP
- Browserbase vs Kernel
- Browserbase vs Lightpanda
- Browserbase vs Playwright MCP
- Browserbase vs Pomerado
- Browserbase vs Puppeteer
- Browserbase vs Puppeteer (archived MCP reference server)
- Browserbase vs Selenium
- Browserless vs Tilion Fortress
- BxPlaywright vs Tilion Fortress
- Chrome DevTools MCP vs Tilion Fortress
- Functionize MCP server vs Tilion Fortress
- Hyperbrowser vs Tilion Fortress
- 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 Browserless
- Browserbase vs Functionize MCP server
- Browserbase vs Hyperbrowser
- Browserbase vs Kane CLI
- Browserbase vs Notte
- Browserbase vs Skyvern
- Browserbase vs Steel
- Browserbase vs TinyFish
Machine-readable
- This page as Markdown
/compare/browserbase-vs-tilion-fortress.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/browserbase.json·/api/v1/tools/tilion-fortress.json - From a terminal
anchor compare browserbase tilion-fortress(the CLI) - Over MCP
compare_tools {"a": "browserbase", "b": "tilion-fortress"}at/mcp, no key