Choose a build, then verify it
The downloads page lists every published artifact with its exact version, size, publication date and SHA-256 checksum, and it shows the verification command for your platform. Check the checksum before you run an installer.
Two release channels exist. Stable is the signed, released line and is the right default. Beta brings new features earlier and may contain bugs.
What has actually been verified
No application build has been produced or run yet, and this site does not claim otherwise. The published blockers are specific: there is no Android SDK and no macOS host in the environment that builds this repository, so Android, iOS and macOS artifacts cannot be produced there, and release signing credentials are not provisioned.
Where credentials are missing, the pipeline marks artifacts unsigned-development and the release verification step fails the signing gate rather than passing it. That is why an artifact can be absent from the downloads page — the page disables the control and says why, instead of linking to a file that is not there.
Building it yourself
The toolchain is pinned to exact versions rather than ranges, and the manifest records why each non-latest choice was made. You need Node 20.11 or newer and pnpm 9 or newer for the clients; the backend additionally needs PHP 8.3 or newer and Composer.
From a clean checkout, install with pnpm at the repository root, then build the desktop, Android or iOS target with the corresponding script. Build instructions and the release procedure live in the repository, next to the code they describe.
Source documents
This page summarises the files below. Read them for the full, authoritative text.
README.md
Repository pathdocs/TOOLCHAIN.md
Repository pathdocs/runbooks/RELEASE.md
Repository pathdocs/execution/BLOCKERS.md
Repository path