P2P host monitoring without opening ports or maintaining a VPN. The recommended path is the interactive install.sh script. It detects OS and arch, installs a Linux systemd agent and/or a desktop client, and pulls artifacts from the rolling release.
Interactive by default. Asks server vs client (or both).
Server path is Linux-only for systemd; client works on Linux and macOS.
Windows: download a .tar.gz from the rolling release.
curl -fsSL https://install.peardata.rest | bash
# Non-interactive
curl -fsSL https://install.peardata.rest | bash -s -- --server --yes
curl -fsSL https://install.peardata.rest | bash -s -- --client --yes
curl -fsSL https://install.peardata.rest | bash -s -- --both --yes
| Flag / env | Meaning |
|---|---|
--server / -s | Install peardata-server (Linux → /opt/peardata + systemd) |
--client / -c | Install desktop client |
--both / -b | Install both |
--yes / -y | Non-interactive defaults |
--tag rolling | Release tag (default: rolling) |
PEARDATA_SERVER_DIR | Server install path (default /opt/peardata) |
PEARDATA_VERSION | Pin asset version (default: auto from release) |
peardata-server-VERSION-linux-ARCH.tar.gz from the rolling release/opt/peardata/peardata-serverpeardata; adds it to systemd-journal (Logs tab) and, when Docker is detected, the docker group for optional container metrics/etc/systemd/system/peardata.service and optionally enables it/opt/peardata/.env (mode 600). Check this file after first start for your keys.sudo systemctl status peardata
sudo journalctl -u peardata -f
# After first start, keys are in .env (preferred)
sudo grep -E '^(SERVER_PUBLIC_KEY|SERVER_SEED)=' /opt/peardata/.env
# SERVER_PUBLIC_KEY → share for viewer / paste in client
# SERVER_SEED → admin only (never give to operators)
# Operators → Access → Create invite → share full pd1. string
peardata-client-VERSION-HOST.tar.gzpeardata.app under ~/Applications (clears quarantine via xattr)~/.local/share/peardata, symlink in ~/.local/bin, desktop entrypd1. invite (operator)For binary downloads by platform, checksums, and release notes, see Releases. Source builds and production ops are in Quick start and Operator guide.