Use real browsers in production
Run managed Chromium for authenticated scraping, visual checks, artifacts, and agent workflows. Validate in the playground, then ship through the API.
Three short paths
Pick the path that matches your job. You do not need to learn the whole platform first.
Start from an API key, launch a managed Chromium instance, and connect with Playwright or Puppeteer.
Test target pages, selectors, timeouts, screenshots, and crawl boundaries in the playground.
Store cookies, localStorage, proxy settings, and fingerprint config so repeat jobs do not start from a blank browser.
From debugging to rollout
Keep the integration loop short: validate, codify, then observe.
Validate the target page, login state, timeout policy, and output shape in the playground first. Move stable workflows into server-side code, write session, artifact, and error data back to your system, then use session details, logs, replay, screenshots, and API reference pages to diagnose failures after launch.
Four objects are enough
Your application works with runtime outputs. Hivebrowser handles placement, routing, state persistence, and browser operations.
A managed Chromium instance with CDP endpoints, lifecycle state, and live preview.
Durable cookies, localStorage, proxy settings, and fingerprint config for reusable browser state.
Screenshots, PDFs, or extracted content generated by a browser session and retrievable via API.
Complete REST API for sessions, profiles, artifacts, API keys, and usage.
Hivebrowser has a narrow contract: your app calls the API, connects over CDP, and reads session state plus artifacts. The platform handles runner selection, browser launch, connect routing, profile sync, and usage accounting.