Transparency alternatives to Lumos
Other Privileged access management vendors we measure, sorted by how much we found at them and not at Lumos. This is a comparison of disclosure, not of features or fitness.
12 shown of 40 that differ from Lumos on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Lumos has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “Found there, not found at Lumos” is the one that closes them.
| Vendor | Score | Found there, not found at Lumos | Found at Lumos, not found there | |
|---|---|---|---|---|
| Tailscaletailscale.comSee also Transparency alternatives to Tailscale | 70/100 | 6 Data processing agreement, Data location stated, Certifications named, +3 | 1 Status page with history | Compare |
| C1c1.aiSee also Transparency alternatives to C1 | 61/100 | 6 Data processing agreement, Subprocessor list, Certifications named, +3 | 1 Status page with history | Compare |
| Dopplerdoppler.comSee also Transparency alternatives to Doppler | 83/100 | 5 Data processing agreement, Subprocessor list, Data location stated, +2 | nothing | Compare |
| Delineadelinea.comSee also Transparency alternatives to Delinea | 65/100 | 5 Data processing agreement, Subprocessor list, Certifications named, +2 | nothing | Compare |
| Devolutionsdevolutions.netSee also Transparency alternatives to Devolutions | 70/100 | 4 Subprocessor list, Data location stated, security.txt (RFC 9116), +1 | nothing | Compare |
| SailPointsailpoint.comSee also Transparency alternatives to SailPoint | 61/100 | 4 Subprocessor list, Data location stated, Certifications named, +1 | nothing | Compare |
| GitGuardiangitguardian.comSee also Transparency alternatives to GitGuardian | 52/100 | 4 Data processing agreement, Subprocessor list, Certifications named, +1 | 2 Status page with history, Named privacy contact | Compare |
| StrongDMstrongdm.comSee also Transparency alternatives to StrongDM | 52/100 | 4 Data processing agreement, Certifications named, Uptime SLA with a figure, +1 | nothing | Compare |
| Infisicalinfisical.comSee also Transparency alternatives to Infisical | 48/100 | 4 Subprocessor list, Uptime SLA with a figure, security.txt (RFC 9116), +1 | 2 Status page with history, Named privacy contact | Compare |
| Akeylessakeyless.ioSee also Transparency alternatives to Akeyless | 43/100 | 4 Data processing agreement, Certifications named, Uptime SLA with a figure, +1 | 1 HTTPS enforced with HSTS | Compare |
| Twingatetwingate.comSee also Transparency alternatives to Twingate | 57/100 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | 1 HTTPS enforced with HSTS | Compare |
| NordLayernordlayer.comSee also Transparency alternatives to NordLayer | 48/100 | 3 Data processing agreement, Certifications named, security.txt (RFC 9116) | 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.