Skip to content
SPECIFICTION
Get listed

BrowserGap

github.com

Free plan WebWindowsmacOSLinuxAPISelf-hosted
Visit github.com
Spec score 9.0 #2 of 55 in WebSocket Tools

What it is

BrowserGap is an open-source remote browser isolation solution for automation, security, privacy, and CBII. It runs a browser remotely and streams the page as pixels to a browser interface on the user's device, so the page's HTML, CSS, and JavaScript do not execute there. Users can work with tabs, forms, file transfers, modal dialogs, incognito tabs, and session-data clearing. Developers can embed a BrowserView in another web app, connect Puppeteer, or use the VF.openSecurely(url) API method. BrowserGap can also expose automation activity so a person can intervene when a job needs input. It adjusts image resampling to available bandwidth. The project can be self-hosted from source or run in Docker; binary instructions require Google Chrome on Windows, Mac OS, or Linux. Secure document viewing with content disarm and reconstruction is supported, but the source-available edition requires users to set up the viewer. The community edition is free under stated in-house deployment conditions. A managed session is listed at $3.81, paid once.

Spec sheet

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

Plans and prices

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 Read 4 Oct 2026 · raw.githubusercontent.com
Managed session $3.81, paid once A session; duration or other limits not stated Read 4 Oct 2026 · raw.githubusercontent.com
Pro / license exemption Priced on request Flexible licenses, maintenance, deployment, delivery, and custom development options; contact maker Read 4 Oct 2026 · raw.githubusercontent.com

Every BrowserGap plan and price →

Strong points and limits

Strong points

  • Remote pages are sent as pixels, not executed on the client.
  • Supports tabs, forms, file transfers, and incognito tabs.
  • Can embed BrowserView in another web application.
  • Puppeteer connection and VF.openSecurely(url) are documented.
  • Can be self-hosted or run in Docker.

Limits

  • Text selection and page zoom are unimplemented or buggy.
  • WebGL and fluid multiple-window support are limited.
  • Document viewer setup is required for the source-available edition.
  • Binary use requires Google Chrome.

Who it suits

BrowserGap suits developers and organizations seeking remote browser isolation for automation, security, privacy, or CBII. It is also relevant where a human needs visibility into an automation session and the option to intervene.

BrowserGap in depth

Read the full write-up

BrowserGap is an open-source remote browser isolation tool for developers and organizations building security-conscious browsing or human-assisted automation workflows. It is most appealing when remote rendering and integration flexibility matter more than a turnkey browser experience; its interaction gaps and setup demands narrow its fit.

Overview

BrowserGap runs web pages in a remote browser and streams their rendered pixels to a browser interface on the user’s device. The page’s HTML, CSS, and JavaScript stay off that device, a useful boundary for privacy- and security-focused browsing. The project supports self-hosting from source or Docker, with a hybrid deployment model.

Its distinctive value is combining isolation with automation visibility: a person can watch an automated browser job and intervene when it needs input. That makes BrowserGap a more natural fit for teams developing assisted browser workflows than for buyers looking for a complete managed security suite.

Key features

Remote sessions and controls

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. Those controls cover many routine interactions, while adaptive image resampling adjusts images to available bandwidth to help balance responsiveness and quality.

There are important compromises: text selection, page zoom, multi-touch, and WebGL are unimplemented or buggy, as is fluid use of multiple windows. Users whose work depends on those interactions should look elsewhere rather than assume a streamed browser will behave like a local one.

Embedding and automation

Developers can embed a BrowserView in another web application to connect user flows across sites. The README documents a Puppeteer connection to the browser service and an API method, VF.openSecurely(url). Together with human intervention during automation, these options suit teams building browser-based workflows that need a person to step in, though they require integration work rather than providing a finished workflow product.

Document security and deployment

Secure document viewing with content disarm and reconstruction is supported, but the source-available edition requires the operator to set up the document viewer. That prerequisite adds implementation work for teams that need document protection. The binary instructions call for Windows, Mac OS, or Linux and an installed Google Chrome; Docker is another deployment route, but Docker use has no sound.

Pricing

BrowserGap is freemium, with a free plan and paid options. The Source-available community edition costs 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 organizations able to run the software themselves; the exemption’s conditions matter if deployment is not in-house.

The Managed session costs $3.81, paid once for a session.

Pro / license exemption has custom pricing. It offers flexible licensing, maintenance, deployment, delivery, and custom development options through the maker. This route fits organizations needing commercial licensing or tailored support, while the free community edition gives up those stated commercial options. The repository describes dual licensing under AGPL-3.0 and a custom exemption, with commercial licensing available by contacting the maker.

Platforms

BrowserGap supports API, Linux, macOS, self-hosted, web, and Windows. Binary use requires Google Chrome on Windows, Mac OS, or Linux. Teams can run it from source or Docker, with the Docker sound limitation worth considering for workflows that depend on audio.

Who it's for

BrowserGap suits developers integrating remote browsing into another application, teams that want a human to oversee automation, and security-conscious organizations comfortable operating their own browser service. Its free use conditions make it relevant to governments, researchers, journalists, and nonprofits that meet the in-house deployment requirements.

It is a weaker choice for users who need dependable text selection, zoom, WebGL, multi-touch, or smooth multiple-window use, or for teams unwilling to set up a document viewer and manage deployment prerequisites. Buyers seeking a managed security product should compare alternatives rather than assume BrowserGap provides that operating model.

Pros and cons

Pros: Remote rendering keeps page code off the client device, providing a clear separation for isolation-focused use.

Pros: BrowserView embedding, Puppeteer connectivity, and human intervention support assisted automation workflows.

Pros: A free source-available edition and self-hosting offer a route for eligible organizations that can manage deployment.

Cons: Text selection, zoom, multi-touch, WebGL, and fluid multiple-window support have notable gaps.

Cons: Secure document viewing requires operators to arrange their own viewer in the source-available edition.

Cons: Chrome is a binary prerequisite, and Docker use has no sound.

Alternatives

Browser Isolation Software is the broader category to explore when comparing browser isolation approaches.

Netzilo Enterprise Browser is worth comparing if a free plan with a stated allowance of up to five users and 100 devices, plus a free trial, better matches the buying decision.

Check Point Harmony SASE is a paid option with a free trial and a license requirement after the 30-day trial.

Netskope One Private Access is an enterprise product with a free trial and no free plan.

Zscaler Private Access is a paid alternative whose Standard tier is described as limited private access for 5% of users.

Cisco Secure Access is a paid alternative with a free trial and tiered pricing based on covered-user count and subscription term.

Keeper Remote Browser Isolation is a quote-based option with a free trial, but no free plan.

iboss Cloud is a paid option whose Zero Trust Core plan includes web filtering, URL categorization, basic CASB controls, HTTPS decryption, and Cloud Connector agents.

DefensX Remote Browser Isolation is a paid alternative with a free trial; its Core plan has 30-day log retention, while Premium adds remote browser isolation and 90-day retention.

Verdict

Choose BrowserGap if you need remote pixel-rendered browsing tied to automation or an embedded user flow, and can handle self-hosting, Chrome prerequisites, and the viewer setup. Its strongest reason to choose is that combination of isolation and human-visible automation; its strongest reason to look elsewhere is the incomplete interaction set and the work required to turn the source-available edition into a complete deployment.

Verdict

BrowserGap combines remote rendering with browser controls, embedding, and automation visibility. Check the listed interaction limitations and document-viewer setup requirement against your intended use.

Where Specifiction places it

Alternatives to BrowserGapAll alternatives →