Download
The PyreData app and thepyre command line
Everything the dashboard does, from a terminal or a script: volumes,
restore points, views, appliances.
One binary, no runtime to install; pyre update keeps it current.
The desktop app for Apple silicon (macOS 13 or later): your volumes, time travel,
history and the engine in one window; it includes the pyre command and the engine runtime.
The desktop app (Apple silicon)
1. Install — open the downloaded PyreData-arm64.pkg (signed with
PyreData's Developer ID and notarised by Apple). The installer puts PyreData in Applications, the
pyre command in /usr/local/bin, and starts the agent with your login.
2. Sign the Mac in — open PyreData and paste an enrolment code. The code works once and for a day;
it signs in both the app and the pyre command. The first sign-in offers to set up the engine
(about 500 MB from pyredata.io).
An enrolment code comes from your account: log in and create one here.
SMB volumes mount on the Mac itself (under ~/PyreData); NFS and iSCSI volumes are served to other
machines on your network. Intel Macs: a build is not published yet. Removing: drag PyreData out of Applications
after Stop safely; the vault keeps everything.
The pyre command line
1. Install
curl -fsSL https://www.pyredata.io/dl/cli/install.sh | sh
It installs into ~/.local/bin, yours alone: no
password, no sudo, and pyre update and
pyre uninstall need none either. If that directory is not on
your PATH yet it adds one line to your shell file; then
open a new terminal (or run source ~/.zshrc,
~/.bashrc on Linux bash) before using pyre.
Set PYRE_INSTALL_DIR=/usr/local/bin for a system-wide install.
Homebrew instead
brew tap pyredata/pyre https://gitlab.pyredata.io/pyredata/homebrew-pyre.git brew trust pyredata/pyre brew install pyre
Homebrew 7 refuses a third-party tap until you say you trust it; that is
the second line. Apple silicon and Intel are both served; the formula
picks the right build. brew upgrade pyre updates it.
The installer downloads the build for this computer from
https://www.pyredata.io/dl/cli/, checks it against a signed checksum,
and puts pyre on your PATH with tab completion for bash, zsh,
fish and PowerShell. Nothing else is touched. Every release, its
checksums and the signing keys are listed at
https://www.pyredata.io/dl/cli/.
Direct downloads of the current release:
macOS Apple silicon,
macOS Intel,
Linux x86-64,
Debian package,
Windows pyre.exe,
Windows zip;
checksums in SHA256SUMS, signed
(.minisig) with the key at
keys/. Every version:
https://www.pyredata.io/dl/cli/. Command reference:
docs/pyre.md (the same text as
pyre --help and man pyre).
2. Log in
A token comes from your account: log in and create one here, or on the dashboard under API tokens.
pyre auth login
It asks for the token; paste it. Or pass it:
pyre auth login --token pyre_…
The token is saved in ~/.pyre/config (Windows:
%APPDATA%\pyre\config), readable by you alone. It acts as
you and nobody else; pyre auth whoami shows who that is.
Scripts can pass it as PYRE_TOKEN instead of saving it.
3. Try it
pyre volume list pyre --help
Every command has --help with examples; add
-o json for scripts and --yes to skip confirmations.
Exit codes: 0 ok, 1 error, 2 usage, 3 not logged in, 4 not found, 5 a
confirmation was needed and --yes was absent. pyre batch
runs several commands from a file or stdin.
Removing it
pyre uninstall
pyre uninstall --dry-run lists what goes;
--purge removes the saved token and config too.
Installed with Homebrew: brew uninstall pyre instead.
Without --purge the saved token stays in
~/.pyre/config (Windows: %APPDATA%\pyre\config); revoke
it on the dashboard too if the computer is leaving your hands.