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