Alternatives to Keeper
Other Password and identity vendors we measure, sorted by how much they publish that Keeper does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 24 that differ from Keeper on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Keeper has 2 gaps in what we could measure: Status page with history, Uptime SLA with a figure. The column “publishes and Keeper does not” is the one that closes them.
| Vendor | Score | Publishes, and Keeper does not | Keeper publishes, and they do not | |
|---|---|---|---|---|
| WorkOSworkos.com | 60/100 | 2 Status page with history, Uptime SLA with a figure | 4 Subprocessor list, HTTPS enforced with HSTS, No third-party tracking before consent, +1 | Compare |
| Ping Identitypingidentity.com | 74/100 | 1 Status page with history | 2 Data processing agreement, No third-party tracking before consent | Compare |
| 1Password1password.com | 70/100 | 1 Status page with history | 2 Subprocessor list, No third-party tracking before consent | Compare |
| Clerkclerk.com | 70/100 | 1 Status page with history | 2 Subprocessor list, No third-party tracking before consent | Compare |
| Oktaokta.com | 61/100 | 1 Status page with history | 3 Subprocessor list, Certifications named, No third-party tracking before consent | Compare |
| Duo Securityduo.com | 48/100 | 1 Status page with history | 3 Data processing agreement, Subprocessor list, No third-party tracking before consent | Compare |
| Stytchstytch.com | 45/100 | 1 Status page with history | 5 Data processing agreement, Subprocessor list, Certifications named, +2 | Compare |
| Oryory.com | 43/100 | 1 Uptime SLA with a figure | 3 Data processing agreement, Subprocessor list, No third-party tracking before consent | Compare |
| Descopedescope.com | 39/100 | 1 Uptime SLA with a figure | 5 Data processing agreement, Data location stated, Certifications named, +2 | Compare |
| Fronteggfrontegg.com | 39/100 | 1 Status page with history | 5 Data processing agreement, Subprocessor list, HTTPS enforced with HSTS, +2 | Compare |
| FusionAuthfusionauth.io | 39/100 | 1 Status page with history | 4 Data processing agreement, Subprocessor list, Data location stated, +1 | Compare |
| JumpCloudjumpcloud.com | 35/100 | 1 Status page with history | 5 Data processing agreement, Subprocessor list, Data location stated, +2 | 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.