BrowserGap

B
B tier on Browser Isolation SoftwareScore 7.2 · #1 of 25
Android app
Not listed
Free plan
Yes
Runs on
api, Linux, Mac, self-hosted, Web, Windows
github.com
The BrowserGap homepage

Summary

BrowserGap is an open-source, clientless remote browser isolation solution for automation, security, privacy, and CBII. It runs a browser remotely and streams the page to an interface on the user's device as pixels, so the page's HTML, CSS, and JavaScript do not run there. Browser functions include tabs, forms, file transfers, modal dialogs, incognito tabs, and clearing session data. Developers can embed a BrowserView in another web app, connect Puppeteer, or use the VF.openSecurely(url) API method. It can also expose browser automation to a human who may need to intervene. Adaptive image resampling adjusts to available bandwidth. Secure document viewing with content disarm and reconstruction is supported, but users of the source-available edition must configure the viewer themselves. The project can be self-hosted from source or run in Docker; binary use requires Google Chrome on Windows, Mac, or Linux. The 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 suits developers and organizations seeking remote browser isolation or visibility into automated browser sessions. It may also suit government, research, journalism, and nonprofit users who meet the community edition's deployment conditions.

What is good

  • Remote pages stream as pixels, not local page code.
  • Supports tabs, forms, and file transfers.
  • Can connect Puppeteer and embed in web apps.
  • Offers human intervention in browser automation.
  • Can be self-hosted or run in Docker.

What to know first

  • Binary use requires Google Chrome.
  • Document viewer setup is left to source-edition users.
  • Text selection and page zoom are unimplemented or buggy.
  • Docker use has no sound.

Everything Xiaomi review

BrowserGap: the full review

BrowserGap offers remote rendering, browser controls, and integration options for isolated browsing and automation. Its documented limitations and setup requirements matter, especially for document viewing and unsupported browser interactions.

BrowserGap is a remotely rendered browser service for developers and organizations that want isolated browsing alongside automation. Its pixel-streaming design keeps page code off the user’s device, but browser quirks and deployment work make it a poor fit for anyone who needs a turnkey, fully featured browser.

Overview

BrowserGap runs the browser remotely and streams the resulting page to a browser interface on the user’s device. Because the client receives pixels rather than the page’s HTML, CSS, and JavaScript, the page code does not execute locally. That separation suits workflows where keeping page execution away from the endpoint matters; it does not, by itself, establish a broader security guarantee.

The project can be deployed from source or as a Docker image, and its deployment model is hybrid. Docker has no sound, while the binary setup requires Google Chrome on Windows, Mac OS, or Linux. BrowserGap is therefore most attractive to teams prepared to manage the environment rather than those seeking a ready-made managed service.

Key features

Interactive remote browsing

BrowserGap supports tabs, form entry, file uploads and downloads, modal dialogs, incognito tabs, touch or pointer scrolling, and clearing session data, cache, history, and cookies. These controls cover many ordinary browsing tasks and make remote sessions usable rather than merely viewable. However, text selection, page zoom, multi-touch, WebGL, and fluid use of multiple windows are unimplemented or buggy. Those gaps can rule it out for sites or workflows that depend on such interactions.

Automation and embedding

Automation can be made visible to a person, who can intervene when a job needs input. Developers can embed a BrowserView in another web application to connect user flows across sites. The README also documents connecting Puppeteer to the browser service and an API method, VF.openSecurely(url). This combination is a strong reason to consider BrowserGap for assisted automation, but less relevant to teams seeking only a conventional end-user browser.

Bandwidth and document viewing

Adaptive image resampling adjusts to available bandwidth to help maintain responsiveness and image quality. Secure document viewing with content disarm and reconstruction is supported, but users of the source-available edition must set up the document viewer themselves. That extra work matters for organizations whose main requirement is secure document handling.

Pricing

BrowserGap is freemium, with a free plan and paid options. The community edition costs 0.00 USD per free 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 eligible groups able to meet those conditions; the license terms matter to other users, and commercial licensing is available by contacting the maker.

The Managed session costs 3.81 USD per once for a session. No duration or other usage limits are stated, so buyers should confirm whether that one-session purchase suits their expected use. Pro / license exemption has custom pricing and offers flexible licensing, maintenance, deployment, delivery, and custom development options; it is the route for organizations needing tailored support or commercial terms. The cheaper community edition gives up those paid options and requires users to handle deployment, including their own document viewer setup.

Platforms

BrowserGap supports API, Linux, macOS, self-hosted, web, and Windows. Binary use requires Google Chrome on Windows, Mac OS, or Linux; Docker deployment is also supported, with no sound. Its remote isolation mode and hybrid deployment make it relevant to teams combining hosted and locally managed infrastructure.

Who it's for

BrowserGap is best suited to developers connecting browser automation to human oversight, and to organizations that can self-host and value keeping page execution off client devices. Eligible governments, researchers, journalists, and nonprofits may also find the no-cost community edition compelling if they meet its in-house deployment conditions.

It is a weaker choice for people who depend on text selection, zoom, WebGL, multi-touch, or smooth multi-window use, and for buyers who want document viewing without configuring a viewer. Organizations seeking a managed security suite rather than a deployable browser component should compare other approaches.

Pros and cons

  • Pros: Remote pixel rendering keeps page HTML, CSS, and JavaScript from executing on the client, which supports isolated browsing workflows.
  • Pros: BrowserView embedding, Puppeteer connectivity, and human intervention make it useful for automation that sometimes needs a person.
  • Pros: The free community edition and self-hosting provide an option for eligible organizations comfortable with in-house deployment.
  • Cons: Text selection, zoom, multi-touch, WebGL, and fluid multi-window use are unimplemented or buggy, limiting compatibility with some sites and tasks.
  • Cons: Source-available users must arrange their own document viewer, and Docker runs without sound.
  • Cons: Binary prerequisites include Google Chrome, and commercial users may need to contact the maker for licensing.

Alternatives

Browser Isolation Software is the category directory for comparing other options. Consider Netzilo Enterprise Browser if you want a freemium alternative with a free plan, free trial, and support across mobile, desktop, browser extension, and self-hosted platforms; its Free plan caps use at 5 users and 100 devices and limits support to the community.

Kasm Workspaces is worth considering if you want a freemium, self-hosted option: its Community plan allows 5 concurrent sessions but bars commercial use. For paid offerings with no free plan, Zscaler Private Access, Menlo Security Secure Cloud Browser, Check Point Harmony SASE, iboss Cloud, Netskope One Private Access, and Cisco Secure Access are alternatives to evaluate; their listed plans are priced on request or have prices not stated.

Verdict

Choose BrowserGap if you need remotely rendered browsing that can connect to automation and you have the capacity to manage deployment. Its strongest case is the combination of client-side isolation and human-visible automation. Look elsewhere if your work depends on the unsupported browser interactions, requires a ready-configured document viewer, or calls for a turnkey managed security product.

BrowserGap plans and pricing

All plans
Source-available community edition Free AGPL-3.0 and custom exemption · government, researchers, journalists, and nonprofits may use without purchase under stated in-house deployment conditions raw.githubusercontent.com · 4 Oct 2026
Managed session $3.81 once A session; duration or other limits not stated raw.githubusercontent.com · 4 Oct 2026
Pro / license exemption Not published Flexible licenses, maintenance, deployment, delivery, and custom development options; contact maker raw.githubusercontent.com · 4 Oct 2026

Compared on browser isolation software

Free plan
Yesgithub.com
Isolation mode
remotegithub.com
Deployment model
hybridgithub.com

Facts

Purpose
BrowserGap is an open-source, clientless remote browser isolation solution for automation, security, privacy, and CBII.github.com · 3 Oct 2026
Remote browsing
It streams a remotely running browser interactively to a browser interface on the user's device.github.com · 3 Oct 2026
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.github.com · 3 Oct 2026
Embedding
Developers can embed a BrowserView in another web application to connect user flows across sites.github.com · 3 Oct 2026
Automation
BrowserGap can provide visibility into browser automation and allow a human to intervene when an automation job needs input.github.com · 3 Oct 2026
Browser controls
Supported browser functions include tabs, form input, file upload and download, modal dialogs, and clearing cache, history, and session cookies.github.com · 3 Oct 2026
Bandwidth
The project describes adaptive image resampling based on available bandwidth to help maintain responsiveness and image quality.github.com · 3 Oct 2026
Integrations
The README documents connecting Puppeteer to the browser service and an API method called VF.openSecurely(url).github.com · 3 Oct 2026
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.github.com · 3 Oct 2026
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.github.com · 3 Oct 2026
Free use
The repository says use is free for governments and non-profits, subject to stated in-house deployment conditions.github.com · 3 Oct 2026
Known limitations
The README lists text selection, page zoom, multi-touch, WebGL, and fluid multiple-window support as unimplemented or buggy.github.com · 3 Oct 2026
Platform prerequisites
The binary instructions list Windows, Mac OS, or Linux and require Google Chrome to be installed.github.com · 3 Oct 2026
Maker and contact
The README identifies Cris Stringfellow as the maker and gives [email protected] for business inquiries.github.com · 3 Oct 2026
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.raw.githubusercontent.com · 4 Oct 2026
Browser functions
Documented working functions include tabs, file upload and download, incognito tabs, session data clearing, form input, and touch or pointer scrolling.raw.githubusercontent.com · 4 Oct 2026
Deployment
The project can be self-hosted from source or run from a Docker image; the README notes Docker use has no sound.raw.githubusercontent.com · 4 Oct 2026
Supported operating systems
The README gives binary prerequisites for Windows, Mac OS, or Linux, with Google Chrome installed.raw.githubusercontent.com · 4 Oct 2026
Security contact
The repository security policy says to report vulnerabilities to [email protected] and lists the latest version as supported.github.com · 4 Oct 2026

Best BrowserGap alternatives

See all 12

Where it ranks on Everything Xiaomi

Is BrowserGap yours?

Claim it for free: prove the domain, then correct facts, plans and screenshots. An editor reviews every change.

Sources