CyberCLI
Sign in →

Download CyberCLI

One binary.
Six platforms.
Signed end to end.

The full Sovereign AI SOC engine in a single file. No package manager required, no daemon to register, no kernel modules to compile. macOS, Linux, and Windows. Free up to 10 endpoints, no card. Verified at three layers: SHA-256 manifest, Sigstore keyless signature, and platform-native code signing.

Latest release · v0.1.0 Published recently Release notes →
Fastest path

One line. Detect your platform. Install verified.

Our installer detects your OS and CPU, downloads the right binary from GitHub Releases, verifies the SHA-256 against our signed manifest, drops the binary into /usr/local/bin, and prints your next command. On Windows, the PowerShell installer does the same to %LOCALAPPDATA%\CyberCLI.

macOS · Linux
curl -sSfL https://cybercli.com/install.sh | bash
Windows (PowerShell)
iwr -useb https://cybercli.com/install.ps1 | iex

Prefer a manual install? Pick your platform below.

Manual install — pick your platform.

Every tarball ships with SHA-256 + Sigstore signature

macOS
Apple Silicon (M1, M2, M3, M4)
Target: darwin-arm64
Download .tar.gz
Verify the download (recommended)
SHA-256
sha256sum cybercli-darwin-arm64.tar.gz
# compare against SHA256SUMS from the release
Sigstore (cosign)
cosign verify-blob \
  --certificate SHA256SUMS.pem \
  --signature SHA256SUMS.sig \
  --certificate-identity-regexp '.+@whoisepic' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com \
  SHA256SUMS
After install: cybercli init
macOS
Intel-based Macs
Target: darwin-amd64
Download .tar.gz
Verify the download (recommended)
SHA-256
sha256sum cybercli-darwin-amd64.tar.gz
# compare against SHA256SUMS from the release
Sigstore (cosign)
cosign verify-blob \
  --certificate SHA256SUMS.pem \
  --signature SHA256SUMS.sig \
  --certificate-identity-regexp '.+@whoisepic' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com \
  SHA256SUMS
After install: cybercli init
Linux
x86-64 — Ubuntu, Debian, RHEL, Arch
Target: linux-amd64
Download .tar.gz
Verify the download (recommended)
SHA-256
sha256sum cybercli-linux-amd64.tar.gz
# compare against SHA256SUMS from the release
Sigstore (cosign)
cosign verify-blob \
  --certificate SHA256SUMS.pem \
  --signature SHA256SUMS.sig \
  --certificate-identity-regexp '.+@whoisepic' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com \
  SHA256SUMS
After install: cybercli init
Linux
ARM64 — Raspberry Pi 4/5, AWS Graviton, Ampere
Target: linux-arm64
Download .tar.gz
Verify the download (recommended)
SHA-256
sha256sum cybercli-linux-arm64.tar.gz
# compare against SHA256SUMS from the release
Sigstore (cosign)
cosign verify-blob \
  --certificate SHA256SUMS.pem \
  --signature SHA256SUMS.sig \
  --certificate-identity-regexp '.+@whoisepic' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com \
  SHA256SUMS
After install: cybercli init
Windows
Windows 11 + Server 2022 (x86-64)
Soon
Target: windows-amd64
Download .zip
Verify the download (recommended)
SHA-256
Get-FileHash cybercli-windows-amd64.zip -Algorithm SHA256
# compare against SHA256SUMS from the release
Sigstore (cosign)
cosign verify-blob \
  --certificate SHA256SUMS.pem \
  --signature SHA256SUMS.sig \
  --certificate-identity-regexp '.+@whoisepic' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com \
  SHA256SUMS
Microsoft Authenticode
Get-AuthenticodeSignature .\cybercli.exe
# Signed by CyberCLI LLC
After install: cybercli init
Windows
ARM-based Surface + Copilot+ PCs
Soon
Target: windows-arm64
Download .zip
Verify the download (recommended)
SHA-256
Get-FileHash cybercli-windows-arm64.zip -Algorithm SHA256
# compare against SHA256SUMS from the release
Sigstore (cosign)
cosign verify-blob \
  --certificate SHA256SUMS.pem \
  --signature SHA256SUMS.sig \
  --certificate-identity-regexp '.+@whoisepic' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com \
  SHA256SUMS
Microsoft Authenticode
Get-AuthenticodeSignature .\cybercli.exe
# Signed by CyberCLI LLC
After install: cybercli init

Trust chain

Three independent verification layers.

Sovereign software has to be verifiable software. Every release passes through three checks before it lands on your box, all reproducible offline by anyone with the right tools.

Layer 1

SHA-256 manifest

Every tarball has a 256-bit hash published in SHA256SUMS at the GitHub Release. A mismatch means the file was modified after we built it.

Layer 2

Sigstore keyless

Our GitHub Actions workflow signs SHA256SUMS with a short-lived certificate issued by Sigstore against the workflow's OIDC identity. Anyone can verify the artifact was built by our pipeline, not a stranger.

Layer 3

Platform code signing

macOS notarization (via Apple) and Microsoft Authenticode (CyberCLI LLC identity) so the OS itself trusts the binary on first run. No SmartScreen warnings, no xattr -d dance.

Don't want to do this yourself?

We'll install it for you.

Business and Enterprise tiers include white-glove onboarding. A CyberCLI engineer schedules a 60-minute session, screen-shares with your team, installs the binary, wires your first three connectors, configures your notification channels, and walks you through the dashboard. You leave the call with a live SOC.

Free + Pro tiers self-install with our installer above. Most operators are at first-incident triage within 30 minutes.

Schedule onboarding → Self-install guide →

Common questions

Is the install script safe to pipe into bash?

The script at https://cybercli.com/install.sh is plain readable bash. We recommend reviewing it before piping to bash on any new system — that's true of any installer. The script itself verifies SHA-256 before installing the binary, so even if you trust the install pipeline only halfway, the binary itself is hash-pinned to the release.

What if the install fails?

The installer is idempotent. Re-run it. If it still fails, run cybercli doctor — it walks every install + runtime invariant and tells you the exact command to fix any red light. Still stuck? Email hello@cybercli.com — a human replies same business day.

Does CyberCLI need root or admin?

Only at install time, to drop the binary into a system PATH directory. The CyberCLI engine itself runs as your user with no elevated privileges. The dashboard binds to 127.0.0.1, never inbound on a network interface.

Air-gapped install?

Download the tarball + SHA256SUMS + SHA256SUMS.sig on an internet-connected machine, sneakernet the bundle, verify, install. The binary never phones home for activation; the license is offline-verified by an Ed25519 signature embedded in the engine. See /architecture for the full signed-payload spec.

Source code?

The engine, the dashboard, and the marketing site all live at github.com/whoisepic/CyberCLI. Apache 2.0 for the engine. The Cyber Guild role LoRAs distribute from a separate signed registry (v1.x).

Next

You've got the binary. Now what?

Day one
First 30 minutes →
How it's built
Architecture →
Pick a tier
Pricing →