Downloads | Cade Runtime

Cade ships as a single self-contained binary, packaged as an archive for Linux and Windows, or as a native package on Linux. Pick the download for your platform, install it, and you are ready to write your first table.

Loading the current release…

Downloads need JavaScript to look up the current release. You can fetch the manifest directly from https://dl.cade.run/latest.json — it lists every binary with its URL and SHA-256.

Install it

Archives (Linux, Windows)

Each archive contains the cade binary plus LICENSE, README.md, and an example config. Extract it and move the binary onto your PATH:

tar -xzf cade_0.1.0_linux_amd64.tar.gz
sudo mv cade /usr/local/bin/cade
cade --version

On Windows, extract the .zip (Explorer’s “Extract All”, or Expand-Archive in PowerShell) and put the directory containing cade.exe on your PATH:

Expand-Archive cade_0.1.0_windows_amd64.zip
cade.exe --version

Linux packages (deb, rpm, apk)

Prefer a native package? Install it with your distribution’s package manager, which also pulls in the ALSA dependency cade needs:

sudo apt install ./cade_0.1.0_linux_amd64.deb   # Debian, Ubuntu
sudo rpm -i cade_0.1.0_linux_amd64.rpm          # Fedora, RHEL
sudo apk add --allow-untrusted cade_0.1.0_linux_amd64.apk  # Alpine

Packages install cade to /usr/bin/cade, already on PATH.

Verify the download

Every release publishes a SHA256SUMS file alongside the binaries. Checking against it confirms you got the bytes we published:

curl -O https://dl.cade.run/v0.1.0/SHA256SUMS
sha256sum --check --ignore-missing SHA256SUMS

Replace v0.1.0 with the version shown in the table above. --ignore-missing lets you verify just the one file you downloaded rather than every artifact.

Which build do I want?

If you are on	Use
Most Linux desktops and servers	`cade_<version>_linux_amd64.tar.gz`, or the `.deb`/`.rpm`/`.apk` package
Raspberry Pi 4/5, ARM servers	`cade_<version>_linux_arm64.tar.gz`, or the arm64 package
Windows 10/11	`cade_<version>_windows_amd64.zip`

There are no prebuilt macOS binaries yet: the audio engine needs Apple’s CoreAudio toolchain, which the release builders don’t carry. On a Mac, clone the repository and run task build to produce a native binary.

On Windows, running cade under WSL gives the best console experience — the TUI is built for a terminal with full ANSI support.

Older releases

Every tagged release stays available at a versioned URL:

https://dl.cade.run/<version>/<file>

For example, https://dl.cade.run/v0.1.0/cade_0.1.0_linux_amd64.tar.gz. The release notes list what shipped in each version.