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