The CLI installers below target Linux. On Windows and macOS, most people use the Desktop Agent, which bundles hookdeployed. Raw binaries for Linux, macOS, and Windows are also published on GitHub Releases for advanced or scripted setups.
Generate a one-time enrollment token from the Linux / CLI flow on the Agents page in the dashboard, then pick an install method.
Adds the HookDeploy APT repository and installs the hookdeployed package:
curl -fsSL https://apt.hookdeploy.dev/install.sh | sudo bash -s -- --token hd_enroll_...Downloads a release tarball, installs the binary, and sets up a systemd unit:
curl -fsSL https://raw.githubusercontent.com/hookdeploy/hookdeployed/main/install.sh | sudo bash -s -- --token hd_enroll_...Replace hd_enroll_... with the token from the dashboard (shown once).
Non-interactive token
Both installers accept the token as --token or as the environment variable HOOKDEPLOYED_TOKEN:
sudo HOOKDEPLOYED_TOKEN=hd_enroll_... bash install.sh
With a token, install + enroll + start can complete unattended (suitable for servers and provisioning scripts). Without a token, the package/binary is installed and you enroll afterward — typically with the device-code flow (hookdeployed enroll), which needs a real terminal.
After install
Confirm the service is running (systemd installs):
sudo systemctl status hookdeployed
Useful next steps: CLI reference, Using taps, Production vs Development.