Download

Two binaries. No runtime to install.

The saved CLI drives everything the dashboard can do. The local worker is what runs backups on your own hardware, so the source connection never leaves your network. Both are single static binaries.

macOS

Apple silicon and Intel

Linux

amd64 and arm64

Windows

amd64 and arm64

The CLI

saved

Sign in with a device code, then work from the terminal. Workspaces, members, workers, backups, runs, artifacts, restores and saved apply to reconcile a YAML file like any other infrastructure.

# macOS and Linux
curl -fsSL https://saved.sh/cli.sh | sh

saved login
saved workspace list

All CLI releases

The worker

saved-worker

Runs on a machine you control and polls for work. Its credential and the source connection stay in a local config file; we never receive either. Provision one from the CLI, then run it wherever the data lives.

curl -fsSL https://saved.sh/worker.sh | sh

saved worker provision prod-worker-1

# on the machine that holds the data
saved-worker --config ./config.yaml

All worker releases

Verify what you run

The worker holds your credentials. Check it before you trust it.

The local worker reads your database passwords and your encryption key. That is a lot to ask of a binary from the internet, so every release is checksummed and published from a tagged build you can trace back to a commit.

shasum -a 256 -c saved_checksums.txt