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

Vault-OS
for macOS.

An APFS sparse-bundle enclave, written and likewise unexercised. Same rule as Linux: unrun encryption code is not a release.

Not released
VAULT_OS
Archive
Explorer
Sessions
Groups
Pipeline
Map
Loops
Telemetry
Explorer · Legal
macOS · interface
// REQUIREMENTS

What it needs. Exactly.

OS
macOS 13 Ventura or later, Apple silicon
Enclave
APFS sparse bundle via hdiutil — implemented, unexecuted
Status
Unreleased — needs Apple hardware to verify
// WHY NOT YET

The APFS sparse-bundle enclave is likewise unexercised. Needs Apple hardware to build and verify.

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.