BrowserGap is an open-source, clientless remote browser isolation solution for automation, security, privacy, and CBII. A remotely running browser streams page pixels to an interface on the user's device, rather than executing the page's HTML, CSS, and JavaScript there. Documented browser functions include tabs, forms, file transfers, modal dialogs, incognito tabs, and clearing session data. Developers can embed a BrowserView in another web application, connect Puppeteer, or use the VF.openSecurely(url) API method. The tool can make browser automation visible so a person can intervene if a job needs input. Adaptive image resampling responds to available bandwidth to help maintain responsiveness and image quality. Secure document viewing with content disarm and reconstruction is supported, but the source-available edition requires users to set up the viewer. BrowserGap can be self-hosted from source or run in Docker. Binary instructions require Google Chrome on Windows, Mac, or Linux. The source-available community edition is free under stated in-house deployment conditions; a managed session is listed at 3.81 USD per once.
Who it is for
BrowserGap may suit developers and organizations that need remote browsing for automation, security, privacy, or CBII. Its automation visibility can support workflows where a person may need to step in.
What is good
- Page content is streamed as pixels to the client
- Supports tabs, forms, and file transfers
- Can expose automation for human intervention
- Can be self-hosted or run in Docker
What to know first
- Binary instructions require Google Chrome
- Source-available edition requires viewer setup for secure documents
- Text selection and page zoom are unimplemented or buggy
- Docker use has no sound
Freedom251 review
BrowserGap: the full review
BrowserGap separates page execution from the user's device by streaming pixels from a remote browser. Consider its listed implementation gaps and document-viewer setup requirement when evaluating whether it fits a deployment.
BrowserGap is a remote browser isolation project for developers and organizations that want interactive remote browsing alongside browser automation. It is most compelling when teams can manage deployment and accept some interface gaps; its pixel-streaming model keeps page code off the user’s device, but it is not a turnkey, fully featured browser service.
Overview
BrowserGap runs pages in a remote browser and streams their rendered pixels to a browser interface on the user’s device. Because the page’s HTML, CSS, and JavaScript stay remote rather than executing locally, the approach suits deployments that want to separate page execution from client devices. The project supports self-hosting from source or a Docker image, with a hybrid deployment model.
Its more distinctive use is connecting isolation with automation. A person can watch an automation job and step in when it needs input, making BrowserGap relevant to assisted workflows as well as remote browsing. That combination is useful for teams building browser-based processes, but the setup and known browser-function gaps count against it as a general-purpose managed service.
Key features
Interactive remote sessions
Documented browser functions include tabs, form entry, file uploads and downloads, modal dialogs, incognito tabs, touch or pointer scrolling, and clearing session data, cache, history, and cookies. These cover many routine interactions and give users meaningful control of a remote session. Text selection, page zoom, multi-touch, WebGL, and fluid use of multiple windows are unimplemented or buggy, however, so workflows depending on those capabilities may be frustrating or unsuitable.
Automation and integration
BrowserGap can expose browser automation to a human who needs to intervene, and its README documents connecting Puppeteer to the browser service. Developers can also embed a BrowserView in another web application to connect user flows across sites, or use the API method VF.openSecurely(url). These options make it a better fit for teams building custom browser workflows than for buyers seeking a ready-made end-user product.
Bandwidth and documents
Adaptive image resampling adjusts image delivery to available bandwidth, aiming to preserve responsiveness without sacrificing image quality unnecessarily. Secure document viewing with content disarm and reconstruction is supported, but the source-available edition requires users to set up the document viewer themselves. That extra work matters for organizations that need document protection but do not want to assemble deployment components.
Pricing
BrowserGap is freemium, with a free plan and paid options.
- Source-available community edition — 0.00 USD per free. Licensed 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 natural fit for eligible organizations able to operate the software themselves; the document viewer still needs to be set up by the user.
- Managed session — 3.81 USD per once. This covers a session, making it suited to a one-off need rather than an ongoing deployment. No session duration or other usage limit is stated.
- Pro / license exemption — custom pricing. Flexible licensing, maintenance, deployment, delivery, and custom development options are available by contacting the maker. This is the relevant route for organizations needing commercial terms or help beyond the community edition.
Commercial licensing is available by contacting the maker. The repository describes free use for governments and non-profits subject to in-house deployment conditions.
Platforms
BrowserGap supports API, Linux, macOS, self-hosted, web, and Windows. Binary instructions require Windows, Mac OS, or Linux and Google Chrome to be installed, so the operating system list does not remove the Chrome prerequisite. Docker is also an option, though the README notes that Docker use has no sound.
Who it's for
BrowserGap is best suited to developers and organizations that want to combine remote browsing with automation visibility, human intervention, or embedded cross-site flows. It is also worth considering where keeping page execution off the client device is a priority and the team can self-host or arrange a deployment.
It is a weaker choice for people who need polished document viewing without extra setup, depend on WebGL or fluid multi-window work, or want a conventional fully managed security suite. Its controls cover common tasks, but the unimplemented and buggy functions narrow the workflows it can serve comfortably.
Pros and cons
- Pro: Remote pixel streaming keeps page HTML, CSS, and JavaScript from executing on the user’s device, supporting a clear separation between page execution and the client.
- Pro: Puppeteer integration, BrowserView embedding, and human intervention in automation jobs make it useful for custom assisted workflows.
- Pro: The source-available community edition is free, with use without purchase for specified public-interest groups under in-house deployment conditions.
- Con: Text selection, zoom, multi-touch, WebGL, and fluid multiple-window support are unimplemented or buggy, limiting compatibility with some browsing tasks.
- Con: Secure document viewing requires users of the source-available edition to set up the viewer themselves.
- Con: The documented binary setup requires Google Chrome, and Docker runs without sound, which may constrain deployment choices.
Alternatives
Browser Isolation Software is a broader category page for comparing tools in this area.
- Netzilo Enterprise Browser is a better fit to consider when a free plan covering up to five users and 100 devices, or a free trial, matters.
- Kasm Workspaces is worth comparing for a self-hosted option with a Community plan allowing five concurrent sessions, though that plan does not permit commercial use.
- Menlo Security Secure Cloud Browser is an alternative for organizations considering a paid cloud browser offering with custom-quote pricing.
- DefensX Remote Browser Isolation is an alternative to consider for a paid remote browser isolation product with a free trial.
- Zscaler Private Access is a paid alternative for organizations evaluating private-access products.
- Check Point Harmony SASE is a paid option with a 30-day trial before a software license is required.
- Cisco Secure Access is a paid alternative with tiered pricing based on covered-user count and subscription term.
- Citrix Remote Browser Isolation is another paid remote browser isolation option for Windows, macOS, and Linux.
Verdict
Choose BrowserGap if you need remote page execution combined with automation visibility or custom browser workflows, and your team can handle deployment and the viewer setup. Its pixel-streaming model and integration options give it a focused role; look elsewhere if your work depends on the browser functions it lacks or you need a turnkey, fully featured service.
BrowserGap plans and pricing
All plansCompared on browser isolation software
- Free plan
- Yes
- Isolation mode
- remote
- Deployment model
- hybrid




