Minimum Requirements

sos-vault ships as a self-contained appliance. This page lists the minimum operating system, hardware, and package dependencies the installer expects to find on a freshly imaged host.

Supported operating systems

• Ubuntu 22.04 LTS (Jammy)
• Ubuntu 24.04 LTS (Noble)
• Red Hat Enterprise Linux 8.x / 9.x
• Rocky Linux 8.x / 9.x
• AlmaLinux 8.x / 9.x

The installer will continue on an unrecognised distribution but the install is untested outside the list above.

Hardware floor

• RAM: 32 GB recommended. The installer warns below this floor but proceeds.
• CPU: 16 cores recommended. The installer warns below this floor but proceeds.
• System disk: a separate root volume for the OS and the appliance binaries (/opt/sos-vault, /var/lib/docker).
• Vault disk: a dedicated block device for the ZFS pool that backs /vault. Size depends on case retention — budget for the largest sosreport you will store, times the number of cases kept online.

Runtime dependencies

These are listed under Depends: in the deb control file and pulled in automatically by apt-get install on Ubuntu/Debian. On RHEL/Rocky/AlmaLinux, alien --to-rpm preserves the list and dnf resolves it.

• docker.io (or docker-ce) plus docker-compose-plugin
• ufw
• openssl
• sosreport
• zfsutils-linux
• rsync

Network

• TCP 80, 443 inbound from your analyst network. UFW is configured by the installer.
• Outbound 443 only needed for module downloads from the sos-vault Customer Portal and for optional LLM model pulls. The appliance does not phone home for licensing once the .lic is uploaded.

Licensing

You need a .lic file issued by the sos-vault Customer Portal. The appliance enforces the licensed seat count on user creation and blocks expired or revoked licenses. The license file is bound to this host's /etc/machine-id — ordering a new license is required when the appliance moves to new hardware.