Skip to content

Download livematrix

These links always point to the latest stable release. Use the installer unless you have a reason not to: it installs a service or an application, keeps your data across upgrades, and lets livematrix update itself.

Windows x64 Linux x86_64
Client — the app operators talk and listen with Installer (.msi) Package (.deb)
Server — runs livematrix for your production Installer (.msi) Package (.deb)
Bridge — connects sound cards and other intercoms Installer (.msi) Package (.deb)

Portable versions unpack into a folder and run from there without installing. They do not update themselves:

Windows x64 Linux x86_64
Client .zip .tar.gz
Server .zip .tar.gz
Bridge .zip .tar.gz

macOS builds are not published yet. The client also runs in any browser from your server’s address, and on iPhone, iPad and Android.

On Windows, the downloads are for 64-bit Windows and are tested on Windows 11.

On Linux, each one needs a recent enough C library (glibc). To see yours, run ldd --version.

Needs Runs on
Client glibc 2.38 or newer Ubuntu 24.04, Debian 13 and later
Server glibc 2.43 or newer Debian testing or unstable
Bridge glibc 2.43 or newer Debian testing or unstable

The Linux server and bridge do not start on Ubuntu 24.04 or Debian 13 yet: they stop with version `GLIBC_2.43' not found. Run them on Windows, or on Debian testing, until a build for older distributions is published.

On Linux the server and the bridge are headless: the packages install them as system services, with no tray icon, and they need nothing of a desktop. They use the machine’s sound cards through ALSA. Set them up from their web pages, or on the machine with sudo livematrix-server-ctl and sudo livematrix-bridge-ctl (--help lists what they do).

Every file is listed with its SHA-256 checksum in sha256sums. The installers are not code-signed yet, so the checksum is what tells you a file is the one we published. Windows SmartScreen warns about them; choose More info and Run anyway only for a file whose checksum matches.

On Linux, in the folder with your downloads:

Terminal window
curl -fsSLO https://console.livematrix.io/v1/downloads/latest/stable/sha256sums
sha256sum -c sha256sums --ignore-missing

On Windows, in PowerShell, compare the output with the file’s line in sha256sums:

Terminal window
Get-FileHash .\livematrix-server-windows-x64.msi -Algorithm SHA256
  • Windows: open the .msi. The server asks for its ports and whether to open them in the firewall.

  • Linux: install with apt, which also installs what the package needs:

    Terminal window
    sudo apt-get install ./livematrix-server_amd64.deb
    sudo apt-get install ./livematrix-bridge_amd64.deb

    Both start as services. The bridge’s page is on port 5678 of its machine.

Then open the server’s management page and follow First Setup.

The client, the server and the bridge check for a newer version on their own. When one is out, they download it in the background and ask before installing:

  • Server: a banner in the management page offers Install and restart. On Linux it links to the new package instead; install it with sudo apt-get install ./livematrix-server_amd64.deb as above. Users are disconnected for the few seconds the server takes to restart.
  • Bridge: the same banner in the bridge’s page. On Linux it shows the sudo apt-get install command for the new package, as the server’s does.
  • Client: a banner on the main screen offers Install and restart. Windows and Linux ask for an administrator’s password.

Each one follows a release channel: on the server’s Settings page, the bridge’s Setup page and the client’s Settings › Updates:

Channel What you get
Stable Releases only. The default.
Nightly A build of the latest development version, every night that something changed. For trying new features before they are released; expect rough edges.
Off No checks. Install new versions yourself from this page.

Moving from nightly back to stable takes effect with the next stable release that is newer than the nightly you run. To go back to an older version, uninstall and install it from this page; the server keeps a snapshot of its database from before every upgrade.