Browserless

Browserless — Self-hostable headless Chrome service; BrowserQL for bot-heavy sites. Browserless is the oldest product here and the only one most teams have already run in Docker. The cloud service bills time in short units and exposes the same CDP endpoint as the self-hosted image, so moving between them is a URL change. BrowserQL, its newer GraphQL-style API, is the stealth-first path: declarative navigation with challenge handling and a live takeover URL built in. Founded 2018. Open source.

We track it in 1 comparison — Browser APIs — so every claim below is a cell in a table you can open and check rather than an impression. Across those rosters it sits against 12 other tools, and what follows is where it visibly separates from them.

Where it wins.

• Human handoff — Yes, which only 3 of 13 tools here manage.
• Open-source core — Yes, which only 3 of 13 tools here manage.
• Browser regions — us-west, eu-west, eu-central, 2nd of 9.

Each of those is ranked against the whole roster on its category page, not against a hand-picked subset, so a first place here means first of everything we list.

Where it gives ground.

• GitHub stars — 10,000, 4th of 5. Self-hosted Playwright records 73,000.
• Agent API — No. Hyperbrowser records Yes.

None of these disqualify it on their own. They are the fields to check against your own requirements before you commit, because they are the ones where a competitor genuinely does better.

Provenance. 22 of 26 tracked fields carry a value for Browserless, and 7 of those cite a document you can open. Last verified 2026-07-01. Every figure keeps its own provenance — measured by us, claimed by the vendor, inferred, or community-reported — and we would rather print a dash than a guess.

Its nearest neighbour in our data is Airtop. Browserless is ahead on Open-source core (Yes against No) and CDP endpoint (Yes against Partial). Airtop takes Agent API (Yes against No) and Session persistence (Yes against Partial). That pattern repeats across the rest of the roster — see Browserless alternatives for the other rivals, each compared the same way.

Founded

2018

Licence

Open source

Fields we track

22 of 26

Last verified

2026-07-01

The pragmatic choice when you want the option to bring everything in-house later: the cloud and the container speak the same protocol. BrowserQL is a genuinely different product bolted alongside the classic API, and the two have diverging capabilities, which makes the docs harder work than they should be.

Human handoff

●Yes1st of 13

Inferred

Open-source core

●Yes1st of 13

Vendor-claimedverified 2026-07-01source

GitHub stars

10,0004th of 5

Inferred

Stealth mode

●Yes1st of 13

Vendor-claimedverified 2026-07-01source

CDP endpoint

●Yes1st of 13

Vendor-claimedverified 2026-07-01source

CAPTCHA solving

●Yes1st of 13

Vendor-claimedverified 2026-07-01source

Playwright

●Yes1st of 13

Vendor-claimedverified 2026-07-01source

Live view

●Yes1st of 13

Inferred

Browserless is the right call in these situations, each one drawn from a field we actually record:

• Teams that expect to self-host eventually.
• Screenshot and PDF pipelines at steady volume.
• Declarative unblocking without adopting an agent framework.
• Human handoff is your binding constraint. Browserless records Yes, which only 3 of the 13 tools in the Browser APIs roster do. We define that field as a documented pause-for-human path — hand a person a takeover URL for a login or 2FA prompt, then resume the automation in the same session.
• Open-source core is your binding constraint. Browserless records Yes, which only 3 of the 13 tools in the Browser APIs roster do. We define that field as a self-hostable core under a public licence, so you can leave.
• Browser regions is your binding constraint. Browserless records us-west, eu-west, eu-central, 2nd of 9 in the Browser APIs roster.

Reach for something else when any of the following is a requirement rather than a nice-to-have:

• GitHub stars. Browserless records 10,000, 4th of 5 in the Browser APIs roster. Self-hosted Playwright records 73,000 on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• Agent API. Browserless records No on the Browser APIs table. Hyperbrowser records Yes on the same field. If that is a hard requirement rather than a preference, start elsewhere.

We publish this block because a comparison that only lists what a tool is good at is marketing. Every figure above sits on the same page as its source, and the field definitions are on the category tables if you want to check how we measured them.

What we don't know. 4 of the 26 fields we track for Browserless are still blank: Anti-bot pass rate, Cold start, Max concurrency and Per browser-hour. Those render as dashes rather than as zeroes or assumptions, because an empty cell and a bad cell are not the same thing and only one of them is honest. If you know any of these figures and can point at a document, tell us.