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