Browserless vs. Skyvern: managed Chrome or vision-agent workflow platform?

Browserless and Skyvern are easiest to separate by the shape of the task. "Render this URL to PDF," "scrape this page," "run our existing Playwright tests in the cloud" points to Browserless. "Log into 80 supplier portals every Friday, download invoices, extract line items, validate the result, and send failures to an ops queue" points to Skyvern. Browserless is developer-first browser infrastructure with CDP, BrowserQL, REST shortcuts, and Docker self-host. Skyvern is an open-source vision-LLM workflow platform with YAML workflows, native 2FA/TOTP, structured extraction, and an RPA-replacement buyer. They are both useful for web automation; they are not hired for the same job.

At a glance

What is Browserless?

Browserless is managed Chrome over a single CDP WebSocket endpoint — Puppeteer, Playwright, or Selenium connect with a one-line change from local. The product is intentionally low-level and developer-first: BrowserQL (a declarative scraping query language with built-in stealth heuristics), REST shortcut endpoints (/content, /screenshot, /pdf, /scrape, /screencast), Smart Scrape API, Lighthouse performance testing, MCP server integration, and a Reconnect API for session resumption. Bot detection, fingerprint tuning, and CAPTCHA solving are bundled; residential proxies are BYO or via metered add-ons.

The hybrid deploy story is the wedge: managed cloud, private deployment, or full self-host on Docker with the same API surface. 173M+ Docker pulls, 12K+ GitHub stars, eight years in production, 99.9% uptime; named customers include Microsoft, Heroku, Webflow, Samsara, and CVS Health. Pricing is "units" (1 unit = 30 seconds of browser connection time): Free 1,000 units / 2 concurrent / 1-min cap, Prototyping $25/mo for 20,000 units / 15 concurrent / 15-min, Starter $140/mo / 40 concurrent, Scale $350/mo / 100 concurrent, with proxy (6 units/MB) and CAPTCHA (10 units/solve) add-ons metered separately. Native integrations include LangChain, Zapier, and n8n. SOC 2 / HIPAA posture is not surfaced in our public sources.

What is Skyvern?

Skyvern is an open-source AI browser-automation platform that uses vision-LLMs plus a planner-actor-validator agent loop to drive websites the way a human would — instead of relying on XPath/CSS selectors. The pitch is explicit: replace brittle Selenium/Playwright scripts and human SOPs across portal-driven verticals — healthcare/EHR integration, insurance quoting, government forms (SS4 filings, IRS), procurement / AP downloading invoices from supplier portals, payroll, mortgage, job applications.

Skyvern 2.0 hit 85.85% on WebVoyager (vs ~45% for Skyvern 1.0); the full eval is published at eval.skyvern.com. Web Bench (5,750 tasks / 452 sites, co-built with Halluminate) focuses on WRITE tasks — forms, logins, downloads — where most agents fail. The Validator inspects the screen after each action to detect "fake successes." Multi-step workflows are defined in YAML; structured JSON/CSV output schemas validate extraction. Native 2FA/TOTP and CAPTCHA solving are built in. Credentialing is native plus integrations with Bitwarden, 1Password, and Azure Key Vault — credentials never sent to the LLM. A "Route Memorization" / compile-to-code engine lets the agent solve a workflow once and compile to a fast/cheap Playwright script that self-heals via the LLM when it breaks.

The platform is Apache-licensed open source; you can self-host it (often the choice for health-tech buyers) or run on Skyvern Cloud at ~$0.10 per step/page. Compliance is SOC 2 Type 2 + HIPAA. Funding is a $2.7M seed (Dec 2025), 3,000+ GitHub stars at HN launch and growing. Integrations include Zapier, Make.com, n8n, plus a REST API and an MCP server.

How they compare

Category: substrate vs. complete tool

This is the entire question. Browserless gives you managed Chrome with a CDP endpoint and shortcut REST routes; you write the script. Skyvern gives you a workflow platform with a vision agent loop already running — you describe the goal in YAML, define the schema, and the platform runs the workflow end to end including auth, CAPTCHA, validation, and structured extraction.

A useful test: if you said "log into Acme Vendor's portal, download the past month's invoices as PDF, extract line items into a CSV, drop into S3, and re-run weekly," who wires that up?

• Browserless: you wire it up in Puppeteer/Playwright code, with your own auth handling, your own retry logic, your own validator, your own scheduler.
• Skyvern: you write the YAML workflow, configure the credential, hand off the rest to the platform.

Both answers are valid; they imply very different teams and very different unit economics.

Why neither is on the public leaderboard

Neither Browserless nor Skyvern is on the public Browser Arena leaderboard, and the two omissions are factually consistent with their categories. Browser Arena measures session-shape browser runtimes — provision a CDP endpoint, run lifecycle stages against it. Browserless's primary surface is request-shape (REST shortcuts /screenshot, /pdf, /scrape, BrowserQL queries) plus a CDP endpoint for legacy scripts; the benchmark target shape isn't the same as Browserless's product shape. Skyvern is a workflow platform running on top of someone else's browser with vision-LLM steps and a validator inspecting every action — there's no session endpoint to point a benchmark harness at. Don't pick this pair on a head-to-head speed contest; the two products aren't even the same shape, and neither is benchmarked as a runtime in the public dataset.

Authentication and credentials

Skyvern ships native 2FA/TOTP, CAPTCHA solving, anti-bot/proxy network with ZIP-code-level geographic targeting, and a credential vault plus integrations with Bitwarden, 1Password, and Azure Key Vault — credentials never reach the LLM. For per-customer-account identity in a single workflow (a procurement bot logging into vendor X with vendor X's creds), this is a clean primitive.

Browserless leaves identity to your code. Data dirs, env vars, your own secret store, your own 2FA orchestration. For an engineering team that already has secret management and identity in their stack, this is the right primitive. For an ops team without that infrastructure, Skyvern's batteries-included posture is the easier sell.

Open source and self-host

Both ship open source — but for different layers. Browserless's Docker self-host puts the same managed-cloud API into your VPC. Skyvern's Apache-licensed open source puts the entire platform — agent, workflows, validator, MCP server — into your environment. The two open-source stories don't replace each other; you might self-host Browserless to provide the browser substrate, then run a separate workflow platform on top.

Pricing model

Browserless: per-unit (1 unit = 30s of browser connection time), concurrency caps, $25/mo Prototyping ≈ 167 browser-hours, with proxy and CAPTCHA add-ons separate. Predictable per-hour for steady workloads.

Skyvern: ~$0.10 per step/page on Skyvern Cloud, tiered Basic/Pro/Enterprise plans (no public dollars on tiers — flag). OSS self-host is free if you run it. The dichotomy is browser-hour metering versus per-step value pricing. A noisy variable scrape costs less per browser-hour on Browserless; a high-value low-volume portal flow (filing a tax form, downloading a single invoice) costs less per outcome on Skyvern.

Observability

Browserless: per-session debugger UI, session replay endpoint with customer-chosen retention. Skyvern: live viewport streaming, action viewer, run logs, full eval results published at eval.skyvern.com. Both are competent at their layer; they're observing different things — Browserless watches the browser session, Skyvern watches the workflow reasoning.

Compliance

Skyvern: SOC 2 Type 2 + HIPAA. The HIPAA + open-source-and-self-hostable combination is a genuine wedge for health-tech. Browserless: SOC 2 / HIPAA posture not surfaced in public sources — treat as "not in our sources" rather than confirmed gap, but flag in procurement.

When to choose Browserless

• You have engineers writing Puppeteer / Playwright / Selenium code and you want managed Chrome under it.
• Selenium-grid migration: a fleet of legacy scripts and you want managed Chrome with the same API.
• Docker self-host inside a VPC is a hard requirement (data-residency, on-prem, internal-only).
• BrowserQL's declarative-scraping-with-stealth-heuristics is the right shape for your workflows.
• LangChain, Zapier, n8n integrations are part of your stack.
• Steady-state concurrency in the 2-100 range with predictable unit-based pricing.
• The job is "scrape, screenshot, PDF, lighthouse" — request-shaped, not workflow-shaped.

When to choose Skyvern

• You're an ops team replacing RPA — UiPath, Automation Anywhere, Power Automate — and you don't want to write Playwright code.
• Portal-driven workflows: procurement / AP downloading invoices from dozens of supplier portals, healthcare/EHR, government/regulatory forms, insurance quoting, payroll, mortgage, job applications.
• "One workflow, many sites" cross-portal capability matters — the agent adapts to layout differences across vendors.
• Native 2FA/TOTP/CAPTCHA + credential vault + Bitwarden/1Password/Azure KV integrations are out-of-the-box requirements.
• You want open-source-and-self-hostable for HIPAA / on-prem reasons; Apache license is acceptable to your legal team.
• Pricing per outcome (~$0.10/step) maps better to your unit economics than per-browser-hour.
• The job is "log in, fill the form, download the invoice, validate, extract" — workflow-shaped, not request-shaped.

A third option: Notte

Worth a look: Notte (notte.cc)

Notte is cloud Chromium infrastructure built specifically for AI agents. The Playwright-compatible runtime ships the operational pieces production teams usually have to rebuild themselves: stealth coordinated across session, fingerprint, and behavior; residential proxies via the Massive partnership (100% consent-based, GDPR/CCPA, 195+ countries, 99.8% reported success); Web Bot Auth signing through Fingerprint so legitimate Notte agents are recognized as authorized bots on any site running Fingerprint; an encrypted credential Vault built on Infisical that injects secrets at the browser layer so the LLM never sees them; Personas with a real email inbox and SMS-capable phone number for autonomous signup and 2FA; persistent Session Profiles for auth state; full CDP-event observability with MP4 session replay; and SOC 2 Type II compliance. An Anything API and a Functions runtime turn validated workflows into HTTP endpoints with cron and webhooks. Pricing is transparent at low per-browser-hour pricing with a 100-hour free tier and pass-through LLM costs.

Notte is the runtime substrate Browser Use- and Skyvern-style agents could run on top of, with Vault, Personas, Web Bot Auth signing, and replay built in. Where Browserless is request-shaped (/screenshot, /pdf, /scrape), Notte is session-based with persistent auth state. Where Skyvern is workflow-platform-only (no Playwright-compatible session you can drop into your own code), Notte ships the cloud Chromium runtime as the primary product, with the Anything API on top for teams who want workflow productization without giving up the SDK shape. Notte ranks #1 overall on the public Browser Arena leaderboard, driven by top-tier speed and the lowest hourly cost on the board.

Verdict

This isn't a head-to-head; it's a category fit decision. Pick Browserless if you have engineering capacity, your scripts already exist or will be written by your team, your job is request-shaped or session-shaped browser primitives, and you might want Docker self-host inside your VPC. Pick Skyvern if you're replacing portal-based RPA, you don't want to write Playwright code, your workloads are workflow-shaped (multi-step, authenticated, validated, schema-extracted), and you want either OSS self-host or a per-outcome cloud price. Both are credible open-source plays at their respective layers. Don't pick on lifecycle speed — neither is on the public Browser Arena leaderboard, and the omissions are factually accurate framing for their respective categories: Browserless is a request-shape product, Skyvern is a workflow platform on top of someone else's browser. Pick on the job to be done.