Manual Downloads

Manual downloads are intended for offline installs, pinned versions, air-gapped hosts, and custom images where a package manager or installer script is not appropriate.

The Download page exposes the available packages by operating system and CPU architecture. After a package is selected, it shows the package id, version, filename, and SHA-256 checksum for verification.

Unix systems

Download the archive that matches the target host, verify the checksum shown on the Download page, then extract the binary into a directory on PATH.

sha256sum rstream-*.tar.gz
# or: shasum -a 256 rstream-*.tar.gz
tar xvzf rstream-*.tar.gz -C /usr/local/
rstream --version

The exact extraction path depends on the archive layout and local filesystem policy. Long-lived hosts should prefer the package-manager path when one is available, because upgrades then follow the normal system update workflow.

Windows

Download the Windows archive that matches the target architecture, verify the checksum shown on the Download page, then extract it into a directory included in PATH.

Get-FileHash .\rstream-*.zip -Algorithm SHA256
Expand-Archive -Path .\rstream-*.zip -DestinationPath "C:\Program Files\"
rstream --version

When PowerShell execution policy blocks a launcher installed through npm, use rstream.cmd or the Windows installer path documented in Windows. Manual archives avoid npm launcher generation but still need the extracted executable to be discoverable through PATH.

Configuration

Manual installation only places the binary. Runtime configuration follows the same model as every other install method: authenticate with rstream login, select a project with rstream project use <project-endpoint> --default, or provide RSTREAM_ENGINE and RSTREAM_AUTHENTICATION_TOKEN explicitly for non-interactive environments.