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