Skip to content

Documentation

Hosts and the agent

What the agent collects, how it enrolls, and why it cannot read your database.

What it collects

CPU, memory, swap, disk, network, system load, temperature, per-device disk I/O, per-interface traffic, GPU, battery and drive health. A single binary compiled with Native AOT — there is no runtime to install on the monitored machine.

Enrollment

  1. 01In the console, under Hosts, generate a one-time enrollment token — or a package, whose token is reusable and already sets the group and collector profile.
  2. 02Install the agent on the machine and run enrollment with the token.
  3. 03The token is exchanged for a long-lived key, stored hashed on the server and in plaintext only in the local config file, with restricted permissions.
  4. 04The agent starts pushing samples at the configured interval.

Why it cannot read your database

Because there is no path for it. The agent is push-only: it opens no port, accepts no remote command, and holds no database credential at all. Every batch is authenticated with the agent key and signed with HMAC-SHA256 over the body and timestamp, which stops a captured batch from being replayed.

It updates itself: a few times a day it reads the manifest from the same channel it was installed from, and if a newer version is published it downloads that build from the immutable per-version directory, verifies the SHA-256 the manifest declares, runs the staged binary once to make it state its own version, and only then swaps it in.

Platforms

  • Windows — x86-64 and ARM64
  • Linux — x86-64 and ARM64

There is no macOS build. When there is, it appears on the download page.