Transparency alternatives to Paessler
Other Network monitoring vendors we measure, sorted by how much we found at them and not at Paessler. This is a comparison of disclosure, not of features or fitness.
12 shown of 35 that differ from Paessler on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Paessler has 6 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “Found there, not found at Paessler” is the one that closes them.
| Vendor | Score | Found there, not found at Paessler | Found at Paessler, not found there | |
|---|---|---|---|---|
| Kentikkentik.comSee also Transparency alternatives to Kentik | 70/100 | 4 Subprocessor list, Status page with history, Uptime SLA with a figure, +1 | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Auvikauvik.comSee also Transparency alternatives to Auvik | 52/100 | 3 Subprocessor list, Status page with history, Notice before subprocessors change | 3 Public pricing, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Zscalerzscaler.comSee also Transparency alternatives to Zscaler | 43/100 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | 5 Data location stated, Public pricing, Certifications named, +2 | Compare |
| LogicMonitorlogicmonitor.comSee also Transparency alternatives to LogicMonitor | 39/100 | 3 Data processing agreement, Status page with history, Uptime SLA with a figure | 4 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | Compare |
| Catchpointcatchpoint.comSee also Transparency alternatives to Catchpoint | 39/100 | 1 Status page with history | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| WatchGuardwatchguard.comSee also Transparency alternatives to WatchGuard | 39/100 | 1 Status page with history | 2 Public pricing, Certifications named | Compare |
| Ubiquitiui.comSee also Transparency alternatives to Ubiquiti | 35/100 | 1 Status page with history | 3 Public pricing, Certifications named, Named privacy contact | Compare |
| Netgear Insightnetgear.comSee also Transparency alternatives to Netgear Insight | 26/100 | 1 Status page with history | 3 Data location stated, Public pricing, Certifications named | Compare |
| Palo Alto Networkspaloaltonetworks.comSee also Transparency alternatives to Palo Alto Networks | 26/100 | 1 Status page with history | 3 Data location stated, Public pricing, security.txt (RFC 9116) | Compare |
| Domotzdomotz.comSee also Transparency alternatives to Domotz | 22/100 | 1 Status page with history | 4 Data location stated, Public pricing, Certifications named, +1 | Compare |
| Nile Networksnilesecure.comSee also Transparency alternatives to Nile Networks | 22/100 | 1 Status page with history | 5 Public pricing, Certifications named, HTTPS enforced with HSTS, +2 | Compare |
| TP-Link Omadatp-link.comSee also Transparency alternatives to TP-Link Omada | 22/100 | 1 No third-party tracking before consent | 4 Data location stated, Public pricing, Certifications named, +1 | 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.