The central server is for self-hosting. Remotes are installed on every machine you want to monitor - needed for both hosted and self-hosted users.
Only needed if you're self-hosting. Hosted (cloud) customers can skip this section and jump straight to Remotes.
MSI installer. Installs the RedNetMonitorServer service. Data lives under ProgramData\RedNetMonitor.
3fb054c81caa41394c0b91a0b44ed2cc9fa7d566f2ca20938defe0627d58922a
systemd service (red-net-monitor.service). Data under /var/lib/red_net_monitor.
Windows Server 2019+ (a Linux server build is coming soon). 2 vCPU / 2 GB RAM minimum. Supports SQLite (default), PostgreSQL, MySQL and SQL Server.
Required for both hosted and self-hosted. Lightweight: only outbound HTTPS to the central server.
Installs the RedNetMonitorRemote service. Logs via Event Viewer.
a7097578932c3ea226cb4f234a5397408b9d6a2ba915bcaa132635135c9a0dd5
Installs red-net-monitor-remote.service. Logs via journalctl.
Compute the SHA-256 of the file you downloaded and compare it to the value shown on its download above (or in the SHA256SUMS file). They must match exactly - case doesn't matter. If they differ, do not run the file.
In PowerShell, from the folder you downloaded into (replace FILENAME with the file you got):
No PowerShell? In any Command Prompt: certutil -hashfile FILENAME SHA256
In a terminal, from the folder you downloaded into (replace FILENAME with the file you got):
On macOS use shasum -a 256 FILENAME (there's no sha256sum by default).