Give every test a clean start.
Run tests in ephemeral browser environments so cookies, cache, storage, and process state do not leak between jobs.
EPHEMERAL SESSIONSSolution / Automated testing
Ship with confidence in a real browser
Run critical Chromium journeys in clean, isolated cloud browsers. Parallelize test suites, observe active runs, and replay failures with the context your team needs.
- Clean test environments
- Parallel execution
- Failure replay
TEST RUN · RELEASE-2026.09.1842 / 48 PASSED
Test suite48 journeys queued
Cloud runners12 browsers active
Failure contextReplay captured
RUN INPARALLEL
- Passed
- 42
- Running
- 4
- Failed
- 2
Cloud browsers for your test pipeline
PlaywrightPuppeteerSeleniumCI workflows
More signal from every failure
Test the journey, not your browser infrastructure
Keep test logic in your existing framework while Browserherd provides clean Chromium sessions and the execution context around every run.
Finish large suites sooner.
Distribute independent journeys across on-demand cloud browsers without maintaining a permanent pool of test runners.
ELASTIC CONCURRENCYReplay what happened before the assertion.
Use visual recordings, console output, and network events to understand failures that cannot be explained by a stack trace alone.
SESSION REPLAYTesting workflow
From CI job to actionable failure
Use Browserherd as the remote Chromium layer behind your existing tests. Each run gets its own isolated session and optional recording.
- 01
Start a browser for each test worker
Your CI pipeline requests cloud sessions in parallel using a project API key.
- 02
Execute existing test code
Connect Playwright, Puppeteer, or Selenium over a standard endpoint and run the same selectors and assertions.
- 03
Capture the browser context
Record selected sessions and retain the console and network events needed for diagnosis.
- 04
Review failed journeys
Search test sessions by name or ID, replay the failure, and resolve the issue without rerunning locally.
TEST REPORT · CHECKOUT SUITE06:42 TOTAL
- guest-checkout.spec.ts
- 3.8s · us-east-1
- saved-payment.spec.ts
- 5.2s · us-east-1
- coupon-expiry.spec.ts
- 7.4s · us-east-1
- 14:52:21 expected total: $42.00
- 14:52:21 received total: $47.00
- 14:52:22 screenshot captured
- 14:52:22 session replay available
Debugging with context
Turn intermittent failures into inspectable runs
When a critical journey fails only in CI, Browserherd keeps the browser evidence your team needs to investigate it.
Replay the complete journey
See the browser state leading up to the failed assertion.
Correlate technical events
Review console errors and network activity alongside the recording.
Search the test history
Compare repeated runs by suite, session ID, status, region, or duration.
CI-friendly connection
Point Playwright at Browserherd
Use an environment variable for your project API key and create one isolated session per test worker or suite.
PLAYWRIGHT · TEST SETUP
import { chromium } from "playwright-core";
const params = new URLSearchParams({
token: process.env.BROWSERHERD_API_KEY,
sessionName: `checkout-${process.env.CI_JOB_ID}`,
sessionRecording: "true",
sessionTTL: "900"
});
const browser = await chromium.connectOverCDP(
`wss://connect.browserherd.com?${params}`
);
await runCheckoutSuite(browser);
await browser.close(); Designed for parallel Chromium test workers
Your tests. Our clean browsers.
Run critical journeys with better failure context
Start with your existing test framework, connect to Browserherd, and scale isolated Chromium sessions with your suite.