Appearance
Install Partner on Linux
Partner ships for Linux as a Debian/Ubuntu .deb, a Fedora/RHEL .rpm, and a portable AppImage. Each is a single, self-contained download — the Partner binary is statically built, so there are no extra packages or libraries to install.
The
.deb/.rpmregister Partner as a managedsystemdservice that starts at boot. The AppImage is a portable single file that does not register a managed service — use it for a quick try, and the.deb/.rpmfor a permanent install.
Option A — Debian / Ubuntu (.deb)
Download
Partner_<version>_amd64.deb.Install it:
bashsudo dpkg -i Partner_*_amd64.debThe installer registers and starts the
partnerdservice automatically. Confirm it is running:bashsystemctl status partnerdYou should see
active (running), enabled to start at boot.
Option B — Fedora / RHEL (.rpm)
bash
sudo rpm -i Partner_<version>.x86_64.rpm
systemctl status partnerdOption C — Portable AppImage
Download
Partner-<version>.AppImage.Make it executable and run it:
bashchmod +x Partner-*.AppImage ./Partner-*.AppImage statusThe AppImage front-ends the same Partner commands. Because it does not install a managed service, it will not auto-start at boot — keep the terminal open or use the
.deb/.rpmfor an always-on host.
Verify it is self-contained
The Partner binary is statically linked. You can confirm there are no external library dependencies:
bash
ldd $(command -v partnerd)
# expected: "not a dynamic executable" (or only linux-vdso)Check your connection details
Once the service is running, view your machine ID and current connection code:
bash
partnerd statusThis prints a stable machine ID and a short-lived connection code. That is everything someone needs to reach this machine — head to Getting started next.
Where things live
| Item | Location |
|---|---|
| Service unit | systemd unit named partnerd |
| Logs | journalctl -u partnerd |
To remove Partner later, see Uninstall.