Vault-OS Background Paths
Vault-OS Background Paths
All downloads
// APPLIANCE
v1.0.9.1Building

Vault-OS
for Windows.

The appliance itself. Download it, install it, watch it build its encrypted enclave. It stops at licence activation, because it is bound to one machine’s TPM — that is the evaluation, not a demo.

Publishing to the mirror
VAULT_OS
Archive
Explorer
Sessions
Groups
Pipeline
Map
Loops
Telemetry
Explorer · Legal
Windows · interface
// REQUIREMENTS

What it needs. Exactly.

OS
Windows Server 2019+ or Windows 11 Pro, x64
Security
TPM 2.0 enabled in firmware. Administrator rights required.
GPU
NVIDIA, 8 GB VRAM minimum; 24 GB+ for anything past a 7B model
Memory
32 GB RAM minimum, 64 GB recommended
Disk
120 GB free — the media alone is ~22 GB and the enclave grows
Network
None required, ever. LAN only, so clients can reach it.
Licence
Required. Hardware-bound, issued by IronGap.

It will not run unlicensed. That is the point.

Vault-OS binds itself to this machine’s TPM, system UUID and MAC at activation. An unlicensed copy installs, boots, builds its enclave and stops — so you can evaluate everything up to the point where a contract starts.