Compatibility & prerequisites

The stillvault CLI is a single, self-contained binary — the control commands (create an org, seal a secret, enrol an agent) and the local agent runtime ship in the same executable. It runs natively on Linux, macOS, and Windows.

Supported platforms

OS	Architectures	Status
Linux	`amd64`, `arm64`	Supported
macOS	`amd64` (Intel), `arm64` (Apple Silicon)	Supported
Windows	`amd64`, `arm64`	Supported

Minimum versions:

Linux — any modern distribution (kernel 3.17+).
macOS — macOS 11 (Big Sur) or later.
Windows — Windows 10 / Windows Server 2019 or later.

Prerequisites

None. The binaries are statically linked, so there is no runtime to install — no glibc version to match, no .NET, no interpreter. Download the binary for your platform, put it on your PATH, and run it.

Who asked is recorded on every platform

When a local process asks the agent for a secret, the request is attributed to the exact process and user that made it — verified by the operating system, not by anything the caller can claim. That attribution travels with the approval, so the human approving a release always sees who is asking. This holds identically on Linux, macOS, and Windows; on Windows the agent listens on a per-user named pipe, and on Linux and macOS on a per-user socket. If the agent cannot establish who is asking, it refuses the request rather than releasing a secret blindly.

Production agents most often run in Linux containers, but macOS and Windows are first-class for local and development agents and for the full control CLI.

Install

Linux / macOS:

curl -fsSL https://stillvault.ai/install.sh | sh

Windows (PowerShell):

irm https://stillvault.ai/install.ps1 | iex

Re-running either installer upgrades to the latest version.

Verifying a download

Every binary and install script is published with its own .sha256 checksum, and the full release is listed in a SHA256SUMS manifest. The installers verify the binary checksum automatically.

Verify the installer before running it

So you don’t have to pipe an unverified script straight to a shell:

# Linux / macOS
curl -fsSLO https://stillvault.ai/install.sh
curl -fsSL  https://stillvault.ai/install.sh.sha256 | sha256sum -c   # expect "install.sh: OK"
sh install.sh

# Windows
irm https://stillvault.ai/install.ps1 -OutFile install.ps1
"$((Get-FileHash install.ps1 -Algorithm SHA256).Hash.ToLower())  install.ps1"   # compare to:
irm https://stillvault.ai/install.ps1.sha256

Verify a binary directly

Each binary has a standalone checksum (and all are in SHA256SUMS):

curl -fsSLO https://stillvault.ai/dl/stillvault-linux-amd64
curl -fsSL  https://stillvault.ai/dl/stillvault-linux-amd64.sha256 | sha256sum -c

Signing & notarization

macOS — binaries are signed with an Apple Developer ID and notarized, so Gatekeeper opens them with no extra steps.
Linux — the SHA256SUMS manifest is published with a detached minisign signature (SHA256SUMS.minisig) for provenance. The install.sh script verifies it automatically when minisign is installed. To verify by hand:
```
minisign -Vm SHA256SUMS -P RWT95647+V/HhBU6+gE8NGfOq4DPQikZKPdH1s3W8xK2ZERlqu4F5nE+
```
Stillvault release-signing public key (minisign, key ID 84C75FF93BAEE7FD):
```
RWT95647+V/HhBU6+gE8NGfOq4DPQikZKPdH1s3W8xK2ZERlqu4F5nE+
```
Windows — the binary is not yet code-signed, so SmartScreen may show an “unrecognized app” warning on first run; the published checksum proves integrity in the meantime.