Transparency alternatives to Codeproof
Other Endpoint management and security vendors we measure, sorted by how much they publish that Codeproof does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 37 that differ from Codeproof on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Codeproof has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and Codeproof does not” is the one that closes them.
| Vendor | Score | Publishes, and Codeproof does not | Codeproof publishes, and they do not | |
|---|---|---|---|---|
| Addigyaddigy.com | 87/100 | 8 Data processing agreement, Subprocessor list, Data location stated, +5 | nothing | Compare |
| Malwarebytesmalwarebytes.com | 83/100 | 8 Data processing agreement, Subprocessor list, Data location stated, +5 | 1 Certifications named | Compare |
| Hexnodehexnode.com | 62/100 | 5 Data processing agreement, Subprocessor list, HTTPS enforced with HSTS, +2 | 1 Certifications named | Compare |
| NinjaOneninjaone.com | 52/100 | 5 Data location stated, Status page with history, HTTPS enforced with HSTS, +2 | nothing | Compare |
| SentinelOnesentinelone.com | 48/100 | 5 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116), +2 | nothing | Compare |
| Fleetfleetdm.com | 48/100 | 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 | nothing | Compare |
| Levellevel.io | 48/100 | 4 Subprocessor list, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | nothing | Compare |
| Automoxautomox.com | 43/100 | 4 Data processing agreement, Uptime SLA with a figure, HTTPS enforced with HSTS, +1 | nothing | Compare |
| Scalefusionscalefusion.com | 43/100 | 4 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | nothing | Compare |
| Kaseyakaseya.com | 39/100 | 4 Subprocessor list, Status page with history, HTTPS enforced with HSTS, +1 | 2 Public pricing, Certifications named | Compare |
| Jamfjamf.com | 35/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | nothing | Compare |
| Action1action1.com | 30/100 | 3 Data processing agreement, 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.