Install
Install alforria from the universal installer, a prebuilt release binary, or a source build.
alforria ships as a single native binary. Choose the installer for the fastest path, a prebuilt binary for manual placement, or a source build when you want to compile it yourself. No Node.js or other language runtime is required.
Supported platforms
| Platform | Prebuilt binary | Installer |
|---|---|---|
| Linux x86_64 (glibc 2.35 or newer, OpenSSL 3) | alforria-linux-x86_64 |
Yes |
| macOS x86_64 | alforria-macos-x86_64 |
Yes |
| macOS aarch64 (Apple Silicon) | alforria-macos-aarch64 |
Yes |
| Windows x86_64 | alforria-windows-x86_64.exe |
No, download manually |
| WSL | Yes, using the Linux binary | Yes |
| Linux aarch64 | Not published | No, build from source |
Linux binaries are built on Ubuntu 22.04 so they run on distributions with
glibc 2.35 or newer, including Ubuntu 22.04 and later. They are dynamically
linked, so the system also needs the OpenSSL 3 (libssl.so.3,
libcrypto.so.3), zlib (libz.so.1), and zstd (libzstd.so.1) shared
libraries.
Installer (Linux, macOS, WSL)
curl -fsSL https://raw.githubusercontent.com/alforria-ai/alforria/main/packaging/install.sh | sh
The installer:
- resolves the latest GitHub release;
- downloads the asset for your OS and architecture;
- downloads the
.sha256sidecar and verifies the checksum withsha256sumorshasum; - installs
alforriato~/.local/bin.
It needs curl, uname, mktemp, and install. Verification needs
sha256sum or shasum; if neither is installed, the installer stops with an
error. If the .sha256 sidecar cannot be downloaded, it prints a warning and
installs the binary without verification.
Change the destination by setting ALFORRIA_INSTALL_DIR:
curl -fsSL https://raw.githubusercontent.com/alforria-ai/alforria/main/packaging/install.sh \
| ALFORRIA_INSTALL_DIR="$HOME/bin" sh
ALFORRIA_VERSIONpins a specific release tag. Thevprefix is optional.ALFORRIA_INSTALL_DIRchanges the destination.
If ~/.local/bin is not in your PATH, the installer prints the line to add
to your shell profile.
Prebuilt binaries
Download the asset for your platform from the
latest release.
Every binary has a .sha256 sidecar.
Linux and macOS:
curl -fLO https://github.com/alforria-ai/alforria/releases/latest/download/alforria-linux-x86_64
curl -fLO https://github.com/alforria-ai/alforria/releases/latest/download/alforria-linux-x86_64.sha256
sha256sum -c alforria-linux-x86_64.sha256
install -m 0755 alforria-linux-x86_64 ~/.local/bin/alforria
On macOS, shasum -a 256 -c alforria-macos-aarch64.sha256 verifies the
checksum when sha256sum is unavailable. Use alforria-macos-x86_64 on Intel
Macs and alforria-macos-aarch64 on Apple Silicon.
Windows:
# Download the .exe and its .sha256 sidecar, then compare hashes.
Get-FileHash .\alforria-windows-x86_64.exe -Algorithm SHA256
Get-Content .\alforria-windows-x86_64.exe.sha256
Rename the executable to alforria.exe, place it in a directory on PATH,
and run alforria --version to verify it.
Build from source
Requirements:
- a stable Rust toolchain with Cargo;
- a C compiler and
pkg-config; - OpenSSL development headers for your target;
- git;
- a POSIX shell for the
bashtool.
Clone and install the CLI crate:
git clone https://github.com/alforria-ai/alforria
cd alforria
cargo install --path crates/alforria
Or let Cargo fetch and build the repository directly:
cargo install --git https://github.com/alforria-ai/alforria --bin alforria
Cargo installs the binary to ~/.cargo/bin by default. Make sure that
directory is on PATH.
On Windows, use the MSVC Rust toolchain and a matching Visual Studio Build Tools installation. On Linux, the package names for the C toolchain and OpenSSL headers vary by distribution.
Verify the install
alforria --version
alforria --help
alforria --help lists the command surface. If the binary starts but the model
list is empty, continue with the quickstart to connect a
provider.
Upgrade
There is no package manager integration yet. Re-run the installer, download a
newer release binary, or run cargo install again. Your sessions and
credentials live outside the binary and are kept across upgrades.
To see where alforria stores its data, configuration, cache, and state:
alforria debug paths
Uninstall
Remove the binary from the directory where you installed it. If you also want
to remove sessions and credentials, delete the data and config directories
reported by alforria debug paths. Back up anything you want to keep first.