Transparency alternatives to Cerbos
Other Password and identity vendors we measure, sorted by how much they publish that Cerbos does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 34 that differ from Cerbos on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Cerbos has 8 gaps in what we could measure: Subprocessor list, Data location stated, Status page with history, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact. The column “publishes and Cerbos does not” is the one that closes them.
| Vendor | Score | Publishes, and Cerbos does not | Cerbos publishes, and they do not | |
|---|---|---|---|---|
| Keeperkeepersecurity.com | 74/100 | 5 Subprocessor list, Certifications named, No third-party tracking before consent, +2 | nothing | Compare |
| Ping Identitypingidentity.com | 61/100 | 5 Subprocessor list, Status page with history, Certifications named, +2 | 1 Data processing agreement | Compare |
| 1Password1password.com | 57/100 | 5 Data location stated, Status page with history, Certifications named, +2 | 2 Public pricing, Notice before subprocessors change | Compare |
| Clerkclerk.com | 61/100 | 4 Status page with history, Certifications named, security.txt (RFC 9116), +1 | nothing | Compare |
| Oktaokta.com | 61/100 | 4 Data location stated, Status page with history, security.txt (RFC 9116), +1 | 1 Notice before subprocessors change | Compare |
| Dashlanedashlane.com | 52/100 | 4 Subprocessor list, Data location stated, security.txt (RFC 9116), +1 | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Duo Securityduo.com | 48/100 | 4 Data location stated, Status page with history, Certifications named, +1 | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Oryory.com | 43/100 | 4 Data location stated, Certifications named, Uptime SLA with a figure, +1 | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Passboltpassbolt.com | 43/100 | 4 Data location stated, Certifications named, security.txt (RFC 9116), +1 | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Fronteggfrontegg.com | 39/100 | 4 Data location stated, Status page with history, Certifications named, +1 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | Compare |
| FusionAuthfusionauth.io | 39/100 | 4 Status page with history, Certifications named, security.txt (RFC 9116), +1 | 2 Data processing agreement, Notice before subprocessors change | Compare |
| WorkOSworkos.com | 48/100 | 3 Status page with history, Certifications named, Uptime SLA with a figure | 1 HTTPS enforced with HSTS | 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.