FREEDOM251

Freedom251 › WebSocket Tools

BrowserGap

Free plan APILinuxMacSelf-hostedWebWindows

Visit BrowserGap Alternatives Pricing

BrowserGap's own site

What BrowserGap is

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, paid once.

Who it suits

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 it does well

  • 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

Limits

The free community edition is subject to stated in-house deployment conditions. The source-available edition requires users to set up the secure document viewer themselves; text selection, page zoom, multi-touch, WebGL, and fluid multiple-window support are listed as unimplemented or buggy.

Plans

PlanBilled and limitsPrice
Source-available community editionAGPL-3.0 and custom exemption · government, researchers, journalists, and nonprofits may use without purchase under stated in-house deployment conditionsFree
Managed sessionA session; duration or other limits not stated$3.81, paid once
Pro / license exemptionFlexible licenses, maintenance, deployment, delivery, and custom development options; contact makerOn request

As github.com lists them, read 4 Oct 2026. The maker's own page has the final word.

Getting started

  1. Open the BrowserGap project website on GitHub.
  2. Choose whether to self-host from source or run the Docker image.
  3. For binary use, use Windows, Mac OS, or Linux with Google Chrome installed.
  4. Use the free community edition under its stated in-house deployment conditions, or arrange a managed session listed at $3.81, paid once.
  5. Connect Puppeteer or use the documented VF.openSecurely(url) API method if needed.

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 — 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, paid 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.

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.

Verdict

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.

Questions

Is BrowserGap free?

The source-available community edition is listed as free. Free use for governments and non-profits is subject to stated in-house deployment conditions.

What does a managed session cost?

A managed session is listed at $3.81, paid once. No duration or other session limits are stated.

Which systems can run BrowserGap?

Binary instructions list Windows, Mac OS, or Linux and require Google Chrome. The listed platforms also include API, web, and self-hosted.

Is BrowserGap open source?

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

Can BrowserGap connect to Puppeteer?

Yes. The README documents connecting Puppeteer to the browser service, as well as an API method called VF.openSecurely(url).

Facts from BrowserGap's own pages

Automation
The project can provide visibility into Puppeteer, Playwright, or DevTools Protocol browser automation and allow human intervention in jobs. · raw.githubusercontent.com, 4 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
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
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
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. · raw.githubusercontent.com, 4 Oct 2026
Embedding
Developers can embed a BrowserView in another web application to integrate user flows. · raw.githubusercontent.com, 4 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
Integrations
The README documents Puppeteer and Playwright use, a DevTools connection at localhost:5002, and a JavaScript SDK with VF.openSecurely(url). · raw.githubusercontent.com, 4 Oct 2026
Known limitations
The README lists text selection, WebGL, multiple windows, and several zoom and mobile touch functions as unimplemented or buggy. · raw.githubusercontent.com, 4 Oct 2026
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. · raw.githubusercontent.com, 4 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
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
Platform prerequisites
The binary instructions list Windows, Mac OS, or Linux and require Google Chrome to be installed. · github.com, 3 Oct 2026
Purpose
BrowserGap is described as a clientless remote browser isolation product for security, automation, and privacy. · github.com, 4 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
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
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
Supported operating systems
The README gives binary prerequisites for Windows, Mac OS, or Linux, with Google Chrome installed. · raw.githubusercontent.com, 4 Oct 2026

Where BrowserGap stands on Freedom251

Look at these too