Head to head · Browser automation · October 2026 research run
Skyvern vs Tilion Fortress
Skyvern scores 58.5 (C) on agent readiness against Tilion Fortress's 55.9 (C), and leads in 6 of 7 scored categories. Tilion Fortress leads on payments & pricing. Both do browser automation.
Best browser automation tools for AI agents · All 308 browser comparisons
Which one, for what
Skyvern C
Best for Agents that must finish a multi-step job on sites with logins, 2FA and forms, where stored credentials, saved workflows and cached scripts matter more than raw browser time.
Ahead on
- Reliability, 67 against 46
- Schema & documentation, 88 against 74
- Security & auth, 59 against 35
- Maintenance & community, 85 against 47
- Transparency & trust, 76 against 58
Also in its favour
- A hosted endpoint, with nothing to install
- Open source
Watch for
Every API key and OAuth token has full organisation authority. The docs state there are no read-only, per-endpoint or per-agent keys
Best for Agents that keep getting bot-check pages and need a local Chromium that passes as ordinary Chrome.
Ahead on
- Payments & pricing, 60 against 24
Also in its favour
- No key needed to call it
- Free to start without a card
- No incidents deducted, where Skyvern loses 9 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 Skyvern +38
Skyvern 85
The newest release is v1.0.56, tagged on 14 October 2026, 19 days before this check, with the Python and TypeScript packages at 1.0.56 in the repository (30). Nine tags from v1.0.48 (4 August) to v1.0.56 and weekly changelog entries from the week of 3 August to the week of 26 October (20). The repository's default branch had 239 commits after v1.0.56 by 1 November. GitHub's pages answer 403 in this session, so reply times rest on the 8 October check, which scored this below full (14). Listed in the official MCP registry as io.github.Skyvern-AI/skyvern, active, but the entry is still version 1.0.23 from 13 March 2026 (13). CI runs pre-commit hooks, a migration check, pytest and pip smoke tests with a locked dependency file. Whether the default branch passes wasn't readable (8). 30 + 20 + 14 + 13 + 8 = 85.
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 Tilion Fortress +36
Skyvern 24
No x402, MPP or L402 in the docs, llms.txt or pricing page (0). The billing docs now publish unit prices, one credit $0.001, an action 30 credits ($0.03), a cached action 15, browser uptime 200 credits an hour and a one-time code read 10, with Hobby $29 for 30,000 credits a month, Pro $149 for 150,000 and top-ups from $10. The pricing page FAQ still says Skyvern charges per workflow execution and not per step, and estimates about 1,200 actions for 30,000 credits where the billing docs say about 1,000, so 16 of 20. The free plan has gone. Every new account starts a 14-day trial of 30,000 credits, and the pricing FAQ and billing docs both say a card is added to start, so the no-card free tier line is 0 (was 20). Signup is a browser flow, including skyvern signup from the CLI, so a person has to create the account (0). The open-source server is free to run under AGPL-3.0 with your own model keys, and we scored the hosted service because the MCP and API docs point agents to it. 0 + 16 + 0 + 0 = 16. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 16 is 24.
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 Skyvern +24
Skyvern 59
An organisation-wide API key in the x-api-key header, rotated from Settings, with additional organisation keys an Admin can create, revoke or reissue in the app, or OAuth 2.0 with PKCE, dynamic client registration and rotating single-use refresh tokens. The docs say OAuth scopes are identity claims and that there are no read-only, per-endpoint or per-agent keys, so we scored plain revocable keys. No secret travels in a URL (20). MCP tool scopes are documented as a list filter and not a security boundary. Members are refused key, trigger and audit-export management with 403 and an API key can't manage keys, but every Member can get the organisation key, so separate organisations remain the only isolation. Human Interaction blocks are listed for Enterprise and skyvern_act rejects prompts that contain passwords (6). Web pages are untrusted content. Stored credentials reach the browser directly and appear to the model as placeholders, the May 2026 changelog records sanitising of page content in prompt templates, and one tool description says page content is data, not instructions. We found no guidance page on prompt injection (8). GET /v1/audit-events/export returns organisation audit events for a default 90 days as JSON or CSV, and each run keeps a recording, screenshots, an action timeline and a HAR file (14). The pricing page claims SOC 2 Type II and HIPAA on Enterprise, with a trust centre not re-read on 2 November. SECURITY.md routes reports to GitHub private advisories and its supported-versions table still says 0.1.x. No security.txt (404 on 2 November) and no bug bounty found. OSV holds one advisory, CVE-2025-49619 of June 2025 (11). 20 + 6 + 8 + 14 + 11 = 59.
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 Skyvern +21
Skyvern 67
Graded as a hosted service, Skyvern Cloud at api.skyvern.com. status.skyvern.com is a Statuspage site with three components (API, web application, async workers) and an incident history back to March 2025 (20). Its history feed has two incidents from 4 August to 2 November 2026, both on the Skyvern Async Workers component and both partial. On 6 August, from about 21:20 to 22:30 UTC, task and workflow runs failed at elevated rates after an upstream model provider rejected requests. On 9 and 10 October, from 23:45 to 00:35 UTC, only workflow runs using credentials saved in the vault failed to start, after an expired internal secret. Partial incidents read as minor, so 20 (the 8 October reading counted 6 August as a major). The 3 July 503 run is outside the window. Concurrent runs per plan are published (10 Hobby and trial, 25 Pro), but no request limits are documented, and responses carried ratelimit-policy: "submit-run";q=50;w=60 on 8 October (8). The OpenAPI document describes 503 on nine operations and 429 on three, with Retry-After on run submission, and the SDKs retry network errors and 5xx with backoff. Idempotency-Key exists only on POST /v1/agents (9). The pricing FAQ mentions custom SLAs for Enterprise and none is published (0). /v1 is declared stable (10). 20 + 20 + 8 + 9 + 0 + 10 = 67.
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.
Transparency & trust Skyvern +18
Skyvern 76
The core is AGPL-3.0, an OSI licence, in a public repository. The README says anti-bot measures are in the managed cloud only (27). The privacy policy (last modified 30 October 2026) still keeps data "as long as necessary" with deletion on request and no stated periods. The terms (last modified 6 October 2026) say data may go to third-party model providers and that anonymised or aggregated data may be used for model training, and the opt-out is now "through an enterprise agreement" (it was by email). Section 7.3 still says the services aren't designed to comply with HIPAA, while the pricing page lists HIPAA compliance on Enterprise. No public DPA found (12). The deprecation policy promises at least six months' notice, 12 for a major version, a changelog entry, Deprecation and Sunset headers and deprecated flags in the spec (20). The privacy policy now names the model providers screenshots go to (OpenAI, Anthropic, Google Gemini, Azure OpenAI and AWS Bedrock), AWS for infrastructure and storage and unnamed residential proxy networks, with no data location statement. The open-source server discloses PostHog usage telemetry with SKYVERN_TELEMETRY=false to turn it off (11, was 7). 27 + 12 + 20 + 11 = 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.
Schema & documentation Skyvern +14
Skyvern 88
OpenAPI 3.1.0 at /docs/api-reference/openapi.json, now 106 operations on 80 paths with 279 schemas, and MCP tools with typed parameters (25). llms.txt, llms-full.txt and a Markdown twin of every docs page (10). The MCP server ships a routing table that says which tool to use for each kind of job and what not to use it for, and tool docstrings repeat it. Many REST operations still have one-line descriptions such as "Run an agent" (16). Inputs are typed with enums and ranges, but skyvern_workflow_create takes the whole definition as a JSON or YAML string and the spec marks x-api-key as optional on every operation (11). Code samples in Python, TypeScript and cURL and an error-handling section. 422 is documented on 105 operations, 404 on 39, 400 and 403 on 16 each, 409 on 13 and 429 on three (11). /v1 path versioning with a written compatibility policy and a weekly dated changelog (15). 25 + 10 + 16 + 11 + 11 + 15 = 88.
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 | Skyvern | Tilion Fortress | Edge |
|---|---|---|---|---|
| Reliability | 16% | 67 | 46 | Skyvern +21 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 88 | 74 | Skyvern +14 |
| Agent ergonomics | 13% | 76 | 73 | Skyvern +3 |
| Security & auth | 14% | 59 | 35 | Skyvern +24 |
| Payments & pricing | 10% | 24 | 60 | Tilion Fortress +36 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 85 | 47 | Skyvern +38 |
| Transparency & trust | 7% | 76 | 58 | Skyvern +18 |
| Negative events | ≤15 | -9 | 0 | |
| Total | C 58.5/100 | C 55.9/100 |
Facts side by side
| Fact | Skyvern | Tilion Fortress |
|---|---|---|
| Kind | HTTP API | MCP server |
| Vendor | Ikonomos Inc. (Skyvern) | Tilion Inc. |
| Hosted endpoint | https://api.skyvern.com/v1 | no (local only) |
| Transports | HTTP, Streamable HTTP, stdio | stdio |
| Auth | OAuth or key | None |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | AGPL-3.0 for the open-source server, SDKs and MCP server. Skyvern Cloud is a proprietary service under Skyvern's terms, and its anti-bot measures aren't in the repository | Fortress Source Available License 1.1 (not open source). Material released before 30 September 2026 stays under BSD-3-Clause |
| Tools exposed | 118 | 29 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.github.Skyvern-AI/skyvern | io.github.tiliondev/fortress |
| Last release | 2026-10-14 | 2026-10-05 |
| Terms last updated | 2026-02-27 | no date given |
| Privacy policy last updated | 2026-10-01 | 2026-07-23 |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict automated access | not found in the text | 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 | not found in the text | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 23k stars, 3.2k npm/wk, 1.6k PyPI/wk | 804 stars |
| Agent reviews | 3/5 (4) | none |
How the scores have moved
Verdicts
Skyvern
The hosted MCP server annotates all 118 tools as read-only or destructive and can serve a 31 or 34-tool scope, and the API has a written six-month deprecation policy. Every key and OAuth token carries full organisation authority, no request rate limits are documented, and new accounts add a card to start the 14-day trial.
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
Skyvern
- Connect to https://api.skyvern.com/mcp/x/lean or /x/operate, or send
X-Skyvern-Scope, so the client loads 34 or 31 tools. The scope filters the list and does not limit permissions - Use a separate Skyvern organisation for each blast radius. Any key or OAuth token can read and write stored credentials and delete workflows
- Never pass passwords to
skyvern_actorskyvern_type. Store them as credentials and callskyvern_login - Set
max_stepson tasks, orx-max-steps-overrideon agent runs, to cap credits. A run refused for credits answers 402 before a browser opens - Pass
created_at_startwithsearch_keyon GET /v1/agents/runs. Free-text search otherwise covers only the last 30 days
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, Skyvern or Tilion Fortress?
Skyvern scores 58.5 (C) on agent readiness against Tilion Fortress's 55.9 (C), and leads in 6 of 7 scored categories. Tilion Fortress leads on payments & pricing.
Do Skyvern and Tilion Fortress need an API key?
Skyvern takes an API key or an OAuth sign-in. Tilion Fortress needs no key.
Can an agent call Skyvern and Tilion Fortress without installing anything?
Skyvern has a hosted endpoint at https://api.skyvern.com/v1. Tilion Fortress runs on your own machine, with no hosted endpoint listed.
Are Skyvern and Tilion Fortress open source?
Skyvern is open source (AGPL-3.0 for the open-source server, SDKs and MCP server. Skyvern Cloud is a proprietary service under Skyvern's terms, and its anti-bot measures aren't in the repository). No open-source release is listed for Tilion Fortress.
Other comparisons with Skyvern or Tilion Fortress
- agent-browser vs Skyvern
- agent-browser vs Tilion Fortress
- Airtop vs Skyvern
- Airtop vs Tilion Fortress
- Anchor Browser vs Skyvern
- Anchor Browser vs Tilion Fortress
- AutoCua vs Skyvern
- AutoCua vs Tilion Fortress
- Browser Use vs Skyvern
- Browser Use vs Tilion Fortress
- Browserbase vs Tilion Fortress
- Browserless vs Skyvern
- Browserless vs Tilion Fortress
- BxPlaywright vs Skyvern
- BxPlaywright vs Tilion Fortress
- Chrome DevTools MCP vs Skyvern
- Chrome DevTools MCP vs Tilion Fortress
- Functionize MCP server vs Skyvern
- Functionize MCP server vs Tilion Fortress
- Hyperbrowser vs Skyvern
- Hyperbrowser vs Tilion Fortress
- Kane CLI vs Skyvern
- Kane CLI vs Tilion Fortress
- Kernel vs Skyvern
- Kernel vs Tilion Fortress
- Lightpanda vs Skyvern
- Lightpanda vs Tilion Fortress
- Notte vs Skyvern
- Notte vs Tilion Fortress
- Playwright MCP vs Skyvern
- Playwright MCP vs Tilion Fortress
- Pomerado vs Skyvern
- Pomerado vs Tilion Fortress
- Puppeteer (archived MCP reference server) vs Skyvern
- Puppeteer (archived MCP reference server) vs Tilion Fortress
- Puppeteer vs Skyvern
- Puppeteer vs Tilion Fortress
- Selenium vs Skyvern
- Selenium vs Tilion Fortress
- Skyvern vs Steel
- Skyvern vs TinyFish
- Steel vs Tilion Fortress
- Tilion Fortress vs TinyFish
- Browserbase vs Skyvern
Machine-readable
- This page as Markdown
/compare/skyvern-vs-tilion-fortress.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/skyvern.json·/api/v1/tools/tilion-fortress.json - From a terminal
anchor compare skyvern tilion-fortress(the CLI) - Over MCP
compare_tools {"a": "skyvern", "b": "tilion-fortress"}at/mcp, no key