Installation

The CLI ships as a single binary per operating system and architecture. There is no installer and no runtime dependency.

1. Download

Download the binary for your platform from your app’s SDK Downloads page in the Alphyn dashboard. Builds are published for:

OS	Architectures	Binary name
macOS	Apple silicon, Intel	alphyn-cli-darwin-arm64, alphyn-cli-darwin-amd64
Linux	x86-64, ARM64	alphyn-cli-linux-amd64, alphyn-cli-linux-arm64
Windows	x86-64	alphyn-cli-windows-amd64.exe

Download the SHA256SUMS file from the same page.

2. Verify the download

Every release ships a SHA256SUMS file. Verify the binary’s integrity before running it; the CLI runs inside your build pipeline, so this step matters:

sha256sum -c SHA256SUMS        # GNU / Linux
shasum -a 256 -c SHA256SUMS    # macOS

You should see OK next to the binary you downloaded.

3. Make it runnable

# macOS / Linux: mark the binary executable and put it on your PATH.
chmod +x alphyn-cli-darwin-arm64
mv alphyn-cli-darwin-arm64 /usr/local/bin/alphyn-cli

On Windows, place alphyn-cli-windows-amd64.exe in a directory on your PATH (rename it to alphyn-cli.exe if you prefer).

macOS Gatekeeper

The macOS binaries are checksummed but not yet Apple-notarized, so Gatekeeper may block the first run. After verifying the SHA-256 above, clear the quarantine attribute:

xattr -d com.apple.quarantine /usr/local/bin/alphyn-cli

(or approve it once under System Settings → Privacy & Security).

4. Confirm

alphyn-cli --version
alphyn-cli --help

Keeping the CLI current

Update the CLI in place at any time. The new binary is downloaded, its SHA-256 is verified, and the running binary is atomically replaced, and the CLI never downgrades:

alphyn-cli self-update --android-api-key <your-key>

Reproducible builds

Releases are built with a pinned Go toolchain and -trimpath, so an auditor can rebuild a release from source and confirm the binaries are byte-for-byte identical to the published ones, a property that matters for banking and government supply chains.