Transparency alternatives to UpGuard
Other Compliance automation vendors we measure, sorted by how much we found at them and not at UpGuard. This is a comparison of disclosure, not of features or fitness.
12 shown of 59 that differ from UpGuard on at least one criterion we measured for both. Public transparency score, not a product or security rating.
UpGuard has 7 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “Found there, not found at UpGuard” is the one that closes them.
| Vendor | Score | Found there, not found at UpGuard | Found at UpGuard, not found there | |
|---|---|---|---|---|
| Secureframesecureframe.comSee also Transparency alternatives to Secureframe | 83/100 | 5 Data processing agreement, Subprocessor list, Data location stated, +2 | 1 security.txt (RFC 9116) | Compare |
| Keelkeelgrc.comSee also Transparency alternatives to Keel | 78/100 | 4 Data processing agreement, Subprocessor list, Data location stated, +1 | nothing | Compare |
| LogicGatelogicgate.comSee also Transparency alternatives to LogicGate | 68/100 | 4 Data processing agreement, Subprocessor list, Data location stated, +1 | 1 Public pricing | Compare |
| Vantavanta.comSee also Transparency alternatives to Vanta | 57/100 | 4 Data processing agreement, Status page with history, Uptime SLA with a figure, +1 | 1 Public pricing | Compare |
| Whisticwhistic.comSee also Transparency alternatives to Whistic | 57/100 | 4 Subprocessor list, Data location stated, Uptime SLA with a figure, +1 | 2 Public pricing, Named privacy contact | Compare |
| Hyperproofhyperproof.ioSee also Transparency alternatives to Hyperproof | 48/100 | 2 Subprocessor list, Data location stated | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Certacerta.aiSee also Transparency alternatives to Certa | 43/100 | 2 Subprocessor list, Data location stated | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Trusterotrustero.comSee also Transparency alternatives to Trustero | 35/100 | 2 Data location stated, Status page with history | 3 Public pricing, Certifications named, security.txt (RFC 9116) | Compare |
| Kertoskertos.ioSee also Transparency alternatives to Kertos | 30/100 | 2 Subprocessor list, Notice before subprocessors change | 4 Public pricing, Certifications named, security.txt (RFC 9116), +1 | Compare |
| Riskonnectriskonnect.comSee also Transparency alternatives to Riskonnect | 30/100 | 2 Data location stated, Uptime SLA with a figure | 3 Public pricing, security.txt (RFC 9116), Named privacy contact | Compare |
| ProcessUnityprocessunity.comSee also Transparency alternatives to ProcessUnity | 39/100 | 1 Data location stated | 1 security.txt (RFC 9116) | Compare |
| Akitraakitra.comSee also Transparency alternatives to Akitra | 30/100 | 1 Data processing agreement | 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.