Stravia Docs

Install Stravia

Desktop installers and Server packages are different release assets. Select the one for the mode you chose; do not treat the Server executable as a Desktop installer or assume every operating system has every package.

Before you download

Choose Desktop or Server first. Then identify the operating system and CPU architecture of the computer that will run Stravia. A Server package is for the host, not necessarily the client computer.

Select a release asset

Use the GitHub Releases page and choose an asset whose name and architecture match your target:

  • Desktop release assets include Windows setup executables and Linux AppImages.
  • Server release assets include Windows ZIP archives and Linux GNU tar archives.
  • The public v0.3.1 release inspected on 2026-10-02 did not list macOS assets. Check the current release page rather than assuming availability from these observed names.

For example, the Windows x86_64 Server archive observed on that release was stravia-server-v0.3.1-windows-x86_64.zip. Use the current release's matching file rather than copying an old version number into an install script.

Verify the download

  1. Download the SHA256SUMS file published alongside the selected release asset.
  2. Calculate the downloaded file's SHA-256 using a trusted tool on your operating system.
  3. Compare the result with the exact asset entry in SHA256SUMS; stop if it does not match.

This verifies that the downloaded archive matches the published checksum. It does not independently attest to the source revision used to build the release.

Continue installation

  • For a Windows x86_64 Server archive, the Quick start shows a PowerShell extraction and loopback-only first launch using a new data directory.
  • For Docker, see Deploy with Docker ; the container image is a separate Server distribution path.
  • For Desktop, open the platform installer and continue with First setup .

Troubleshoot download or installation problems

If no asset matches, recheck the target operating system and CPU architecture against the current release page. If SHA-256 does not match, do not run the file; download it again and verify against that release's SHA256SUMS.

Next steps

After installing, use First setup for the correct Desktop or Server branch.