Wield vs Skyvern: what each does and when to pick it
Skyvern is an open-source browser workflow tool. It uses vision-capable LLMs instead of hard-coded selectors, and it adds a no-code workflow builder. Its core is licensed under AGPL-3.0. Wield runs fixed site recipes in your own browser with no model in the loop. Its executor, bridge, MCP server and recipe format are MIT-licensed. Skyvern suits unattended workflows on arbitrary sites. Wield suits your repeated, logged-in tasks.
What Skyvern is
Skyvern offers a Playwright-compatible SDK with AI features, plus a no-code workflow builder. Its README says it uses vision-capable LLMs rather than hard-coded selectors. The core is AGPL-3.0. Anti-bot measures in its managed cloud are not part of the open-source repository. Skyvern Cloud adds managed, parallel instances, a proxy network and CAPTCHA solving. To self-host, run pip install "skyvern[all]" and then skyvern quickstart, or use Docker Compose for Postgres, the API and the UI.
Side-by-side
| Wield | Skyvern | |
|---|---|---|
| Approach | Fixed site recipes, with no model in the loop | Vision LLMs decide the steps |
| Where it runs | Your browser, through the Wield extension | Self-hosted, or Skyvern Cloud |
| License | MIT planned for the executor, bridge, MCP server and recipe format; source not public yet | AGPL-3.0 for the core |
| Model cost per run | $0 | Vision LLM calls on each run |
| Logins | Your existing browser session | 2FA by TOTP, email or SMS; credential-manager integrations |
| CAPTCHAs | Stops with site_challenge; you solve it in your tab | Solved in the managed cloud |
Logins and your data
Skyvern supports 2FA through TOTP, email and SMS. It integrates with Bitwarden, 1Password, LastPass and a custom HTTP credential service, and its agent.login uses stored credentials. Its README does not say how those credentials are stored, so check the code before you rely on it.
Wield never reads or copies cookies or passwords. It uses the session your browser already has. Passwords and cookies never leave your computer, and results never pass through wield.run. When a site shows a check, Wield stops and asks you to solve it in your own tab.
When Skyvern is the better choice
- You want unattended, multi-step workflows on sites that have no recipe.
- You want a no-code workflow builder.
- You want to self-host the whole stack.
When Wield is the better choice
- You repeat a personal, logged-in task on a supported site.
- You want credentials to stay on your device.
- You want no model cost per run.
FAQ
Is Skyvern free?
Self-hosting is open source under AGPL-3.0. For managed cloud pricing, see Skyvern's pricing page. We do not state its prices here.
What does AGPL-3.0 mean for me?
AGPL-3.0 has its own conditions, including for software you run as a network service. Read the license text before you build on it.
How does Wield handle a site with bot protection?
It stops with site_challenge and asks you to solve the check in your own tab. Wield does not solve bot checks.
Sources
- Skyvern on GitHubgithub.com
- Skyvern pricingskyvern.com