Secure, modern Remote Browser Isolation (RBI) with a clientless experience
STATUS UPDATE: The new BrowserBox version has landed. We were up and installable from December 2018 until a brief outage last month while we migrated to a binary release system. Sorry for the downtime and thanks for the patience. We are back up now with a soft-launch beta - expect rapid iteration and please report issues.
Stability & Authority: Shipping RBI since 2018, now on signed binary releases with a tighter CI loop. We are small by design but serious about reliability and fast support.
BrowserBox™ is a remote browser isolation (RBI) platform for security teams, SaaS builders, and IT ops. It streams a full modern browser to any client with low latency and 60 FPS, supports embedding, and runs on Windows, Linux, and containers. **A product key is required for all BrowserBox usage.**
At a glance:
* **Clientless RBI:** No plugins or downloads for end users.
* **60 FPS streaming:** Smooth, responsive browsing over the network.
* **Embed anywhere:** Drop in the BrowserBox webview to your app or portal.
* **Flexible deployment:** Works on Windows, Linux, Docker, and LXC.
* **Built for control:** Policies, isolation, and audit-friendly workflows.
Quick links: [Get Started](#get-started-in-3-steps) | [Pricing](https://dosaygo.com/commerce) | [Support](mailto:support@dosaygo.com)
Official sites: [BrowserBox](https://browserbox.io), [DOSAYGO](https://dosaygo.com), and [CloudTabs](https://browse.cloudtabs.net)
bbx CLI help (expand)
```ansi
███████████ ███████████
░░███░░░░░███ ░░███░░░░░███
░███ ░███ ████████ ██████ █████ ███ █████ █████ ██████ ████████ ░███ ░███ ██████ █████ █████
░██████████ ░░███░░███ ███░░███░░███ ░███░░███ ███░░ ███░░███░░███░░███ ░██████████ ███░░███░░███ ░░███
░███░░░░░███ ░███ ░░░ ░███ ░███ ░███ ░███ ░███ ░░█████ ░███████ ░███ ░░░ ░███░░░░░███░███ ░███ ░░░█████░
░███ ░███ ░███ ░███ ░███ ░░███████████ ░░░░███░███░░░ ░███ ░███ ░███░███ ░███ ███░░░███
███████████ █████ ░░██████ ░░████░████ ██████ ░░██████ █████ ███████████ ░░██████ █████ █████
░░░░░░░░░░░ ░░░░░ ░░░░░░ ░░░░ ░░░░ ░░░░░░ ░░░░░░ ░░░░░ ░░░░░░░░░░░ ░░░░░░ ░░░░░ ░░░░░
Welcome to the bbx CLI tool for BrowserBox!
Usage:
bbx [options]
Commands:
install Install BrowserBox + bbx CLI
uninstall Remove everything
activate Purchase a license bbx activate [number of people]
setup Configure options bbx setup [--port|-p
] [--hostname|-h ] [--token|-t ] [--zeta|-z]
setup options:
--zeta, -z Expose each service as a unique hostname. Useful for nginx,
ngrok, similar layers, or standard HTTP/S ports. Expects hosts.env
certify Check your license
run Run BrowserBox bbx run [--port|-p ] [--hostname|-h ]
stop Stop BrowserBox (current user)
run-as Run as a specific user bbx run-as [--temporary] [username] [port]
stop-user Stop BrowserBox for a specific user bbx stop-user [delay_seconds]
logs Show BrowserBox logs
update Update BrowserBox bbx update [|--latest-rc]
status Check BrowserBox status
tor-run Run BrowserBox on Tor bbx tor-run [--no-darkweb] [--no-onion]
zt-run Run BrowserBox with ZeroTier tunnel bbx zt-run
docker-run Run BrowserBox using Docker bbx docker-run [nickname] [--port|-p ]
docker-stop Stop a Dockerized BrowserBox bbx docker-stop
automate *Drive with script, MCP or REPL
ng-run Run BrowserBox with Nginx proxy bbx ng-run
--version Show version
--help Show this help
*automate coming soon
```
---
## Table of Contents
1. [Commercial Licensing & Legal (Not Open Source)](#commercial-licensing--legal-not-open-source)
2. [Get Started in 3 Steps](#get-started-in-3-steps)
* [1. Install the `bbx` CLI](#1-install-the-bbx-cli)
* [2. Purchase & Obtain Your Product Key](#2-purchase--obtain-your-product-key)
* [3. Activate & Run BrowserBox](#3-activate--run-browserbox)
3. [Why Choose BrowserBox?](#why-choose-browserbox)
4. [Key Benefits](#key-benefits)
5. [Who Needs BrowserBox?](#who-needs-browserbox)
6. [Core Features](#core-features)
7. [What's New In The Latest Release](#whats-new-in-the-latest-release)
8. [See It In Action](#see-it-in-action)
9. [Supported Network Topologies](#supported-network-topologies)
10. [Platform Compatibility](#platform-compatibility)
11. [Meet `bbx`: Your BrowserBox Command Center](#meet-bbx-your-browserbox-command-center)
12. [Embed BrowserBox Anywhere](#embed-browserbox-anywhere)
13. [Advanced Usage](#advanced-usage)
14. [License Compliance & Usage Data](#license-compliance--usage-data)
15. [Frequently Asked Questions (FAQ)](#frequently-asked-questions-faq)
16. [Support](#support)
17. [About DOSAYGO](#about-dosaygo)
18. [Copyright & Licensing](#copyright--licensing)
---
## Commercial Licensing & Legal (Not Open Source)
BrowserBox is a commercial product. All usage requires a valid license, including development and evaluation. If you want to contribute, you must first obtain a development license per `CONTRIBUTING.TXT`.
We are a small team and we protect our IP because it funds the work, the infrastructure, and the support that keep BrowserBox reliable. Please review our [Terms of Service](https://dosaygo.com/terms.txt.html) and [Privacy Policy](https://dosaygo.com/privacy.txt.html).
## Get Started in 3 Steps
### 1. Install the `bbx` CLI
The `bbx` command-line interface is your primary tool for managing BrowserBox.
* **Windows:**
```powershell
irm https://browserbox.io/install.ps1 | iex
```
* **Linux (Debian, Ubuntu, CentOS, RHEL, NixOS) & macOS & Docker:**
```bash
bash <(curl -sSL https://browserbox.io/install.sh) install
```
* **Via NPM (@browserbox/browserbox):**
```bash
npm i -g @browserbox/browserbox
bbx-install
```
>[!NOTE]
>Installers now use `browserbox.io` endpoints. If you see older docs pointing to `dosaygo.com`, use the commands above.
### 2. Purchase & Obtain Your Product Key
A product key is required.
* **Commercial Use:** Starts at $99/user/year. [Purchase Commercial License](https://dosaygo.com/commerce).
* **Non-Commercial Use:** $39/user/year (for non-profits, government). [Purchase Non-Commercial License](https://dosaygo.com/noncommercial).
* **Evaluation:** [Apply for a 7-Day Trial](https://browserbox.io).
* **Demo:** [Request a Demo](mailto:sales@dosaygo.com?subject=Demo).
* **Regulated Industries:** [Explore compliance-oriented options](https://dosaygo.com/regulated-enterprise.html).
You can also purchase directly via the `bbx` CLI on Linux/macOS:
```console
bbx activate [number of people]
```
>[!CAUTION]
>Unlicensed instances will display a warning and shut down after a brief period. Ensure you have a valid product key for uninterrupted use.
>[!IMPORTANT]
>After purchase, you'll receive an email with a secure link to view your **Product Key**. Save it safely; the link is single-use. Lost keys can be re-issued by contacting [Support](mailto:support@dosaygo.com).
### 3. Activate & Run BrowserBox
* **Windows:** Set the `LICENSE_KEY` environment variable:
```powershell
$Env:LICENSE_KEY = "YOUR_BROWSERBOX_PRODUCT_KEY"
```
* **Linux/macOS:** Use `bbx certify` to enter and save your Product Key (if not already saved via `bbx activate`).
```console
bbx certify YOUR_BROWSERBOX_PRODUCT_KEY
```
Then, start BrowserBox:
```console
bbx setup # Run once for initial configuration
bbx run
```
Access BrowserBox using the **Login Link** provided in your console. For public internet access, ensure your DNS records are configured correctly. View logs with `bbx logs` and stop with `bbx stop`.
## Why Choose BrowserBox?
In today's threat landscape, standard browsing carries real risk. BrowserBox provides an isolated environment that reduces exposure to web-based threats *before* they reach your network or endpoints. It's a practical tool for:
* **Protecting Sensitive Data:** Support secure workflows in regulated environments.
* **Secure Automation:** Run web automation inside isolation boundaries.
* **Compliance & DLP:** Apply policy-driven controls to reduce data leakage.
* **Developer Productivity:** Easily embed secure browsing into applications.
## Key Benefits
* **Stronger Isolation:** Reduce malware risk and limit exposure to web-based threats.
* **Effortless Integration:** Clientless RBI works in any browser. Embed secure browsing into your apps or protect local tabs with minimal friction.
* **Cross-Platform Coverage:** Runs on Windows, Linux (Debian, Ubuntu, RHEL, CentOS, NixOS), Docker, and LXC.
* **Smooth UX:** Low-latency rendering with a focus on responsiveness and 60 FPS streaming.
* **Developer Friendly:** Powerful `bbx` CLI and a straightforward Embedding API.
## Who Needs BrowserBox?
* **Security Teams:** Reduce risk from untrusted browsing while keeping access simple.
* **SaaS Builders & Integrators:** Embed isolated browsing directly into your product or workflow.
* **IT & Ops:** Deploy a manageable, remote browser on mixed fleets and servers.
* **Automation & QA:** Run scripts against real sites inside an isolated environment.
* **Regulated Orgs:** Support policy-driven browsing with configurable controls.
## Core Features
* **Clientless Remote Browser Isolation (RBI):** No downloads or plugins needed for end-users. Access from any modern web browser.
* **Comprehensive Platform Support:** Windows, major Linux distributions, Docker, LXC.
* **Powerful `bbx` CLI Tool:** Manage installations, licenses, users, and run modes (including Tor).
* **Easy Embedding API:** Integrate BrowserBox into your web applications with a simple `` custom element.
* **Automation Ready:** Designed for use with Puppeteer (PPtr) and Playwright (support coming soon).
* **Security Focused:** Built-in DLP features, Tor support for anonymity, and robust access controls.
* **1-Click Cloud Deployment (Coming Soon):** Easily deploy on Vultr, AWS, Azure, or Linode.
## What's New In The Latest Release
* **Binary release system:** Faster installs and more reliable updates.
* **60 FPS streaming:** Smooth, responsive remote browsing.
* **Unified install endpoints:** `browserbox.io` installers for Linux/macOS and Windows.
## See It In Action
BrowserBox provides a full-featured, secure browsing experience:
Secure Web BrowsingSeamless PDF ViewingPowerful DevToolsFull Browser Features (File Uploads, etc.)
# Supported Network Topologies
🌐 **Unlock Any Network Scenario with BrowserBox** – Whether you're a SD-WAN architect optimizing enterprise connectivity, a NAT traversal expert punching through firewalls, a WiFi specialist ensuring seamless access on the go, or a NOC pro managing mission-critical operations, BrowserBox delivers unmatched flexibility. From massive country-scale deployments to secure homelab setups, our platform adapts to virtually every operating system, client device, and networking topology you'll encounter. Run it headless on servers without a graphical display or GPU for efficient, low-footprint ops—or leverage full GPU acceleration and manual graphical displays when you need visual power. BrowserBox isn't just software; it's an all-in-one toolkit for secure, scalable remote browser access that fits *your* environment, not the other way around. From mesh to edge, from overlay to backbone — BrowserBox works with it all. 🚀
### Comprehensive Topology Compatibility at a Glance
Here's the core of what makes BrowserBox a networking powerhouse—a detailed table of our supported topologies. We've got you covered from simple HTTP setups to advanced overlay networks, with zero-compromise reliability across platforms. (And stay tuned: Native support via the `bbx` CLI is coming soon for NGINX, Cloudflare Tunnels, and ZeroTier on all platforms, plus automated SSH port forwarding with built-in certificate management and orchestration. Get ready for even smoother integrations! 🎉)
| Topology | Description | Public Access? | Key Features & Benefits | OS Support (Ubuntu/macOS/Windows) | Best For |
|----------|-------------|----------------|--------------------------|------------------------------------|----------|
| **HTTP Only** | Basic unencrypted HTTP connections for quick, lightweight access. | Yes (if exposed) | Simple setup; ideal for internal testing or low-security demos. Supports custom ports (e.g., 8080, 9999, 11111) or standard (80). | ✅ / ✅ / ✅ | Rapid prototyping in trusted networks. |
| **HTTP/WS** | HTTP with WebSocket support for real-time bidirectional communication. | Yes (if exposed) | Enables interactive apps; pairs with custom/standard ports for flexibility. | ✅ / ✅ / ✅ | Chat apps, live updates, or collaborative tools. |
| **HTTPS/WSS/WebRTC** | Secure HTTPS with WebSocket Secure and WebRTC for encrypted, peer-to-peer media streaming. | Yes (if exposed) | End-to-end encryption; auto-cert handling; custom/standard ports (443 default). | ✅ / ✅ / ✅ | Video calls, secure file sharing, or real-time collaboration in production. |
| **Tor/HTTP** | Tor onion service over HTTP for pseudonymous access. | Yes (via .onion) | High privacy; bypasses censorship; slow but reliable. Requires Tor Browser. | ✅ / ✅ / ✅ | Privacy-focused demos or restricted environments. |
| **Tor/HTTPS** | Secure Tor onion service with HTTPS encryption. | Yes (via .onion) | Adds TLS to Tor for extra security; reliable NAT traversal. | ✅ / ✅ / ✅ | Anonymous secure access in high-threat scenarios. |
| **SSH Port Forward, HTTP** | SSH-based port forwarding tunneling HTTP traffic. | No (private) | Secure, low-latency; forwards to custom/standard ports. Upcoming auto-cert orchestration. | ✅ / ✅ / ✅ | Private homelab access or secure internal routing. |
| **SSH Port Forward, HTTPS** | SSH forwarding with HTTPS for encrypted tunnels. | No (private) | Combines SSH reliability with TLS; flexible port options. Native enhancements incoming. | ✅ / ✅ / ✅ | Enterprise-grade secure remote sessions. |
| **Custom Ports** | User-defined ports (e.g., 8080, 9999, 11111) across any protocol. | Varies | Total control; avoids conflicts; integrates with all topologies. | ✅ / ✅ / ✅ | Tailored setups for specialized apps or multi-service hosts. |
| **Standard Ports** | Default ports (e.g., 80 for HTTP, 443 for HTTPS) for seamless compatibility. | Varies | Plug-and-play; reduces config overhead in standard environments. | ✅ / ✅ / ✅ | Quick deployments matching common infrastructure. |
| **Cloudflare Tunnel** | HTTPS DNS facade with port relay via Cloudflare's edge network. | Yes (*.trycloudflare.com) | Auto-install; high reliability; great perf. Native `bbx cf-run` support soon. | ✅ / ✅ / ✅ | Quick public demos with origin privacy. |
| **localhost.run** | SSH reverse tunnel with HTTPS facade. | Yes (http(s)://…lhr.life) | Zero-config; medium reliability; occasional interstitials. | ✅ / ✅ / ✅ | Free, easy links for casual sharing. |
| **ngrok** | Port relay with HTTPS and auth token for secure exposure. | Yes (*.ngrok-free.app) | High perf; webhooks ready; free tier limits (1 tunnel). Token required. | ✅ / ✅ / ✅ | Shareable demos and webhook testing. |
| **Pinggy** | Port relay with HTTPS; may have interstitials. | Yes (*.pinggy.io) | Fair reliability; okay perf. | ✅ / ✅ / ℹ️ (Limited on Windows) | Budget-friendly webhooks and demos. |
| **Tailscale** | Overlay network for private, LAN-like access. | No (private tailnet) | Very high reliability; low latency. SSH forwarding; token required. Less stable on Windows/VPN. | ✅ / ✅ / ℹ️ (SSH not upstream-supported on Windows) | Private team debugging and access. |
| **Tor** | Onion routing for pseudonymous, reliable access. | Yes (.onion) | Extremely reliable (but slow); privacy-first. We already have `bbx tor-run`. | ✅ / ✅ / ✅ | Censorship-resistant, anonymous deployments. |
| **Tunnelmole** | OSS ngrok-style relay with HTTPS. | Yes (https://…tunnelmole.net/.com) | High reliability; good perf; auto-install. | ✅ / ✅ / ✅ | Open-source demos with easy URLs. |
| **ZeroTier** | Overlay network for peer-to-peer private access. | No (private network) | LAN-like; very high reliability. Native `bbx zt-run` support soon. Tokens required; client on access device. | ✅ / ✅ / ✅ | Secure P2P demos in overlays. |
**Notes on Flexibility & Power:**
- **Headless or Graphical? Your Call.** BrowserBox thrives on headless machines—no display or GPU needed for core ops—making it perfect for servers or cloud instances. But when you want it, tap into GPU acceleration for heavy rendering or enable manual graphical displays for hands-on control. Scale from a single homelab box to nationwide rollouts without missing a beat. 💪
- **Why BrowserBox Wins Networks:** In a world of rigid tools, BrowserBox stands out by embracing *every* topology. Punch through NAT with ease, integrate with SD-WAN for optimized routing, ensure WiFi stability for mobile pros, and give NOC teams the configurability to monitor and manage at scale. It's not just supported—it's battle-tested for real-world wins. Ready to deploy? Fork, configure, and conquer! 🌍
## Platform Compatibility
BrowserBox runs seamlessly across a wide range of operating systems and containerization technologies:
| Platform | Supported | Icon |
| :----------------------- | :-------- | :-------------------------------------------------------------------------------------------------- |
| Tails\* | ❌ | |
| Windows & Windows Server | ✅ | |
| Debian | ✅ | |
| Ubuntu | ✅ | |
| CentOS Stream | ✅ | |
| RHEL | ✅ | |
| NixOS | ✅ | |
| Docker | ✅ | |
| LXC | ✅ | |
| Podman‡ | 🚧 | |
| Windows 9x† | ✅ | |
>[!NOTE]
>Run `bbx` (or `bbx install` on Windows) to ensure you have the latest version (v13+) with all fixes and features.
**Notes**
- \*Tails is not supported because neither Chrome nor Docker can be installed.
- ‡Podman support is currently under consideration.
- †Windows 9x clients are supported by running the **new** `win9x_bbpro` command which will output the login link for legacy Windows clients (such as Internet Explorer (IE 5, IE 6, etc) or Netscape. Supported Windows 9x operating systems for legacy clients include Windows 95, Windows 98, Windows 2000, Windows NT the BrowserBox server must still be run on a modern system, but now you can connect to BrowserBox from legacy Windows 9x machines and browsers. Modern clients can still use the legacy endpoint but the experience is understandably jurassic.
|
| Windows & Windows Server | ✅ | 
|
| Debian | ✅ | 
|
| Ubuntu | ✅ | 
|
| CentOS Stream | ✅ | 
|
| RHEL | ✅ | 
|
| NixOS | ✅ | 
|
| Docker | ✅ | 
|
| LXC | ✅ | 
|
| Podman‡ | 🚧 | 
|
| Windows 9x† | ✅ | 
|
>[!NOTE]
>Run `bbx` (or `bbx install` on Windows) to ensure you have the latest version (v13+) with all fixes and features.
**Notes**
- \*Tails is not supported because neither Chrome nor Docker can be installed.
- ‡Podman support is currently under consideration.
- †Windows 9x clients are supported by running the **new** `win9x_bbpro` command which will output the login link for legacy Windows clients (such as Internet Explorer (IE 5, IE 6, etc) or Netscape. Supported Windows 9x operating systems for legacy clients include Windows 95, Windows 98, Windows 2000, Windows NT the BrowserBox server must still be run on a modern system, but now you can connect to BrowserBox from legacy Windows 9x machines and browsers. Modern clients can still use the legacy endpoint but the experience is understandably jurassic.
The `bbx` CLI simplifies every aspect of BrowserBox management:
* ✅ **Easy Installation & Updates:** `bbx install`, `bbx update`
* 💳 **License Management:** `bbx activate [number of seats]`, `bbx certify [product key]`
* 👩💻 **Multi-User Support:** Run BrowserBox for multiple users on a single machine.
* 🐳 **Docker Integration:** `bbx docker-run`
* 🧅 **Tor Anonymity:** `bbx tor-run`
* ⚙️ **Core Operations:** `bbx run`, `bbx stop`, `bbx logs`, `bbx setup`
* 🌟 **And much more!** Run `bbx --help` for a full list of commands on your OS.
---
## Embed BrowserBox Anywhere
Easily integrate secure, remote browsing into your web applications using the BrowserBox Embedding API. Our `