# AutoCua vs Tilion Fortress

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

- Canonical: https://www.anchorterminal.com/compare/autocua-vs-tilion-fortress
- Markdown: https://www.anchorterminal.com/compare/autocua-vs-tilion-fortress.md (~4,900 tokens)
- Slim: https://www.anchorterminal.com/compare/autocua-vs-tilion-fortress.min.md (~1,080 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/autocua-vs-tilion-fortress.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-18

Tilion Fortress scores 55.9 (C) on agent readiness against AutoCua's 48 (D), and leads in 4 of 7 scored categories. AutoCua leads on payments & pricing and maintenance & community. Both do browser automation.

- AutoCua: grade D, 48/100, rank #1216 of 1557. Markdown https://www.anchorterminal.com/tools/autocua.md · JSON https://www.anchorterminal.com/api/v1/tools/autocua.json
- Tilion Fortress: grade C, 55.9/100, rank #967 of 1557. Markdown https://www.anchorterminal.com/tools/tilion-fortress.md · JSON https://www.anchorterminal.com/api/v1/tools/tilion-fortress.json
- Best desktop and mobile app automation for AI agents: https://www.anchorterminal.com/best/desktop-automation/index.md
- All 64 desktop comparisons: https://www.anchorterminal.com/compare/desktop-automation/index.md
- Best browser automation tools for AI agents: https://www.anchorterminal.com/best/browser/index.md
- All 308 browser comparisons: https://www.anchorterminal.com/compare/browser/index.md

## Which one, for what

### AutoCua (D)

Good for: Developers who want a local agent to operate desktop apps, their own browser or phones across platforms, on a machine they control.

Ahead on:
- Payments & pricing, 90 against 60
- Maintenance & community, 65 against 47

Also in its favour:
- Open source

Watch for: Two weeks old at version 0.1.9, with no changelog file

### Tilion Fortress (C)

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

Ahead on:
- Reliability, 46 against 25
- Schema & documentation, 74 against 42
- Agent ergonomics, 73 against 55
- Transparency & trust, 58 against 42

Also in its favour:
- Runs on your own machine
- Free to start without a card

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

### Schema & documentation: Tilion Fortress +32

- AutoCua (42): Framework reading. No API reference or typed interface beyond run_agent's documented arguments (5 of 25). No llms.txt (0). The README says what each mode drives and where it runs, and agent_capabilities.md lists what it can do (16 of 20). Modes and device are documented strings (6 of 15). Many examples, no documented errors (10 of 15). Tags without a changelog (5 of 15). 5 + 0 + 16 + 6 + 10 + 5 = 42.
- 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.

### Payments & pricing: AutoCua +30

- AutoCua (90): Free self-hosted package with nothing to buy: 0 + 20 + 20 + 20 = 60. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.
- 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.

### Reliability: Tilion Fortress +21

- AutoCua (25): Local package. Installs from PyPI as AutoCua with Python 3.10 or later and the supported platforms stated (20). No CI runs the tests; the only workflow, use_case_label.yml, labels issues (0). GitHub issues weren't read, so the open-issue line is scored absent (0). Four tags in a week with no changelog file (5). Version 0.1.9 (0). 20 + 0 + 0 + 5 + 0 = 25.
- 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.

### Agent ergonomics: Tilion Fortress +18

- AutoCua (55): Framework reading. One call with a mode, provider, model and task runs a whole agent (20 of 25). A separate compression agent splices handoff summaries in, and runs are capped and stoppable (15 of 20). Permission and blocked-input errors are reported specifically, with no error reference (8 of 20). No resume or retry semantics described (2 of 20). Sensible defaults (simulators unless device is set), Python only (10 of 15). 20 + 15 + 8 + 2 + 10 = 55.
- 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.

### Maintenance & community: AutoCua +18

- AutoCua (65): v0.1.9 tagged on 4 November 2026 (30). Four tags in 90 days (20). Issues and pull requests weren't read (0 of 25). The PyPI wheel is current (15). No CI; dependencies pinned per OS in requirements files (0 of 10). 30 + 20 + 0 + 15 + 0 = 65.
- 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.

### Transparency & trust: Tilion Fortress +16

- AutoCua (42): MIT (30). Says it sends data only to the chosen model provider and keeps everything else locally, and the source agrees (20 of 30). No deprecation policy (0). States no telemetry, and none was found (20). 30 + 20 + 0 + 20 = 70.
- 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

| Category | Weight | AutoCua | Tilion Fortress | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 25 | 46 | Tilion Fortress +21 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 42 | 74 | Tilion Fortress +32 |
| Agent ergonomics | 13% | 55 | 73 | Tilion Fortress +18 |
| Security & auth | 14% | 38 | 35 | AutoCua +3 |
| Payments & pricing | 10% | 90 | 60 | AutoCua +30 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 65 | 47 | AutoCua +18 |
| Transparency & trust | 7% | 42 | 58 | Tilion Fortress +16 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **48 · D** | **55.9 · C** | |

## Facts side by side

| Fact | AutoCua | Tilion Fortress |
| --- | --- | --- |
| Kind | Agent framework | MCP server |
| Vendor | Ashish Yadav and contributors (ComputerUseAgent on GitHub) | Tilion Inc. |
| Hosted endpoint | no (local only) | no (local only) |
| Transports |  | stdio |
| Auth | None | None |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | 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 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | not listed | `io.github.tiliondev/fortress` |
| Last release | 2026-11-04 | 2026-10-05 |
| Terms last updated | no document linked | no date given |
| Privacy policy last updated | no document linked | 2026-07-23 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | none | 804 stars |

## How the scores have moved

### AutoCua

- +3.7 on 13 November 2026 (E to D): checklist

### Tilion Fortress

- +1.9 on 18 November 2026: terms, security, new evidence

## Verdicts

**AutoCua.** A capable, fast-moving open-source agent for driving desktops, browsers and phones through real input and accessibility trees, with a careful safety section. It's two weeks old, with no test CI or changelog, and on Windows the model itself decides whether to accept an admin elevation prompt.

**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

### AutoCua

1. pip install AutoCua, then call run_agent with a mode such as "web use" or "computer use", a provider, a model and a task
2. Run it on a machine or account you can afford to lose; it drives real input and keeps logged-in browser profiles
3. On Windows, don't install the Interception driver unless you accept the model deciding UAC prompts
4. Set AutoCua_DATA_DIR to keep keys and profiles somewhere private
5. Phones go over USB from a script; Wi-Fi only through the desktop app

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

Tilion Fortress scores 55.9 (C) on agent readiness against AutoCua's 48 (D), and leads in 4 of 7 scored categories. AutoCua leads on payments & pricing and maintenance & community.

### Can an agent call AutoCua and Tilion Fortress without installing anything?

No hosted endpoint is listed for AutoCua. Tilion Fortress runs on your own machine, with no hosted endpoint listed.

### Are AutoCua and Tilion Fortress open source?

AutoCua is open source (MIT). No open-source release is listed for Tilion Fortress.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/autocua-vs-tilion-fortress.json, and with the fewest tokens: https://www.anchorterminal.com/compare/autocua-vs-tilion-fortress.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "autocua", "b": "tilion-fortress"}`. From a terminal: `anchor compare autocua tilion-fortress`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/autocua.json and https://www.anchorterminal.com/api/v1/tools/tilion-fortress.json

## Other comparisons with AutoCua or Tilion Fortress

- [agent-browser vs AutoCua](https://www.anchorterminal.com/compare/agent-browser-vs-autocua.md)
- [agent-browser vs Tilion Fortress](https://www.anchorterminal.com/compare/agent-browser-vs-tilion-fortress.md)
- [Airtop vs AutoCua](https://www.anchorterminal.com/compare/airtop-vs-autocua.md)
- [Airtop vs Tilion Fortress](https://www.anchorterminal.com/compare/airtop-vs-tilion-fortress.md)
- [Anchor Browser vs AutoCua](https://www.anchorterminal.com/compare/anchor-browser-vs-autocua.md)
- [Anchor Browser vs Tilion Fortress](https://www.anchorterminal.com/compare/anchor-browser-vs-tilion-fortress.md)
- [AutoCua vs Browser Use](https://www.anchorterminal.com/compare/autocua-vs-browser-use.md)
- [AutoCua vs Browserless](https://www.anchorterminal.com/compare/autocua-vs-browserless.md)
- [AutoCua vs BxPlaywright](https://www.anchorterminal.com/compare/autocua-vs-bx-playwright.md)
- [AutoCua vs Chrome DevTools MCP](https://www.anchorterminal.com/compare/autocua-vs-chrome-devtools-mcp.md)
- [AutoCua vs Functionize MCP server](https://www.anchorterminal.com/compare/autocua-vs-functionize-mcp.md)
- [AutoCua vs Hyperbrowser](https://www.anchorterminal.com/compare/autocua-vs-hyperbrowser.md)
- [AutoCua vs Kane CLI](https://www.anchorterminal.com/compare/autocua-vs-kane-cli.md)
- [AutoCua vs Kernel](https://www.anchorterminal.com/compare/autocua-vs-kernel.md)
- [AutoCua vs Lightpanda](https://www.anchorterminal.com/compare/autocua-vs-lightpanda.md)
- [AutoCua vs Notte](https://www.anchorterminal.com/compare/autocua-vs-notte.md)
- [AutoCua vs Playwright MCP](https://www.anchorterminal.com/compare/autocua-vs-playwright-mcp.md)
- [AutoCua vs Pomerado](https://www.anchorterminal.com/compare/autocua-vs-pomerado.md)
- [AutoCua vs Puppeteer](https://www.anchorterminal.com/compare/autocua-vs-puppeteer.md)
- [AutoCua vs Puppeteer (archived MCP reference server)](https://www.anchorterminal.com/compare/autocua-vs-puppeteer-reference-server-archived.md)
- [AutoCua vs Robocorp](https://www.anchorterminal.com/compare/autocua-vs-robocorp.md)
- [AutoCua vs Selenium](https://www.anchorterminal.com/compare/autocua-vs-selenium.md)
- [AutoCua vs Skyvern](https://www.anchorterminal.com/compare/autocua-vs-skyvern.md)
- [AutoCua vs Steel](https://www.anchorterminal.com/compare/autocua-vs-steel.md)
- [AutoCua vs TinyFish](https://www.anchorterminal.com/compare/autocua-vs-tinyfish.md)
- [Browser Use vs Tilion Fortress](https://www.anchorterminal.com/compare/browser-use-vs-tilion-fortress.md)
- [Browserbase vs Tilion Fortress](https://www.anchorterminal.com/compare/browserbase-vs-tilion-fortress.md)
- [Browserless vs Tilion Fortress](https://www.anchorterminal.com/compare/browserless-vs-tilion-fortress.md)
- [BxPlaywright vs Tilion Fortress](https://www.anchorterminal.com/compare/bx-playwright-vs-tilion-fortress.md)
- [Chrome DevTools MCP vs Tilion Fortress](https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-tilion-fortress.md)
- [Functionize MCP server vs Tilion Fortress](https://www.anchorterminal.com/compare/functionize-mcp-vs-tilion-fortress.md)
- [Hyperbrowser vs Tilion Fortress](https://www.anchorterminal.com/compare/hyperbrowser-vs-tilion-fortress.md)
- [Kane CLI vs Tilion Fortress](https://www.anchorterminal.com/compare/kane-cli-vs-tilion-fortress.md)
- [Kernel vs Tilion Fortress](https://www.anchorterminal.com/compare/kernel-vs-tilion-fortress.md)
- [Lightpanda vs Tilion Fortress](https://www.anchorterminal.com/compare/lightpanda-vs-tilion-fortress.md)
- [Notte vs Tilion Fortress](https://www.anchorterminal.com/compare/notte-vs-tilion-fortress.md)
- [Playwright MCP vs Tilion Fortress](https://www.anchorterminal.com/compare/playwright-mcp-vs-tilion-fortress.md)
- [Pomerado vs Tilion Fortress](https://www.anchorterminal.com/compare/pomerado-vs-tilion-fortress.md)
- [Puppeteer (archived MCP reference server) vs Tilion Fortress](https://www.anchorterminal.com/compare/puppeteer-reference-server-archived-vs-tilion-fortress.md)
- [Puppeteer vs Tilion Fortress](https://www.anchorterminal.com/compare/puppeteer-vs-tilion-fortress.md)
- [Selenium vs Tilion Fortress](https://www.anchorterminal.com/compare/selenium-vs-tilion-fortress.md)
- [Skyvern vs Tilion Fortress](https://www.anchorterminal.com/compare/skyvern-vs-tilion-fortress.md)
- [Steel vs Tilion Fortress](https://www.anchorterminal.com/compare/steel-vs-tilion-fortress.md)
- [Tilion Fortress vs TinyFish](https://www.anchorterminal.com/compare/tilion-fortress-vs-tinyfish.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
