Installing the kamu CLI
kamu is the command-line client for the KamuHub platform. One binary, one
login, every service: websites (kamu sites), git (kamu clone), DNS
(kamu dns), uptime and error telemetry (kamu status), CDN assets
(kamu assets), databases (kamu db) and apps (kamu bee).
Source and releases: github.com/kotisivukamu/kamucli.
Install
Pick one of the three options. All of them give you the same kamu binary.
Homebrew (macOS and Linux)
brew install kotisivukamu/tap/kamu
Upgrade later with brew upgrade kamu.
Pre-built binary
Every release on the
Releases page ships
tarballs for darwin_amd64, darwin_arm64, linux_amd64 and linux_arm64,
plus a checksums.txt. Archive names follow
kamu_<version>_<os>_<arch>.tar.gz (no v prefix in the version).
# Example: Linux on x86_64, replace the version with the latest release.
VERSION=0.9.0
curl -fsSLO "https://github.com/kotisivukamu/kamucli/releases/download/v${VERSION}/kamu_${VERSION}_linux_amd64.tar.gz"
curl -fsSLO "https://github.com/kotisivukamu/kamucli/releases/download/v${VERSION}/checksums.txt"
sha256sum --check --ignore-missing checksums.txt
tar -xzf "kamu_${VERSION}_linux_amd64.tar.gz" kamu
sudo install -m 0755 kamu /usr/local/bin/kamu
On macOS use shasum -a 256 --check --ignore-missing checksums.txt and the
darwin_arm64 (Apple silicon) or darwin_amd64 (Intel) archive.
Windows is not built. Use WSL and the Linux archive.
From source
Requires Go 1.25 or newer.
go install github.com/kotisivukamu/kamucli/cmd/kamu@latest
The binary lands in $(go env GOPATH)/bin. Make sure that directory is on
your PATH.
Verify
kamu version
Log in
Interactive use goes through KamuID with a device flow. kamu auth login
prints a verification URL and a code, opens the browser (skip with
--no-browser), and after you approve it mints a kamuhub access key scoped to
one organization:
kamu auth login # scopes the key to your first organization
kamu auth login --org acme # or pick the organization explicitly
kamu auth whoami
Credentials are stored in ~/.kamu/config.yml. kamu auth logout removes
them.
Agents and CI: use an access key
Do not run the device flow on a build machine or an agent's VM. Create a scoped access key in the dashboard instead (app.kamuhub.com → Manage → Access keys), choose the grants it needs and a TTL, and export it:
export KAMU_ACCESS_KEY=...
kamu sites list
kamu clone my-project
cd my-project && git push
kamu clone installs kamu git-credential as the repo-local credential
helper, so any ordinary git invocation afterwards presents the access key.
The key never ends up in the remote URL or on disk. Revoking the key in the
dashboard cuts its access immediately, including git.
Next: kamu CLI: commands.
Shell completion
kamu completion bash > /etc/bash_completion.d/kamu # bash
kamu completion zsh > "${fpath[1]}/_kamu" # zsh
kamu completion fish > ~/.config/fish/completions/kamu.fish
Run kamu completion --help for the full per-shell instructions.
Environment variables
| Variable | Purpose |
|---|---|
KAMU_ACCESS_KEY | Scoped kamuhub access key. Used instead of a stored login by sites, clone, status, assets and publish. |
KAMU_ACCESS_TOKEN | Raw bearer token override for commands that talk to kamuid directly. Rarely needed. |
NO_COLOR / KAMU_NO_COLOR | Disable colored output. |
Most commands also accept --key as an alternative to KAMU_ACCESS_KEY.