Standard install
curl -fsSL https://cli.smplify.com/install.sh | shInstall the Smplify CLI with the branded endpoint.
Use the standard install path for public docs, pin exact versions for controlled rollouts, and validate the release-backed artifact flow for production environments.
Install methods
The branded installer is the canonical public path today, with pinned installs and manual script access available when teams need deterministic rollout behavior.
Install a specific version
curl -fsSL https://cli.smplify.com/install.sh | sh -s -- --version v0.1.0Manual script path
curl -fsSL https://raw.githubusercontent.com/smplify-mdm/smplify-cli/main/scripts/install.sh | shVerification
After installation, verify the binary is on the path, confirm the version, and re-run the installer for upgrades as new releases become available.
Verify install
smplify --version
smplify auth loginUpgrade path
curl -fsSL https://cli.smplify.com/install.sh | shHomebrew
Official Homebrew formula submission is planned after stable release and packaging review.
Planned install command
brew install smplifyEnterprise rollout
Pin releases in CI and internal runbooks, prefer the branded endpoint in end-user docs, and use JSON output for any automation or AI-assisted execution path.
Recommended for teams
- Pin a specific release in CI and internal documentation
- Use
--output jsonin automation and agent workflows - Validate the installer endpoint as part of rollout checks
Operational note
Official Homebrew support is intentionally sequenced after stable release packaging review, so the branded installer remains the canonical public path today.