Breeze Core v2.5.0 — all-in-one packages for (almost) everything

Breeze Core no longer requires Python on the target machine. Every release now ships self-contained builds — server, web UI, and a private runtime in one bundle — wrapped as native packages for 15+ distros, with the same ease of setup the Windows installer has had.

Install it your way

You run	Grab	Install
Debian, Ubuntu, Mint, Pop!_OS, Raspberry Pi OS, Armbian, Devuan	.deb (amd64/arm64)	sudo apt install ./breeze-core_*.deb
Fedora, RHEL, Alma, Rocky, openSUSE Leap/Tumbleweed, SLE	.rpm (x86_64/aarch64)	sudo dnf install ./breeze-core-*.rpm
Arch, Manjaro, Artix	.pkg.tar.zst	sudo pacman -U …
Alpine	.apk	sudo apk add --allow-untrusted …
Void, Gentoo, anything else	.tar.gz (glibc/musl × amd64/arm64)	unpack, sudo ./install.sh
NixOS / Nix	the repo is now a flake	services.breeze-core.enable = true; via the NixOS module
Windows	Breeze-Core-Setup.exe	double-click

Then: sudo breeze-core pair → set your LAN IP in /etc/breeze-core/breeze-core.env → sudo systemctl enable --now breeze-core. Full guide: docs/PACKAGES.md.

What's inside

• A breeze-core binary with serve / pair / version subcommands; glibc builds made on AlmaLinux 8 (run on anything ≥ RHEL 8 / Debian 11 / Ubuntu 20.04), musl builds for Alpine/Void.
• Hardened service out of the box: unprivileged breeze user, locked-down /etc/breeze-core, the same systemd sandbox as the source install (verified exposure score 3.0), OpenRC/runit variants included.
• Every package is install-tested in CI on 15 real distro userlands (incl. Mint, Devuan, SLE, Artix, Void-musl, Gentoo and an arm64 pass) before release.
• Hybrid extras for packagers: AUR-style source PKGBUILD, Gentoo -bin ebuild, Void xbps-src template (packaging/source/).
• FreeBSD/NetBSD/OpenWrt stay on the documented source install for now (native poudriere builds are planned).

The classic from-source install, Docker images (incl. x86-64-v2/v3), and everything from 2.4.x are unchanged. No API or wire-contract changes — a drop-in update.

Linux package assets are attached by CI (the Packages workflow) — if you're very early to this page, give it a few minutes.