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