Relayium

Releases

Last updated: 2026-10-22

Relayium ships in four rhythms, and this page is honest about all four: the web app is deployed continuously, the command-line tools are numbered and tagged, the macOS app is released on its own — macOS 1.5.0 is a signed download from GitHub, and the Mac App Store carries it on a version line of its own — and the Android app is a direct-APK preview released under android-v0.3.3.

A new version is now tagged by hand from the main branch, and only after the checks on that exact commit have passed. A version's complete notes — every commit it contains — are one click away on GitHub.

Every published version

Newest first. Each version links to its full notes and downloads on GitHub.

What a version number covers

A version tag publishes two programs: the relayium command-line tool, and relayium-node, the relay and storage node that self-hosters run. Both are built from the same source tree, so a version exists only when that tree changed.

  • The web app has no version number. Verified commits are selected for production independently of the version tags below, so what you use in a browser does not correspond to any row here and is usually ahead of the newest one.
  • The macOS app is released under its own tag, macos-v1.5.0: a Developer ID-signed, Apple-notarized direct download from GitHub. The separately versioned Mac App Store release is currently 1.4.10. No version below ships that app.
  • A node does not follow this list by itself: it asks the server it belongs to which version to run, so a new version changes nothing until someone starts a rollout. The command-line tool updates with relayium update.
  • The Android app is released under its own tag, android-v0.3.3: a direct APK, distributed from GitHub with no Google Play listing. It is a public preview, it is versioned independently of everything else on this page, and no version below ships it.

How a release is cut

A maintainer cuts a release by tagging a commit on the main branch, and does so only when the code that actually gets published — the command-line tool or the node — has changed since the last version, and only after every check on that exact commit has passed. The tag then builds and publishes the archives, the checksum file and its signature, and the GitHub release names its source commit and lists every commit since the previous version.

  • The checks come first because tagging an unverified commit would ship exactly the breakage they exist to catch.
  • Changes that touch only documentation or the apps produce no version, because the published programs would be byte-for-byte the previous ones.

Checking what you downloaded

Every command-line release publishes a checksum file next to the archives, and a signature over that file. relayium update verifies both before it installs anything, against a public key compiled into the program — so a tampered archive fails on your machine, rather than depending on whether we noticed on ours.

  • For networks that cannot reach GitHub, Relayium also mirrors its own release files. Where the bytes come from is a question of reachability, not of trust: the verification is identical either way.
  • Android works differently, and this page will not pretend otherwise. The app checks for a newer version only when you ask it to, and then opens the download page in your browser — it never downloads or installs anything itself, so it cannot verify the file it points you at. What protects the install is Android's own rule that an update must carry the same signing certificate as the app it replaces. The SHA-256 is published beside the APK so you can check it by hand if you want to.
  • The source is public. The server, the node and the web app are AGPL-3.0, the native apps Apache-2.0, and the documentation CC BY 4.0.