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