Browser UseBrowser Use · computer-usevs
SkyvernSkyvern · computer-use
The two leading open-source browser-agent frameworks. Browser Use is the larger ecosystem and DOM-first; Skyvern leans on computer vision to operate unfamiliar sites without per-site scripting.
agentlist.io · documented attributes · sources and dates shown per value
Compare the same attributes
Every entry uses the same category fields. Open a source to check the scope and date behind a value. Not documented means we have no supported value, not that a feature is absent.
| Attribute | Browser UseProduct docs checked · 2026-11-05 | SkyvernAwaiting documentation review |
|---|---|---|
| Common attributesDirectory metadata and source-documented values. Not documented is an evidence gap, not a negative claim. | ||
| CategoryAgentlist's buyer category; directory classification rather than a product capability. | Browser and computer use | Browser and computer use |
| Entry typeDirectory classification distinguishing products, frameworks, infrastructure and protocols. | framework | product |
| Directory coverageHow the entry entered this directory; not a quality rating or a claim that every field is verified. | Cataloged | Cataloged |
| Recorded availabilityAvailability classification in the directory; check the source and review date before relying on current access. | active | active |
| InterfacesDocumented ways a person or application interacts with the entry. | Not documentedRecorded sourcesRecorded catalog specification; availability and terms may have changed. | Not documentedRecorded sourcesRecorded catalog specification; availability and terms may have changed. |
| Execution / hostingWhere the documented service or workload runs; this is not a data-residency guarantee. | Not documentedRecorded sourcesRecorded catalog specification; availability and terms may have changed. | Not documentedRecorded sourcesRecorded catalog specification; availability and terms may have changed. |
| Pricing basisSource-described price and billing basis. Different units and plans are not directly equivalent. | Not documentedRecorded sourcesRecorded catalog specification; availability and terms may have changed. | Not documentedRecorded sourcesRecorded catalog specification; availability and terms may have changed. |
| LicenseDocumented license for the specified component or offering. | Not documented | Not documented |
| Browser and computer useComparable questions for this category. Sources and dates describe the evidence; no performance ranking is implied. | ||
| Browser operationControls a real browser to navigate and interact. | Not documented | Not documented |
| Desktop controlOperates a desktop using screenshots, pointer or keyboard actions. | Not documented | Not documented |
| API / SDK accessDesigned to be embedded or driven through an API or SDK. | Not documented | Not documented |
| Self-hostingCan be deployed on the user's infrastructure for the cited component. | Not documented | Not documented |
| Persistent browser profileRetains browser state across sessions through a documented profile mechanism. | Not documented | Not documented |
Pick which
pick Browser Use if
You want the biggest community, MIT licensing, and a managed cloud option from the same team.
pick Skyvern if
Your workflows span many different sites and you don't want to maintain selectors — vision-first is the point.
watch out
Licenses differ (MIT vs AGPL) — check embedding terms; and on both, login-gated flows hit bot defenses.
Feature notes
- Browser Use
- 01OSS Python framework (MIT)
- 02DOM + vision grounding
- 03Cloud API + managed sessions
- 04Stealth/proxy options
- 05Structured output
- 06Large community ecosystem
- Skyvern
- 01OSS (AGPL) + managed cloud
- 02Vision-based navigation
- 03No per-site scripting
- 04Form-filling + workflows
- 052FA/captcha-aware hooks
- 06API + SDKs
Frequently asked
Browser Use or Skyvern — which should I pick?
The two leading open-source browser-agent frameworks. Browser Use is the larger ecosystem and DOM-first; Skyvern leans on computer vision to operate unfamiliar sites without per-site scripting. Pick Browser Use if: You want the biggest community, MIT licensing, and a managed cloud option from the same team. Pick Skyvern if: Your workflows span many different sites and you don't want to maintain selectors — vision-first is the point.
Is Browser Use or Skyvern cheaper?
Browser Use: Free OSS (MIT); Cloud free tier + usage-based plans. Skyvern: Free OSS; Cloud pay-per-task credits. These are recorded catalog prices, not a fresh quote. Check vendor pricing for current plans, usage charges and seat terms.
Does Browser Use or Skyvern run locally?
Browser Use hosting: local, cloud. Skyvern hosting: local, cloud. Interfaces differ too: Browser Use exposes api/browser, Skyvern exposes api/browser.
Are Browser Use and Skyvern still maintained?
Recorded catalog status — Browser Use: actively maintained. Skyvern: actively maintained. Check the linked sources for current availability; the catalog's creation date is not a product verification date.