Installation

The pure CLI is distributed as a Debian package from Pure’s own apt repository, apt.pure.dev. It 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.

Quick install (recommended)

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

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

pure version

Manual install

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

Trust the repository signing key:

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

Add the repository (modern deb822 format):

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

Install:
Terminal window
```
sudo apt update
sudo apt install pure
```

Supported platforms

The CLI ships for Debian and Ubuntu on amd64 and arm64. The compiled output is a native binary built in the cloud — see Language → OS support for the platforms your binaries can target.

Updating

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

sudo apt update && sudo apt upgrade pure

Authentication

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

the --api-key <key> flag
the PURE_API_KEY environment variable
the key stored by pure login

The friendliest path is to log in once:

pure login

This verifies the key against api.pure.dev and stores it at ~/.config/pure/credentials (mode 0600). For CI, set PURE_API_KEY instead:

PURE_API_KEY=… pure build src/main.ts

See Create an API key to mint one.

Next steps

Authenticate and run your first build