Alternatives to Probely
Other Vulnerability management vendors we measure, sorted by how much they publish that Probely does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 32 that differ from Probely on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Probely has 7 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “publishes and Probely does not” is the one that closes them.
| Vendor | Score | Publishes, and Probely does not | Probely publishes, and they do not | |
|---|---|---|---|---|
| Invictiinvicti.com | 83/100 | 6 Data processing agreement, Subprocessor list, Data location stated, +3 | 1 Status page with history | Compare |
| Rapid7rapid7.com | 70/100 | 5 Data processing agreement, Subprocessor list, Uptime SLA with a figure, +2 | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Snyksnyk.io | 61/100 | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | nothing | Compare |
| Intruderintruder.io | 57/100 | 3 Data processing agreement, Data location stated, Notice before subprocessors change | 2 Status page with history, security.txt (RFC 9116) | Compare |
| Wizwiz.io | 57/100 | 3 Data processing agreement, Data location stated, Named privacy contact | 1 Public pricing | Compare |
| Holm Securityholmsecurity.com | 52/100 | 3 Subprocessor list, Data location stated, Named privacy contact | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Mendmend.io | 50/100 | 2 Data location stated, Named privacy contact | nothing | Compare |
| SonarSourcesonarsource.com | 48/100 | 2 Data processing agreement, Subprocessor list | 2 Status page with history, security.txt (RFC 9116) | Compare |
| Detectifydetectify.com | 43/100 | 2 Data processing agreement, Named privacy contact | 1 Status page with history | Compare |
| Veracodeveracode.com | 43/100 | 2 Subprocessor list, Notice before subprocessors change | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Acunetixacunetix.com | 39/100 | 2 Data location stated, Named privacy contact | 2 Status page with history, Certifications named | Compare |
| Aqua Securityaquasec.com | 39/100 | 2 Subprocessor list, Named privacy contact | 2 Public pricing, security.txt (RFC 9116) | 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.