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