Transparency alternatives to PortSwigger
Other API security vendors we measure, sorted by how much they publish that PortSwigger does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 21 that differ from PortSwigger on at least one criterion we measured for both. Public transparency score, not a product or security rating.
PortSwigger has 8 gaps in what we could measure: Subprocessor list, Data location stated, Public pricing, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and PortSwigger does not” is the one that closes them.
| Vendor | Score | Publishes, and PortSwigger does not | PortSwigger publishes, and they do not | |
|---|---|---|---|---|
| Salt Securitysalt.security | 35/100 | 3 Subprocessor list, Notice before subprocessors change, Named privacy contact | 3 Data processing agreement, Status page with history, Certifications named | Compare |
| 42Crunch42crunch.com | 30/100 | 2 Public pricing, Named privacy contact | 2 Data processing agreement, Certifications named | Compare |
| Cequencecequence.ai | 30/100 | 2 Data location stated, Named privacy contact | 2 Data processing agreement, Status page with history | Compare |
| Pyntpynt.io | 30/100 | 2 Data location stated, Named privacy contact | 2 Data processing agreement, Status page with history | Compare |
| FireTailfiretail.ai | 26/100 | 2 Subprocessor list, Named privacy contact | 3 Data processing agreement, Status page with history, Certifications named | Compare |
| Traceabletraceable.ai | 35/100 | 1 Subprocessor list | 2 Certifications named, HTTPS enforced with HSTS | Compare |
| Beagle Securitybeaglesecurity.com | 22/100 | 1 Public pricing | 2 Data processing agreement, Status page with history | Compare |
| APIsecapisec.ai | 17/100 | 1 Public pricing | 3 Data processing agreement, Status page with history, Certifications named | Compare |
| Approovapproov.io | 13/100 | 1 Named privacy contact | 3 Data processing agreement, Status page with history, Certifications named | Compare |
| Data Theoremdatatheorem.com | 13/100 | 1 Named privacy contact | 3 Data processing agreement, Status page with history, Certifications named | Compare |
| Impart Securityimpart.ai | 13/100 | 1 Named privacy contact | 3 Data processing agreement, Status page with history, Certifications named | Compare |
| ZAPzaproxy.org | 13/100 | 1 security.txt (RFC 9116) | 3 Data processing agreement, Status page with history, Certifications named | 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.