Launch one browser or thousands.
Capacity appears when your workload needs it and disappears when the session ends. No fleet sizing, warm pools, or browser images to maintain.
Cloud browsers, fully managed
A browser fleet on demand
Launch secure, isolated Chromium sessions through a single endpoint. Scale browser automation without managing servers, containers, browser updates, or session infrastructure.
- Playwright, Puppeteer, and CDP
- Usage-based scaling
- Live session visibility
BROWSERHERD / LIVE SESSIONRUNNING
Current pageProduct catalog
Session events1,248
- Region
- US EAST
- Browser
- CHROMIUM
- Recording
- ACTIVE
Connect with the tools you already use
PlaywrightPuppeteerSeleniumChrome DevTools
Cloud browser infrastructure
Everything your browser workloads need to run
Browserherd turns Chromium into reliable infrastructure your team can start, control, observe, and scale through code.
A clean environment for every run.
Each cloud browser runs in its own isolated environment. Use ephemeral sessions for clean starts or persistent profiles when workflows need continuity.
Run close to the systems you automate.
Select a region for each session to reduce latency and keep browser workloads close to their destination without operating distributed infrastructure.
See the browser, not just the error.
Open a live session, inspect console and network events, then replay completed runs so failed automation is easier to understand and fix.
Developer first
Keep your code. Change the browser.
Browserherd works with the libraries your team already uses. Replace the local Chromium process with a secure WebSocket endpoint and run the rest of your workflow as usual.
- 01Create a Browserherd project and API key
- 02Connect Playwright or Puppeteer over CDP
- 03Launch, observe, and scale sessions
import { chromium } from "playwright-core";
const browser = await chromium.connectOverCDP(
"wss://connect.browserherd.com?token=YOUR_API_KEY"
);
const context = browser.contexts()[0];
const page = await context.newPage();
await page.goto("https://example.com");
console.log(await page.title());
await browser.close();import puppeteer from "puppeteer-core";
const browser = await puppeteer.connect({
browserWSEndpoint: "wss://connect.browserherd.com?token=YOUR_API_KEY"
});
const page = await browser.newPage();
await page.goto("https://example.com");
console.log(await page.title());
await browser.close();curl --request POST "https://api.browserherd.com/v1/sessions" \
--header "Authorization: Bearer $BROWSERHERD_API_KEY" \
--header "Content-Type: application/json" \
--data '{
"region": "us-east-1",
"session_ttl": 900,
"session_recording": true
}' Endpoint ready · connect.browserherd.com
SESSION REPLAY · bh_8f2c04:18 / 06:54
00:0006:54
Debug in context
Go from failure to root cause faster
A browser error rarely tells the whole story. Browserherd keeps the visual and technical context around every run, so your team can reproduce less and resolve more.
Watch sessions live
See what the browser is doing while automation is running.
Replay completed runs
Review the exact path that led to a failure or unexpected result.
Inspect technical events
Use console output and network activity alongside the visual recording.
Built for production work
Cloud browsers for every stage of your workload
Give agents a reliable place to act.
Run long-lived, observable browser sessions with profile continuity and human visibility when workflows need intervention.
Move recurring workflows off local machines.
Operate Playwright, Puppeteer, and Selenium jobs without maintaining a browser cluster for internal tools and web applications.
Run critical journeys in clean browsers.
Start every test from a predictable environment and use recordings to understand the runs that fail.
Your code. Our browsers.
Launch your first cloud browser today
Start with a free project, connect your existing automation library, and scale when your workload is ready.