Find release information and plan an upgrade

The current public download set provides Orchestris Chat 0.4.18 build 40. Orchestris Server Community Edition uses Windows 0.8.15 and macOS, Linux, and container 0.8.14 because 0.8.15 is a Windows-only installer hotfix. Product and platform versions can advance independently; install the release shown for your platform on Downloads instead of trying to match the numbers.

• Community Edition can initialize and run without a commercial license. The guided setup creates the first organization administrator and preserves supported existing installations during upgrade.
• The launch packages include signed Windows installers, signed and notarized macOS packages, SHA-256 checksums, and detached GPG signatures for Linux packages.
• Community Edition 0.8.14 adds host-authorized organization-administrator recovery, organization-scoped first-administrator setup, managed-HTTPS hosted-web validation, and hardened lifecycle and recovery behavior across native packages and Docker.
• The Windows-only 0.8.15 hotfix preserves existing Start-at-login registry entries without expanding the application directory before the installer initializes it. It contains no database, configuration, or client changes.
• Chat 0.4.18 build 40 is the current signed desktop release for Windows, macOS, and Linux. It restores reliable Community Edition re-login on virtualized and lower-powered Windows hosts by correcting token-expiry allowances and login transport timing.

• The macOS Server package requires Apple Silicon and macOS 13.5 or newer. The Chat package supports Apple Silicon on macOS 11 or newer. Intel macOS packages are not published in this release.
• Windows packages target x64 on Windows 10 or newer. Windows Arm packages are not published in this release.
• Linux Chat packages require glibc 2.35 or newer. Use the DEB package for Ubuntu/Debian-family systems and the RPM package for supported RPM-family systems.
• The Docker image requires a one-time local-init step and a persistent data volume before normal startup. Follow the Docker guide; the short image reference alone is not a complete installation.
• Back up configuration, secrets, and data before upgrading. Do not run an older Server against data already migrated by a newer release; restore the matching pre-upgrade backup instead.

This page records the current public launch release. Use Downloads as the authority for the versions and packages offered now; older private release candidates are not supported public downloads.

1. 1

   Open Downloads and choose the product

   Find Orchestris Chat or Community Edition, then select the platform and architecture you actually run.

2. 2

   Compare the offered version with your installed version

   Do not assume a package is newer because its link changed. Compare the displayed product name and version directly.

3. 3

   Open the release-notes link when it is shown

   Read customer-visible changes, known issues, compatibility limits, and required configuration or migration actions before downloading the package.

4. 4

   Use the artifact details on Downloads

   Download only the package currently shown for your platform. Verify its displayed SHA-256 value and use the detached signature, checksum file, or public key when those links are available.

• Open DownloadsSee the versions, packages, release-note links, and integrity details currently available.
• Ask about a missing or private releaseContact Support when no release-notes link is shown or your build was supplied privately.

1. 1

   Confirm the exact source and target

   Write down the product, installed version, target version, platform, architecture, and deployment method. Keep Chat and Server versions separate.

2. 2

   Read required actions and known issues

   Resolve any configuration, data-migration, compatibility, or maintenance-window requirement before replacing a running version.

3. 3

   Protect recoverability

   Follow the matching installation guide's backup and recovery procedure. Verify that the backup includes the data and secrets required by that deployment.

4. 4

   Plan the interruption and rollback

   Stop or restart the service only as directed by the platform guide. Keep the previous version and verified backup available until the new version passes its checks.

5. 5

   Return to the live download

   Use the package URL currently shown on /download instead of a cached artifact link or an old screenshot.

• Confirm the installed product reports the target version.
• For a Server deployment, check /health and the normal service or container logs.
• Sign in with the expected organization and confirm the intended models are visible.
• Send one minimal Chat message or Agent API request appropriate to the deployment.
• Keep the backup and previous package until normal operation is confirmed.