Transparency alternatives to Admin By Request
Other Privileged access management vendors we measure, sorted by how much they publish that Admin By Request does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 41 that differ from Admin By Request on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Admin By Request has 6 gaps in what we could measure: Subprocessor list, Status page with history, Public pricing, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116). The column “publishes and Admin By Request does not” is the one that closes them.
| Vendor | Score | Publishes, and Admin By Request does not | Admin By Request publishes, and they do not | |
|---|---|---|---|---|
| Infisicalinfisical.com | 48/100 | 4 Subprocessor list, Public pricing, Uptime SLA with a figure, +1 | 4 Data processing agreement, Data location stated, Certifications named, +1 | Compare |
| Dopplerdoppler.com | 83/100 | 3 Subprocessor list, Status page with history, Public pricing | nothing | Compare |
| Tailscaletailscale.com | 70/100 | 3 Public pricing, Uptime SLA with a figure, security.txt (RFC 9116) | nothing | Compare |
| Delineadelinea.com | 65/100 | 3 Subprocessor list, Status page with history, security.txt (RFC 9116) | 1 Data location stated | Compare |
| Twingatetwingate.com | 65/100 | 3 Subprocessor list, Status page with history, Public pricing | 2 Data location stated, Certifications named | Compare |
| C1c1.ai | 61/100 | 3 Subprocessor list, Uptime SLA with a figure, security.txt (RFC 9116) | 1 Data location stated | Compare |
| GitGuardiangitguardian.com | 52/100 | 3 Subprocessor list, Public pricing, security.txt (RFC 9116) | 3 Data location stated, Notice before subprocessors change, Named privacy contact | Compare |
| Devolutionsdevolutions.net | 48/100 | 3 Status page with history, Public pricing, security.txt (RFC 9116) | 3 Data processing agreement, Certifications named, Notice before subprocessors change | Compare |
| NordLayernordlayer.com | 48/100 | 3 Status page with history, Public pricing, security.txt (RFC 9116) | 3 Data location stated, Notice before subprocessors change, Named privacy contact | Compare |
| Netwrixnetwrix.com | 35/100 | 3 Status page with history, Public pricing, security.txt (RFC 9116) | 4 Data processing agreement, Data location stated, Notice before subprocessors change, +1 | Compare |
| Termius Vaulttermius.com | 35/100 | 3 Status page with history, Public pricing, security.txt (RFC 9116) | 4 Data processing agreement, Data location stated, Notice before subprocessors change, +1 | Compare |
| SailPointsailpoint.com | 61/100 | 2 Subprocessor list, Status page with history | 1 Data processing agreement | 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.