Loading page
Loading page
Developer tools · Browserbase alternative
Run headless Chrome as a service, and connect your Puppeteer or Playwright scripts to it over the network.
Browserless runs headless browsers inside Docker and lets your code connect to them over the network. Your Puppeteer or Playwright script points at the Browserless WebSocket address instead of starting a local Chrome. Browserless handles the browser, the fonts, the queue and the crashes.
It also has REST APIs for common jobs, so you can make a PDF, take a screenshot or collect data with a single HTTP call and no browser code at all. A debug viewer lets you watch sessions as they run.
Browserless is for developers who automate browsers: PDF and screenshot services, scrapers, end-to-end tests and AI agents that browse. It helps when you do not want Chrome and its dependencies inside every app container.
Hosted browser services charge per session or per minute. A self-hosted Browserless runs as many sessions as your server can handle. The pages you visit and the data you collect stay inside your own service.
The trade-off: browsers use a lot of memory and CPU, so set a sensible concurrency limit. Keep BROWSERLESS_TOKEN secret, because anyone with it can run browsers on your server. The license is SSPL or commercial, so check it fits your use. This template uses the latest Chromium image tag. You look after updates.
Containers: ghcr.io/browserless/chromium:latest
Step 1
Choose the Starter plan. It costs $20 a month and runs up to 3 apps.
Step 2
Open App templates in the dashboard, choose Browserless, and click Deploy. We set up the containers, secrets and domain.
Step 3
Wait a few minutes for the first deploy, then open your new URL and finish the Browserless setup screen.