Sovereign security for Indian enterprises
Most security tries to detect the attack. Vespertil contains it. Risky work runs inside a hardware-isolated boundary on infrastructure you own. No telemetry leaves the country, and your data never reaches us.
The default posture is to chase the threat: detect it, block it, watch the browser for it. It keeps losing, because it has to recognize the attack first.
Vespertil takes the other approach. Isolate the risky activity inside a hardware boundary, so a compromise is contained whether or not anyone saw it coming.
Sovereignty is decided by where data lives and who controls the infrastructure, not by a checkbox. Vespertil is built in India, by an Indian company, for Indian enterprises.
Everything runs on your own infrastructure. No browsing, content, or audit data reaches us, and no telemetry leaves the country. A foreign vendor cannot make that promise, because jurisdiction and geography decide it, not policy.
Every mediated event is written to a hash-chained, tamper-evident audit. By design it records the finding type, classifier, count, action, site, identity, and timestamp, and never the matched content itself. You get a compliance record without the audit log becoming a second copy of the sensitive data it was meant to protect.
// the matched-value field is absent, not redacted. The sensitive data is never written.
| Product | What it is | Stage |
|---|---|---|
| HyperGate NativePer-device isolation | Per-device hardware isolation on Windows, through the Windows Hypervisor Platform. The strongest per-user form. | In development · design partner |
| HyperGate ServerCentralized isolation | Centralized isolation on your own servers, with users connecting as thin clients. For untrusted endpoints and central control at scale. | Roadmap |
| VesperSovereign browser | A browser on Gecko, the one major engine both open source and independent of Google. De-googled, no foreign telemetry, controllable by the enterprise. Runs standalone or inside HyperGate. | Early access · October 2026 |
Governance lives at the containment boundary, not inside the browser, so the controls apply to whatever runs in the box: stock Chromium for an enterprise whose internal applications assume it, an untrusted attachment, or a legacy desktop application that should not run on the host.