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