01. Deploy the monitor
Download the archive for the machine that will host the monitor from GitHub Releases. Extract it: the executable and out directory must stay together. Choose a persistent data directory.
Pulse Monitor — GitHub Releases ↗Linux
./pulse-monitor -addr 127.0.0.1:8080 -data ./data -static ./outWindows / PowerShell
.\pulse-monitor.exe -addr 127.0.0.1:8080 -data .\data -static .\outOpen the monitor in your browser and register the owner account. For remote access, put it behind an HTTPS reverse proxy and configure the firewall. Do not expose an unencrypted login page to the Internet.
02. Connect your agents
Add a node in the Servers section. The monitor issues a node token and an agent command. Download the agent release for that node’s operating system and architecture, then use the generated command.
Pulse Agent — GitHub Releases ↗The agent needs your monitor URL and the token of its own node. Keep tokens private. Operating-system detection happens automatically.
03. Open your dashboard
Check that the node is online and telemetry arrives. Configure the monitor and agent as services so they start after a reboot. Back up the monitor data directory and keep the agent token safe.
Platform support
Linux amd64 · Linux arm64 · Windows amd64
GPU metrics require a supported GPU and drivers. Optional packet capture requires TShark and suitable privileges; network interface and connection monitoring works independently.
Read the documentation ↗