BrowserBox

What BrowserBox is

BrowserBox streams a full modern browser to clients for remote browser isolation, browsing, automation, and embedding. Access works from modern browsers without plugins, with streaming described at 60 FPS. Sessions run in controlled, disposable environments, and policies can allow or deny copying, pasting, uploads, downloads, printing, and developer tools. Secure defaults include navigation allowlisting, blocked private-network access, and browser-profile encryption at rest. Policy decisions are logged with sensitive fields redacted. The hyper-frame element embeds a live browser session, while JavaScript can drive tabs, navigation, capture, and selection. BrowserBox integrates with Puppeteer and Playwright, and its Cloud API creates ephemeral REST sessions without customer hosting. It runs headless on servers with or without a GPU and can pair with Tor, SSH tunnels, or HTTPS. On Linux, bbx fleet supports multiple isolated seats per host; elsewhere the site describes one session per machine. BrowserBox is commercial, not open source, and requires a license for development and evaluation. Commercial licensing starts at $119 a year.

Who it suits

It suits enterprises, developers, privacy-conscious users, and regulated government, healthcare, or finance organizations needing remote browser isolation. Automation, embedding, and policy controls support secure browser-based workflows.

Limits

Both evaluation licenses last 7 days and allow 1–10 concurrent sessions. The work-email option costs $20, paid once and requires a work email; the free-or-anonymous-email option costs $40, paid once. Both require ID verification via Stripe, are billed per seat, and have fees credited toward a full license; all sales are final.

Getting started

1. Choose a license: evaluation, non-commercial, or commercial.
2. For an evaluation license, select the work-email or free-or-anonymous-email option; both run for 7 days.
3. Use the Cloud API to create ephemeral sessions over REST without hosting them, or deploy BrowserBox on a server.
4. For server deployment, choose headless operation with or without a GPU and optionally pair it with Tor, SSH tunnels, or HTTPS.
5. Use the hyper-frame element to embed a live session, or integrate automation with Puppeteer or Playwright.

Verdict

BrowserBox combines streamed browser sessions with isolation policies, embedding, automation integrations, and cloud or self-hosted deployment. Its commercial licensing requirement and seat limits should be checked before adoption.