Skip to content
browserherdDocs
Browserherd documentation

Build with cloud browsers

Browserherd gives developers secure, isolated Chromium sessions through standard browser automation libraries. Connect with Playwright, Puppeteer, Selenium, or any Chrome DevTools Protocol client.

Start here

Launch your first session

Create an API key, build a WebSocket endpoint, and open a page with Playwright.

Read the quickstart →Integration

Connect Playwright

Use connectOverCDP to run existing Playwright workflows on Browserherd.

View Playwright guide →Integration

Connect Puppeteer

Pass the Browserherd WebSocket URL as Puppeteer’s remote browser endpoint.

View Puppeteer guide →Reference

Handle errors

Understand authentication, validation, concurrency, timeout, and infrastructure errors.

View error reference →

How Browserherd works

Your code connects to a managed Chromium session over a secure WebSocket. Browserherd creates an isolated runtime, applies your session configuration, and keeps the browser available until you disconnect or the configured TTL expires.

wss://connect.browserherd.com?token=YOUR_API_KEY&sessionTTL=900WSS
  1. Authenticate with the project API key from your Browserherd dashboard.
  2. Configure the session using query parameters such as region, timeout, recording, profile, and viewport.
  3. Connect with Playwright, Puppeteer, Selenium, or a CDP client.
  4. Close the browser when work is complete so usage stops immediately.

Your first connection

Install the lightweight Playwright package and replace the local browser launch with a Browserherd endpoint.

TERMINAL
npm install playwright-core
JAVASCRIPT · PLAYWRIGHT
import { chromium } from "playwright-core";

const endpoint = "wss://connect.browserherd.com" +
  "?token=YOUR_API_KEY&sessionTTL=900&region=us-east-1";

const browser = await chromium.connectOverCDP(endpoint);
const context = browser.contexts()[0];
const page = await context.newPage();

await page.goto("https://example.com");
console.log(await page.title());
await browser.close();
The API key shown here is a placeholder. Never commit a real key to source control.

Core concepts

ConceptDescription
ProjectGroups API keys, usage, browser sessions, and billing for a workload or team.
SessionOne isolated Chromium runtime created when your client connects.
ProfileOptional persisted browser state that can be reused across sessions.
RecordingOptional visual capture used for debugging and session replay.
Browser timeUsage measured while a cloud browser session remains connected and running.