
Browserless
https://github.com/browserless/browserless- Category
- Developer Tools
- Rank
- No. 936Tools index
- Listed in
- #13 Control a browser
- Pricing
- Freemium
- Platform
- web
- Type
- TOOL
- Builder
- browserless
- GitHub
- 13.6k stars
- Added
- Aug 12, 2026
About
Browserless runs Chrome, Firefox, and WebKit in Docker and exposes browser sessions over WebSocket and REST APIs. It supports existing Puppeteer and Playwright scripts, persistent sessions, scraping, crawling, CAPTCHA solving, residential proxies, an MCP server, managed cloud, and self-hosting.
What it does
Browserless turns browser automation into a shared service, so application code connects to a maintained browser process instead of launching one locally. It manages concurrent work, queues excess sessions, applies timeouts, exposes debugging tools, and keeps the service alive when a browser crashes.
Why it's ranked here
The project addresses the operational failures that make browser automation painful in cloud and CI environments. Its strongest case is compatibility with standard automation clients, combined with admission controls, session debugging, health checks, and several deployment models. The licensing and premium feature boundary require careful evaluation.
What's good
Existing Puppeteer and Playwright code can connect without adopting forked client libraries. Operators get configurable concurrency, queueing, timeouts, authentication, metrics, health controls, and a live debug viewer. Request schemas produce clear client errors, while unexpected failures are logged without returning internal paths or stack details.
Tradeoffs
The open-source offering covers core automation, while persistent state, session replay, advanced anti-detection, residential proxying, webhooks, and several higher-level data APIs sit in paid offerings. Proprietary commercial applications and closed-source CI require a commercial license. ARM64 is supported, but Chrome and Edge compatibility there is described as limited.
How to use it well
Use Browserless when a team already has Puppeteer or Playwright scripts and wants centralized browser infrastructure for testing, development, scraping, screenshots, PDFs, or production automation. Start with the local container, set explicit concurrency and timeout limits, then choose managed or self-hosted deployment. It runs scripts reliably, but does not replace writing their automation logic.
Technical notes+
The package is an ES module with typed exports and a browserless binary declared in package.json; its engines require Node.js 24 or newer and npm 11.10.0 or newer. src/server.ts handles HTTP and WebSocket traffic, token authorization, body and query schema validation, CORS, bounded payload reads, and sanitized 500 responses. src/router.ts compiles route matchers, applies queue and timeout limiting, injects browser instances, and fires lifecycle hooks. src/config.ts maps environment variables into concurrency, queue, timeout, health, storage, CORS, and browser-version behavior. src/shim.ts translates legacy launch parameters and moves query tokens into authorization headers. src/hooks.ts preserves extension points for downstream Docker images, while src/index.ts performs graceful shutdown on common process signals.
Observed
- License
- SSPL-1.0 or Browserless Commercial License; proprietary commercial applications and closed-source CI require a commercial license.
- Primary language
- TypeScript, compiled with the TypeScript compiler into JavaScript and declaration exports.
- Packaging
- Published as an npm ES module with a typed library export and a browserless command-line binary.
- Container install
- The documented local quickstart runs the Chromium image from GitHub Container Registry with Docker.
- Interfaces
- HTTP REST routes, WebSocket browser routes, Puppeteer and Playwright connections, an npm library, a CLI, and a premium MCP server.
- Platform support
- Docker deployment and ARM64 support, including Apple Silicon; Chrome and Edge have limited ARM64 compatibility.
- Deployment models
- Open-source self-hosting, Enterprise Docker, managed self-serve cloud, and private enterprise deployment.
Read from README.md, package.json, src/index.ts, src/server.ts, src/http.ts, src/shim.ts, src/hooks.ts, src/token.ts, src/types.ts, src/utils.ts, src/config.ts, src/logger.ts, src/router.ts.
Tags
Tech Stack
Media

Comments (0)
No comments yet
Indexed by a proprietary survey. Corrections welcome.