Transparency alternatives to Automox
Other Endpoint management and security vendors we measure, sorted by how much we found at them and not at Automox. This is a comparison of disclosure, not of features or fitness.
12 shown of 37 that differ from Automox on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Automox has 6 gaps in what we could measure: Subprocessor list, Data location stated, Status page with history, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “Found there, not found at Automox” is the one that closes them.
| Vendor | Score | Found there, not found at Automox | Found at Automox, not found there | |
|---|---|---|---|---|
| Malwarebytesmalwarebytes.comSee also Transparency alternatives to Malwarebytes | 83/100 | 5 Subprocessor list, Data location stated, Status page with history, +2 | 2 Certifications named, Uptime SLA with a figure | Compare |
| Addigyaddigy.comSee also Transparency alternatives to Addigy | 87/100 | 4 Subprocessor list, Data location stated, Status page with history, +1 | nothing | Compare |
| Levellevel.ioSee also Transparency alternatives to Level | 61/100 | 4 Subprocessor list, Data location stated, security.txt (RFC 9116), +1 | 3 Data processing agreement, Uptime SLA with a figure, Named privacy contact | Compare |
| NinjaOneninjaone.comSee also Transparency alternatives to NinjaOne | 52/100 | 3 Data location stated, Status page with history, security.txt (RFC 9116) | 2 Data processing agreement, Uptime SLA with a figure | Compare |
| SentinelOnesentinelone.comSee also Transparency alternatives to SentinelOne | 48/100 | 3 Status page with history, security.txt (RFC 9116), Notice before subprocessors change | 2 Data processing agreement, Uptime SLA with a figure | Compare |
| Kaseyakaseya.comSee also Transparency alternatives to Kaseya | 39/100 | 3 Subprocessor list, Status page with history, Notice before subprocessors change | 5 Data processing agreement, Public pricing, Certifications named, +2 | Compare |
| Hexnodehexnode.comSee also Transparency alternatives to Hexnode | 62/100 | 2 Subprocessor list, Notice before subprocessors change | 2 Certifications named, Uptime SLA with a figure | Compare |
| Esperesper.ioSee also Transparency alternatives to Esper | 52/100 | 2 Data location stated, Notice before subprocessors change | 2 Uptime SLA with a figure, HTTPS enforced with HSTS | Compare |
| Action1action1.comSee also Transparency alternatives to Action1 | 48/100 | 2 security.txt (RFC 9116), Notice before subprocessors change | 2 Uptime SLA with a figure, Named privacy contact | Compare |
| Scalefusionscalefusion.comSee also Transparency alternatives to Scalefusion | 43/100 | 2 Data location stated, security.txt (RFC 9116) | 2 Data processing agreement, Uptime SLA with a figure | Compare |
| PDQ Connectpdq.comSee also Transparency alternatives to PDQ Connect | 30/100 | 2 Status page with history, security.txt (RFC 9116) | 3 Data processing agreement, Uptime SLA with a figure, HTTPS enforced with HSTS | Compare |
| ESETeset.comSee also Transparency alternatives to ESET | 26/100 | 2 Status page with history, security.txt (RFC 9116) | 4 Data processing agreement, Public pricing, Uptime SLA with a figure, +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.