Stop babysitting Chrome. It's a one-line change.

Swap puppeteer.launch() for puppeteer.connect() and the memory leaks, security patching, and 3am pages become our problem. Your Puppeteer or Playwright code stays exactly as it is.

Run your script free Read the docs

No credit card. 1,000 free units a month.

import Browserless from "@browserless.io/bap-ts";

const TOKEN = "YOUR_API_TOKEN_HERE";

const browser = Browserless.connect({
  browserWSEndpoint: "wss://production-sfo.browserless.io/chromium/bql",
  token: TOKEN,
});

const page = await browser.newPage();
await page.goto("https://example.com");

await browser.close();

Most scripts only change the connection line. Custom launch flags and long-running sessions are covered in the docs.

175M+

Docker pulls

2017

Open source since

99.9%

Uptime, automatic failover

SOC 2

Type II certified

Pricing you can predict before you sign up

No quote calls, no surprises on the first invoice. Here is the whole model.

1 unit = up to 30 seconds of browser time per connection.

A 20-second scrape costs 1 unit. A 90-second job costs 3. Reconnecting to a session starts a new unit.

Free

1,000 units/mo

2 concurrent browsers
2-minute max session time
No credit card

Prototyping

$35/mo

20,000 units/mo

5 concurrent browsers
15-minute sessions
$25/mo on annual

Starter

$200/mo

180,000 units/mo

30 concurrent browsers
30-minute sessions
$140/mo on annual

Scale

$500/mo

500,000 units/mo

80 concurrent browsers
60-minute sessions
$350/mo on annual

Residential proxies cost 6 units per MB, charged only when you route through them.

Automatic CAPTCHA solving costs 10 units per successful solve. reCAPTCHA, Cloudflare Turnstile, DataDome, and more.

Traffic bursts queue automatically up to 2x your concurrency limit before any request is rejected.

The free plan stops at 1,000 units. It rejects requests instead of billing you.

Overage rates and annual discounts are on the pricing page.

What disappears from your on-call

Not adjectives. The specific work that stops being yours.

Memory leaks and zombie processes

Chrome instances leak memory over time. Browserless recycles browsers automatically, so you never SSH in to kill a hung process again.

Sessions fighting for CPU and RAM

Concurrent sessions compete for resources on shared boxes. Every Browserless session runs isolated, so one bad page can't take down the rest of your jobs.

Chrome version and security patching

Keeping browsers patched is a treadmill that never ends. We keep the runtime up to date so a Chrome release never breaks your pipeline.

Capacity planning and load balancing

Our load balancer routes new sessions away from busy machines, and bursts queue instead of failing. You stop guessing how many servers Tuesday needs.

Three regions: San Francisco, London, and Amsterdam, on every plan. Live history at status.browserless.io.

Keep your code. Keep your exit.

Browserless is the only managed browser platform you can also run yourself. Start on our cloud with your existing scripts, move to a dedicated managed deployment or a self-hosted Docker image whenever cost, scale, or compliance demands it. The connection string is the only thing that changes.

The open-source image runs Puppeteer, Playwright, and the REST APIs under SSPL-1.0; closed-source commercial use needs a commercial license, and BrowserQL, the BAP SDK, plus the stealth and CAPTCHA stack ship in the licensed Enterprise image. Details in the self-hosting docs.

Cloud

Fully managed. Connect in minutes.

Managed Cloud

Dedicated infrastructure in your region.

Self-hosted

Your infrastructure. Full control.

When a site blocks you, there's an escalation path

Stealth browsers, residential proxies at 6 units per MB, and automatic CAPTCHA solving at 10 units per successful solve. All included on every plan, charged only when you use them.

We won't promise you'll never get blocked. We'd rather you test it against your own target site on the free plan.

Your request

Stealth, proxies, CAPTCHAs

Target site