Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

BrowserGap

github.com

  • Free plan
  • Windows
  • macOS
  • Linux
  • Web
  • API
  • Self-hosted
8.3 Club score Visit github.com

What BrowserGap is

BrowserGap is a remote browser isolation solution for automation, security, privacy, and CBII. It runs a browser remotely and sends its rendered page as pixels to an interface on the user’s device, rather than running the page’s HTML, CSS, and JavaScript there. Users can work with tabs, forms, file transfers, modal dialogs, incognito tabs, and session data controls. Developers can embed a BrowserView in another web application, connect Puppeteer, or use the VF.openSecurely(url) API method. BrowserGap can also expose an automation session so a person can step in when a job needs input. Adaptive image resampling is intended to support responsiveness as bandwidth changes. Secure document viewing with content disarm and reconstruction is supported, but the source-available edition requires users to configure the viewer. It can be self-hosted from source or run using Docker, which the README notes has no sound. Binary instructions require Google Chrome on Windows, Mac OS, or Linux. The source-available community edition is free under stated in-house deployment conditions; a managed session is $3.81, paid once.

Who it suits

BrowserGap suits developers and organizations seeking remote browser sessions for automation, security, or privacy, including those that want to embed a browser flow or allow human intervention. Users should account for its deployment prerequisites and listed browser limitations.

Good to know, and what to watch

  • Remote rendering keeps page code off the client device.
  • Supports tabs, forms, and file transfers.
  • Puppeteer connection and VF.openSecurely(url) API method are documented.
  • Adaptive image resampling responds to available bandwidth.
  • Text selection and page zoom are unimplemented or buggy.
  • Multi-touch, WebGL, and multiple-window support have limitations.
  • Binary use requires Google Chrome installed.
  • Source-available document viewing requires users to set up the viewer.

Pro / license exemption

—

Source-available community edition

Free

Managed session

$3.81 one-time

Free plan · pricing on request

Getting started

  1. Open the BrowserGap project website
  2. Choose a self-hosted source deployment or a Docker image
  3. Install Google Chrome on Windows, Mac, or Linux for binary use
  4. Connect an application with BrowserView, Puppeteer, or VF.openSecurely(url)
  5. Configure the document viewer yourself when using the source-available edition

Limits to check

The source-available community edition is free under stated in-house deployment conditions for governments, researchers, journalists, and nonprofits. Several browser functions remain unimplemented or buggy, and Docker use has no sound.

The Club's review

BrowserGap is an open-source remote browser isolation tool that streams remote sessions to a browser on the user’s device. It is best suited to developers and organizations building browser automation or self-hosted workflows. Its remote rendering and human-intervention features are compelling, but interface gaps and deployment requirements narrow its fit.

Overview

BrowserGap renders web pages in a remote browser and sends pixels to the user’s device; the page’s HTML, CSS, and JavaScript do not run on that device. That separation is relevant when keeping page execution away from the client matters. BrowserGap can run from source or a Docker image, though Docker use has no sound.

Beyond remote browsing, BrowserGap can expose automation activity so a person can step in when a job needs input. This makes it more useful as a building block for assisted browser workflows than as a turnkey security service.

Key features

Remote browsing and controls

Supported controls include tabs, form input, file uploads and downloads, modal dialogs, incognito tabs, touch or pointer scrolling, and clearing session data, cache, history, and cookies. Adaptive image resampling adjusts to available bandwidth to help balance image quality and responsiveness. These controls cover routine interactions, but text selection, page zoom, multi-touch, WebGL, and fluid use of multiple windows are unimplemented or buggy. Those gaps matter for users whose work depends on precise page interaction or richer graphics.

Automation and embedding

BrowserGap documents a Puppeteer connection to its browser service and the VF.openSecurely(url) API method. Developers can also embed a BrowserView in another web application to connect user flows across sites. These options make the project a plausible fit for custom automation interfaces; they are less attractive to teams that want a ready-made workflow product.

Document handling and licensing

Secure document viewing with content disarm and reconstruction is supported, but the source-available edition requires users to set up the document viewer themselves. The project is dual-licensed under AGPL-3.0 and a custom exemption, with commercial licensing available by contacting the maker. Governments and non-profits may use it without purchase under stated in-house deployment conditions.

Pricing

The Source-available community edition costs nothing under AGPL-3.0 and a custom exemption. Governments, researchers, journalists, and nonprofits may use it without purchase under stated in-house deployment conditions. This is the clearest fit for technically capable users who can host and maintain their own deployment; the license terms and setup are important considerations for commercial use.

The Managed session costs $3.81, paid once for a session. Pro / license exemption has custom pricing, with flexible licensing, maintenance, deployment, delivery, and custom development options available by contacting the maker.

Platforms

BrowserGap supports API, Linux, macOS, self-hosted, web, and Windows. Binary instructions require Windows, Mac OS, or Linux and an installed copy of Google Chrome. The Chrome prerequisite and self-hosting options favor teams able to manage their own environment over users seeking a browser-only setup.

Who it's for

BrowserGap is a strong candidate for developers who want remote page rendering, browser controls, and a way for people to intervene in automation. It also suits organizations that can handle deployment and licensing choices, particularly those covered by the stated in-house free-use conditions. It is a weaker fit for users who need complete browser interaction, built-in document-viewer setup, or a managed security suite without operational work.

Pros and cons

  • Pros: Remote rendering keeps page HTML, CSS, and JavaScript off the client device, which supports isolation-oriented workflows.
  • Pros: Puppeteer integration, BrowserView embedding, and human intervention make it adaptable to custom automation flows.
  • Pros: A free community edition and self-hosting provide a route for capable teams to run their own deployment.
  • Cons: Text selection, zoom, multi-touch, WebGL, and fluid multiple-window support are incomplete or buggy, limiting some browsing tasks.
  • Cons: Binary use requires Google Chrome, and Docker use has no sound; neither is ideal for every deployment.
  • Cons: The source-available edition leaves document-viewer setup to the user, and commercial licensing may require contacting the maker.

Alternatives

Browser Isolation Software is a broader category to explore when comparing isolation products. Consider Netzilo Enterprise Browser for a freemium option with a free plan, free trial, and support for mobile platforms and browser extensions; its free plan allows up to 5 users and 100 devices with community support only. Check Point Harmony SASE is a paid option with a free trial and a license required after the 30-day trial.

DefensX Remote Browser Isolation is worth considering for its Core and Premium plans, which distinguish 30-day and 90-day log retention. Kasm Workspaces offers a free Community plan with 5 concurrent sessions and no commercial use, making it relevant to non-commercial self-hosted use. Netskope One Private Access, Cisco Secure Access, Keeper Remote Browser Isolation, and Menlo Security Secure Cloud Browser are other options to compare.

Verdict

Choose BrowserGap if you need remote page rendering tied to browser automation and can take responsibility for deployment, Chrome prerequisites, and licensing. Its most distinctive advantage is letting a person see and intervene in automation while page code stays off the client. Look elsewhere if incomplete browser controls or the need to configure document viewing would disrupt your work, or if you want a fully managed security product.

The verdict

BrowserGap combines remote page rendering with browser controls and automation visibility. Its listed limitations and Chrome prerequisite matter when assessing fit; the managed session is listed at $3.81, paid once.

Questions people ask

Is BrowserGap free?

The source-available community edition is listed as free under stated in-house deployment conditions. A managed session is listed at $3.81, paid once.

Which operating systems are supported?

Binary prerequisites cover Windows, Mac OS, and Linux, with Google Chrome installed. The platform listing also includes API, self-hosted, and web use.

Can BrowserGap connect to Puppeteer?

Yes. The documented integrations include connecting Puppeteer to the browser service and using the VF.openSecurely(url) API method.

Is BrowserGap open source?

The project is described as dual-licensed under AGPL-3.0 and a custom exemption. Commercial licensing is available by contacting the maker.

Can I deploy BrowserGap myself?

Yes. It can be self-hosted from source or run from a Docker image.

What the maker publishes

Automation
BrowserGap can provide visibility into browser automation and allow a human to intervene when an automation job needs input. source
Automation
The project can provide visibility into Puppeteer, Playwright, or DevTools Protocol browser automation and allow human intervention in jobs. source
Bandwidth
The project describes adaptive image resampling based on available bandwidth to help maintain responsiveness and image quality. source
Browser controls
Supported browser functions include tabs, form input, file upload and download, modal dialogs, and clearing cache, history, and session cookies. source
Browser functions
Documented working functions include tabs, file upload and download, incognito tabs, session data clearing, form input, and touch or pointer scrolling. source
Deployment
The project can be self-hosted from source or run from a Docker image; the README notes Docker use has no sound. source
Document security
Secure document viewing with content disarm and reconstruction is supported, but the source-available edition requires users to set up the document viewer themselves. source
Document security
Secure document viewing with content disarm and reconstruction is supported, but the source-available edition requires users to set up the separate viewer themselves. source
Embedding
Developers can embed a BrowserView in another web application to connect user flows across sites. source
Embedding
Developers can embed a BrowserView in another web application to integrate user flows. source
Free use
The repository says use is free for governments and non-profits, subject to stated in-house deployment conditions. source
Integrations
The README documents connecting Puppeteer to the browser service and an API method called VF.openSecurely(url). source
Integrations
The README documents Puppeteer and Playwright use, a DevTools connection at localhost:5002, and a JavaScript SDK with VF.openSecurely(url). source
Known limitations
The README lists text selection, page zoom, multi-touch, WebGL, and fluid multiple-window support as unimplemented or buggy. source
Known limitations
The README lists text selection, WebGL, multiple windows, and several zoom and mobile touch functions as unimplemented or buggy. source
License
The repository describes the project as dual-licensed under AGPL-3.0 and a custom exemption, with commercial licensing available by contacting the maker. source
License
The README describes the source-available project as dual licensed under AGPL-3.0 and a custom exemption, with a paid exemption available for other licensing needs. source
Maker and contact
The README identifies Cris Stringfellow as the maker and gives [email protected] for business inquiries. source
Pixel streaming
The project says it sends pixels from the remote page to the device, so the page's HTML, CSS, and JavaScript are not executed there. source
Platform prerequisites
The binary instructions list Windows, Mac OS, or Linux and require Google Chrome to be installed. source
Purpose
BrowserGap is an open-source, clientless remote browser isolation solution for automation, security, privacy, and CBII. source
Purpose
BrowserGap is described as a clientless remote browser isolation product for security, automation, and privacy. source
Remote browsing
It streams a remotely running browser interactively to a browser interface on the user's device. source
Remote rendering
The README says the remote page is rendered by sending pixels to the client, so its HTML, CSS, and JavaScript are not executed on the client device. source

Checked against the maker's pages on 4 Oct 2026.