Enterprise-browser products instrument a managed Chromium, layering software controls and DLP inside the browser. HyperGate is a different architecture. Risky activity runs inside a hardware-isolated, policy-governed, audited VM. A compromise inside the box is contained: it does not reach the host.
Per-device hardware isolation on Windows, through the Windows Hypervisor Platform. The strongest per-user form.
Centralized isolation on your own servers, with users connecting as thin clients. For untrusted endpoints and central control at scale.
The enterprise-browser category instruments a managed Chromium: software controls and DLP added inside the browser process. That is a control layer in the same trust domain as the browser it governs. It handles the ordinary motions, the paste and the upload, but it shares the browser’s fate: a compromise that takes the browser takes the controls with it, precisely when you most need them.
HyperGate moves the boundary below the operating system. The risky activity runs inside a genuine hardware-isolated virtual machine, enforced by the hypervisor, not by a sandbox inside the application. Containment is structural. It does not depend on recognizing the attack, and it is not a feature a browser-control product can add with a toggle.
Governance lives at the containment boundary, in egress inspection and a value-free audit, not inside the browser. Because the controls sit at the boundary, they apply to whatever runs in the box. The browser is just one guest.
An enterprise standardized on Chromium for its internal web applications can run stock Chromium inside the containment and still get the isolation, the DLP, and the audit.
Open an untrusted attachment, run a risky or legacy desktop application, sandbox an untrusted tool. Anything that runs in the guest is contained.
A future direction: an ISV embeds the containment as a component rather than building its own hypervisor layer. Not available today.
HyperGate Native runs the isolation on the user’s own Windows machine through the Windows Hypervisor Platform. It is the strongest per-user form, and the edition in active development with design partners.
HyperGate Server moves the isolation onto the customer’s own servers. Users connect as thin clients, so untrusted, unmanaged, or heterogeneous endpoints never run the risky activity locally. It is the right model for central control, audit, and compliance at scale, and is currently on the roadmap.
Island and similar products instrument a managed Chromium. HyperGate isolates the workspace in hardware. A containment boundary is a stronger, different architecture, not something a browser-control product adds with a feature toggle.
Sovereignty is structural. Everything runs on your own infrastructure with no vendor data egress, and jurisdiction is decided by geography. A foreign vendor cannot make that promise.
You can stand up Linux VMs yourself. The isolation is the easy part, the piece anyone can assemble. The value is the governed, audited, compliant control plane on top: DLP enforcement, a tamper-evident value-free audit, signed central policy, the management console, and the compliance evidence a DIY stack cannot produce.
HyperGate Native is in active development. If your organization runs sensitive work through the browser and wants hardware containment on infrastructure you control, talk to us about a design-partner engagement.