Skip to content

Installation

The pure CLI is a single statically linked binary with no runtime dependencies — there is no Node.js or compiler toolchain to install, because every build runs in the cloud on api.pure.dev.

Distributed as a Debian package from Pure’s own apt repository, apt.pure.dev.

Terminal window
curl -fsSL https://apt.pure.dev/install.sh | sudo sh

This trusts the signing key, registers the repository, and installs pure. Verify it:

Terminal window
pure version

If you’d rather not pipe a script to sh, run the same steps yourself.

  1. Trust the repository signing key:

    Terminal window
    sudo install -d -m 0755 /usr/share/keyrings
    curl -fsSL https://apt.pure.dev/pure.gpg \
    | sudo tee /usr/share/keyrings/pure-archive-keyring.gpg > /dev/null
  2. Add the repository (modern deb822 format):

    Terminal window
    sudo tee /etc/apt/sources.list.d/pure.sources > /dev/null <<EOF
    Types: deb
    URIs: https://apt.pure.dev
    Suites: stable
    Components: main
    Architectures: $(dpkg --print-architecture)
    Signed-By: /usr/share/keyrings/pure-archive-keyring.gpg
    EOF
  3. Install:

    Terminal window
    sudo apt update
    sudo apt install pure
Terminal window
brew tap getpure/pure
brew install pure

No need to run the curl installer first — this doesn’t depend on it.

Terminal window
curl -fsSL https://brew.pure.dev/install.sh | sh

Works on both Apple Silicon and Intel Macs (the script detects your architecture automatically) and installs to /usr/local/bin. Use this on Intel until Homebrew support for Intel lands.

Install methodPlatform
apt (apt.pure.dev)Debian / Ubuntu, amd64 and arm64
Homebrew (getpure/pure)macOS, Apple Silicon (Intel coming soon)
curl (brew.pure.dev)macOS, Apple Silicon and Intel

Windows is planned but not available yet. See Language → OS support for what your compiled binaries can target.

Linux: once the repository is registered, pure upgrades like any other package:

Terminal window
sudo apt update && sudo apt upgrade pure

macOS (Homebrew):

Terminal window
brew upgrade pure

macOS (curl): re-run the install command — it always fetches the latest build:

Terminal window
curl -fsSL https://brew.pure.dev/install.sh | sh

Every command needs an API key. The CLI resolves it in this order:

  1. the --api-key <key> flag
  2. the PURE_API_KEY environment variable
  3. the key stored by pure login

The friendliest path is to log in once:

Terminal window
pure login

This asks how you want to log in — generate a new key (opens your browser and mints one automatically) or paste an existing one — then verifies it against api.pure.dev and stores it in your OS keychain (falling back to ~/.config/pure/credentials, mode 0600, when no keychain is available). See Log in for the full flow, including the SSH/remote fallback and CI/headless setups. For CI, set PURE_API_KEY instead:

Terminal window
PURE_API_KEY=… pure build src/main.ts

See Create an API key if you’d rather mint one from the dashboard directly (e.g. for a service account, not a personal login).