Install Nodus from a stable public URL.

Use the public installer URLs on this domain, or install with Cargo or Homebrew. Release assets still come from GitHub Releases, but the command you paste into docs stays stable.

Choose the install route that matches your workflow.

The public installer is the default. Cargo and Homebrew are there when teams already standardize on them.

macOS and Linux

Fetches the right release for the current OS and architecture.

curl -fsSL https://nodus.elata.ai/install.sh | bash

Windows PowerShell

PowerShell 7+ is the cleanest path, but Windows PowerShell also works.

irm https://nodus.elata.ai/install.ps1 | iex

crates.io

Install from crates.io if you want Cargo to manage the binary.

cargo install nodus

Homebrew

Installs the published release build through Homebrew.

brew install nodus-rs/nodus/nodus

Lock the release when you need exact reproducibility.

Use a version pin for CI, release validation, or any environment that should not move implicitly.

Pin a version

The installer supports a pinned version through NODUS_VERSION on Unix and PowerShell.

curl -fsSL https://nodus.elata.ai/install.sh | NODUS_VERSION=v0.5.2 bash

$env:NODUS_VERSION = "v0.5.2"
irm https://nodus.elata.ai/install.ps1 | iex

Checksum verification

The Unix installer supports inline verification. On Windows, download the script to a temporary path and invoke it with -Verify.

curl -fsSL https://nodus.elata.ai/install.sh | bash -s -- --verify

$script = Join-Path $env:TEMP "nodus-install.ps1"
irm https://nodus.elata.ai/install.ps1 -OutFile $script
& $script -Verify
Remove-Item $script

Inspect the endpoint before you hand it to a team.

The installer stays curl- and PowerShell-friendly while still exposing the raw routes and the install behavior.

What the public installer does

It detects the host platform, resolves the release tag, downloads the matching archive, optionally verifies the checksum, and installs the binary into a standard user-scoped path.

Raw installer endpoints

These routes are published as plain text and are intended to be curl- and PowerShell-friendly.

/install.sh /install.ps1