Download & Install

Download the package for your platform from the releases page.

Each release ships these assets:

• Arch Linux: system-bridge-*-x86_64.pkg.tar.zst (stable releases only)
• Debian / Ubuntu: system-bridge_<version>_<arch>.deb
• Fedora / RHEL: system-bridge-<version>.<arch>.rpm
• Flatpak: system-bridge-<version>.flatpak
• Windows: system-bridge-<version>-setup.exe

Note

Stable builds are attached to the releases page. Development builds from the latest dev branch are also available as workflow artifacts on the GitHub Actions runs, which require a GitHub account to download.

Linux

Install the package that matches your distribution’s package manager.

Arch Linux

Install from the AUR with an AUR helper such as yay.

For the latest stable release, use the system-bridge package:

yay -S system-bridge

For the development branch, use the system-bridge-git package. This builds and installs the application from the latest dev branch, which is updated automatically every commit:

yay -S system-bridge-git

Alternatively, install the .pkg.tar.zst from the releases page or downloaded workflow asset directly:

sudo pacman -U system-bridge-*-x86_64.pkg.tar.zst

Debian / Ubuntu

Install the .deb asset with apt so dependencies are resolved automatically:

sudo apt install ./system-bridge_<version>_<arch>.deb

You can also install it with dpkg:

sudo dpkg -i system-bridge_<version>_<arch>.deb

Fedora / RHEL

Install the .rpm asset with dnf:

sudo dnf install ./system-bridge-<version>.<arch>.rpm

Flatpak

Install the .flatpak bundle:

flatpak install system-bridge-<version>.flatpak

Then run it with:

flatpak run dev.timmo.system-bridge

Windows

Run the system-bridge-<version>-setup.exe installer to install the application. After installation completes, you can start System Bridge from the Start Menu shortcut.

macOS

macOS is not officially supported and has no prebuilt packages. You can still build it from source and test it for yourself.

See Developing for the full build, run, and test workflow from source.

Note

Please do not submit feedback or bug reports for macOS, as it is not supported. Contributions are welcome if you would like to help improve macOS support.

Optional dependencies

System Bridge reads most hardware metrics directly from the kernel, so these tools aren’t required. On Linux, installing them improves detection on some systems:

Package	Tool	What it adds
lm_sensors (Arch, Fedora), lm-sensors (Debian / Ubuntu)	sensors	The full set of temperature and fan sensors on some boards. Run sudo sensors-detect once to load the relevant modules.
nvidia-utils	nvidia-smi	NVIDIA GPU metrics. Intel and AMD GPUs use the kernel drm/hwmon interfaces and need nothing extra.
pciutils	lspci	Friendly GPU model names. GPUs are still detected without it, but fall back to a generic name.
pipewire (Arch), pipewire-bin (Debian / Ubuntu), pipewire-utils (Fedora)	pw-dump	Names the apps using the microphone or camera. Without it, microphone usage falls back to ALSA, which names the sound server instead of the app.
zenity	zenity	The confirmation before Quit or Hide system tray. Without it, those actions can’t be confirmed, so they don’t run.

The .deb and .rpm packages recommend pciutils, PipeWire and zenity, so apt and dnf install them by default. The Arch package lists all of these as optional dependencies, which pacman shows but doesn’t install.

Windows needs no optional tools.

Next steps

• Start System Bridge: see Running.
• Monitor and control your system from the web client.
• Explore the CLI and get your token.
• Connect it to Home Assistant.