Software Downloads

Last validated: 2026-05-05

The canonical Oden download site is releases.voysys.dev. Use it to download stable releases, nightly builds, installers, and package checksums.

For step-by-step installation instructions, see Install Oden.

Release Channels

Channel Use Where

Latest

The newest stable Oden release on the releases index. Choose this for new installations and upgrades unless a project requires a specific version.

Latest Release

Stable

A numbered release such as 2.48.1. Stable releases are listed by version and include product installers, .sha256 checksum files, and release notes. Use the same stable version on every Oden machine in a deployment.

Older Versions on the releases index

Nightly

A date-based build such as 2026-05-04. Nightlies may contain unstable features and should be used for testing, validation, or when Voysys has directed you to use a specific build. Nightly pages do not include generated release changelog sections.

Nightly Builds

The releases index is generated from the release bucket and shows versions from 2.15 onward. The latest stable release is the highest numbered version shown in the Latest Release card. Older stable releases remain available from the same index when you need to match an existing deployment, reproduce a previous setup, or roll back.

Products

Each stable or nightly version page groups downloads by product:

  • Oden Fleet Streamer

  • Oden Streamer

  • OdenVR

  • Oden Dome Player

Only products built for the selected platform are shown as installable on that version page. If a product is not available for a platform, use another platform package or choose a version that includes the package you need.

Platform Packages

Platform Package type Filename pattern

Windows x64

MSI installer

OdenVR_<version>.msi, OdenStreamer_<version>.msi, OdenFleetStreamer_<version>.msi, OdenDomePlayer_<version>.msi

Ubuntu x64

Debian package

oden-vr_<version>_amd64.deb, oden-streamer_<version>_amd64.deb, oden-fleet-streamer_<version>_amd64.deb, oden-dome-player_<version>_amd64.deb

NVIDIA Jetson arm64

Debian package tied to Ubuntu and JetPack

oden-streamer_<version>_arm64_<ubuntu>_jetpack_<jetpack>.deb, oden-fleet-streamer_<version>_arm64_<ubuntu>_jetpack_<jetpack>.deb, oden-vr_<version>_arm64_<ubuntu>_jetpack_<jetpack>.deb

Flatpak

Flatpak package where present

oden-vr_<version>_amd64.flatpak

For Jetson, choose the package that matches the device’s JetPack version. Current release pages map JetPack package labels such as 4.6, 5.1, 6.1, and 7.1 to the corresponding arm64 package filenames when those builds are available. Do not install a package built for a different JetPack version.

Checksums

Every generated package link has a matching SHA link that points to <package>.sha256. Download the checksum file with the package when you need to verify the download before installing.

Verify a downloaded Linux package
sha256sum -c oden-vr_<version>_amd64.deb.sha256

The Linux install script also downloads the matching .sha256 file and verifies it with sha256sum -c before installing.

Linux Install Script

For Ubuntu and Jetson systems, the releases site publishes install.sh. The script installs the latest stable release for one of these roles:

  • fleet-streamer

  • streamer

  • vr

Choose a product interactively
curl -fsSL https://releases.voysys.dev/install.sh | sh
Pass the product role explicitly
curl -fsSL https://releases.voysys.dev/install.sh | sh -s -- fleet-streamer
curl -fsSL https://releases.voysys.dev/install.sh | sh -s -- streamer
curl -fsSL https://releases.voysys.dev/install.sh | sh -s -- vr

The script detects Linux, requires Ubuntu, detects x86_64 or arm64, selects the matching .deb, downloads the package and .sha256 file, verifies the checksum, and installs with sudo DEBIAN_FRONTEND=noninteractive apt-get install -y. It does not install Oden Dome Player; install that product from the downloaded .deb package.

Old Versions

Older stable versions are listed below the Latest Release card on releases.voysys.dev. Use an old version when you need to keep all machines in an existing deployment on the same release, reproduce a previous project, or follow Voysys support guidance.

When installing an old version manually, open that version page, download the package for every machine, and keep all machines on the same version. Do not mix latest, older stable, and nightly packages in the same deployment unless Voysys has told you to do so.

Nightly Builds

Nightly builds are Oden packages produced by the scheduled CI release build. Use a nightly only when you need to test a fix before the next stable release, validate a customer setup with Voysys, or install a specific build that Voysys has requested.

Nightly builds may contain unstable features and changes that have not been validated as a stable release. Use a stable release for normal installations unless Voysys has directed you to use a nightly.

Download nightlies from releases.voysys.dev/nightly/.

Nightly pages use a date-based public build identifier. For example, a nightly shown as 2026-05-04 on the download site uses 20260504 in package filenames and URLs. The nightly index lists the 30 most recent successfully deployed nightlies.

When choosing a nightly:

  1. Use the newest listed nightly when testing the latest changes.

  2. Use the exact date Voysys gave you when troubleshooting a known issue.

  3. Use the same nightly date on every Oden machine in the deployment.

  4. Choose the package that matches product, operating system, CPU architecture, and JetPack version.

Do not mix stable releases, older stable releases, and nightlies in the same deployment unless Voysys has told you to do so.

Nightly package examples:

Product Windows x64 Ubuntu x64 NVIDIA Jetson arm64

Oden Fleet Streamer

OdenFleetStreamer_<nightly>.msi

oden-fleet-streamer_<nightly>_amd64.deb

oden-fleet-streamer_<nightly>_arm64_<ubuntu>_jetpack_<jetpack>.deb

Oden Streamer

OdenStreamer_<nightly>.msi

oden-streamer_<nightly>_amd64.deb

oden-streamer_<nightly>_arm64_<ubuntu>_jetpack_<jetpack>.deb

OdenVR

OdenVR_<nightly>.msi

oden-vr_<nightly>_amd64.deb

oden-vr_<nightly>_arm64_<ubuntu>_jetpack_<jetpack>.deb

Oden Dome Player

OdenDomePlayer_<nightly>.msi

oden-dome-player_<nightly>_amd64.deb

Not built for Jetson

The public Linux install script installs the latest stable release. Install nightly packages manually after downloading the package and checksum from the nightly page.

Install a downloaded Ubuntu or Jetson nightly
sha256sum -c oden-streamer_20260504_amd64.deb.sha256
sudo apt-get install ./oden-streamer_20260504_amd64.deb

Nightly builds may report application version 0.0.0. When reporting a nightly issue, record the nightly page URL, package filename, product name, operating system, JetPack version if applicable, and Git hash from the About dialog.

Changelog and Version Notes

Stable version pages include a What’s New section generated from CHANGELOG.md. The full generated changelog is available at releases.voysys.dev/changelog. Nightly builds are listed separately and do not include stable-release changelog sections.

Stable Oden releases use numeric versions such as 2.48.1. Use the same stable version on all Oden machines in a deployment unless Voysys has directed you to mix versions.

Version form How to interpret it

2.48.1

A stable release version. The same number appears in release page URLs, package filenames, and the application version reported by Oden.

2.48.x

A major/minor release series. Oden’s compatibility warning compares major and minor numbers, so 2.48.0 and 2.48.1 are treated as the same series. Exact version matching is still the safest deployment practice.

0.0.0

A local, test, or nightly build version, not a published stable release version.

2026-05-04

A displayed nightly build date. Nightlies may include changes that are not yet represented in the stable changelog.

The historical release tag and staging prefix use OdenVR_ before the version, for example OdenVR_2.48.1. The public release site uses the bare version folder, for example https://releases.voysys.dev/2.48.1/.

When planning an upgrade:

  1. Open changelog and download pages.

  2. Read every changelog entry after the version currently installed and up to the target version.

  3. Check the target version’s download page for the products and platforms you need.

  4. Install matching package versions across Player, Streamer, Fleet Streamer, and Dome Player machines.