The Hyperping agent runs on Linux with systemd, on macOS with launchd, and on Windows 10 / Windows Server 2016 and later. This page lists the systems we test the agent on, what each host needs, and what is not supported.
We tested agent 0.2.0, with the installer published on November 10, 2026, on the systems below. On each one we checked the install, the service, the metrics, a restart of the service, a reboot of the host, and the uninstall.
| Family | Versions tested | Notes |
|---|---|---|
| Ubuntu | 16.04, 18.04, 20.04, 22.04, 24.04, 26.04 | 24.04 tested on x86_64 and arm64. |
| Ubuntu Pro | 16.04, 20.04 | Both tested in a standard setup. 20.04 also tested with the FIPS kernel and with Canonical's CIS Level 1 hardening. |
| Debian | 9, 10, 11, 12, 13 | |
| RHEL family | CentOS 7, RHEL 7, Oracle Linux 7, Rocky Linux 8 and 9, AlmaLinux 8, Amazon Linux 2 and 2023, Fedora 44 | Tested with SELinux in enforcing mode. |
| SUSE | SUSE Linux Enterprise Server 12 SP5, 15 SP5 | |
| Windows | Windows Server 2016, 2019 | Windows 10, Windows Server 2016 and later are supported. On Server 2016, the command copied from the dashboard starts with a line that turns on TLS 1.2. See Windows. |
| macOS | Not part of this test campaign | Supported, runs as a launchd service. |
x86_64 (amd64) or arm64.sudo.curl or wget, and tar. The installer uses wget when curl is missing.api.hyperping.io and ingest.hyperping.io.To check which init system a host runs, print the name of PID 1. It should say systemd:
cat /proc/1/commamd64).amd64 (Intel) or arm64 (Apple silicon).sudo.virt-customize. systemd is not running there.On Linux without systemd, and inside a chroot, the installer stops before it installs or enrolls anything, and says why. For an image, run the install command at the first boot of each machine instead, for example from cloud-init or your first-boot script. Each machine then enrolls on its own.
The installer writes a systemd unit that restricts what the agent can do. It only writes the directives the host's systemd knows.
ProtectSystem=full) and its memory is capped at 512 MB.ProtectSystem=strict.On Linux the agent runs as the hyperping system user, without privileges, on every version.
pro enable fips).usg fix cis_level1_server).In these tests the agent used about 65 MB of memory and 0.1 to 0.2% of one CPU core.