Alternatives to Nagios
Other Network monitoring vendors we measure, sorted by how much they publish that Nagios does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 21 that differ from Nagios on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Nagios has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “publishes and Nagios does not” is the one that closes them.
| Vendor | Score | Publishes, and Nagios does not | Nagios publishes, and they do not | |
|---|---|---|---|---|
| Kentikkentik.com | 65/100 | 5 Subprocessor list, Data location stated, Status page with history, +2 | nothing | Compare |
| Auvikauvik.com | 52/100 | 5 Subprocessor list, Data location stated, Status page with history, +2 | 1 Public pricing | Compare |
| LogicMonitorlogicmonitor.com | 52/100 | 5 Data processing agreement, Data location stated, Status page with history, +2 | 1 Named privacy contact | Compare |
| Paesslerpaessler.com | 43/100 | 4 Data location stated, Certifications named, HTTPS enforced with HSTS, +1 | nothing | Compare |
| Netgear Insightnetgear.com | 39/100 | 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 | 1 Public pricing | Compare |
| Cambiumcambiumnetworks.com | 26/100 | 3 Data location stated, Certifications named, security.txt (RFC 9116) | 1 Public pricing | Compare |
| Netskopenetskope.com | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Public pricing, Named privacy contact | Compare |
| Domotzdomotz.com | 22/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Public pricing, Named privacy contact | Compare |
| Catchpointcatchpoint.com | 26/100 | 2 Status page with history, Certifications named | nothing | Compare |
| Icingaicinga.com | 22/100 | 2 Data location stated, security.txt (RFC 9116) | 1 Public pricing | Compare |
| Nile Networksnilesecure.com | 22/100 | 2 Data location stated, Status page with history | 2 Public pricing, Named privacy contact | Compare |
| Zyxel Nebulazyxel.com | 17/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 1 Public pricing | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.