Transparency alternatives to Ory
Other Password and identity vendors we measure, sorted by how much we found at them and not at Ory. This is a comparison of disclosure, not of features or fitness.
12 shown of 34 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 “Found there, not found at Ory” is the one that closes them.
| Vendor | Score | Found there, not found at Ory | Found at Ory, not found there | |
|---|---|---|---|---|
| Keeperkeepersecurity.comSee also Transparency alternatives to Keeper | 74/100 | 5 Data processing agreement, Subprocessor list, No third-party tracking before consent, +2 | 2 Data location stated, Uptime SLA with a figure | Compare |
| Ping Identitypingidentity.comSee also Transparency alternatives to Ping Identity | 61/100 | 4 Subprocessor list, Status page with history, Notice before subprocessors change, +1 | 2 Data location stated, Uptime SLA with a figure | Compare |
| Oktaokta.comSee also Transparency alternatives to Okta | 61/100 | 3 Data processing agreement, Status page with history, Named privacy contact | 2 Certifications named, Uptime SLA with a figure | Compare |
| 1Password1password.comSee also Transparency alternatives to 1Password | 57/100 | 3 Data processing agreement, Status page with history, Named privacy contact | 2 Public pricing, Uptime SLA with a figure | Compare |
| Clerkclerk.comSee also Transparency alternatives to Clerk | 52/100 | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | 2 Data location stated, Uptime SLA with a figure | Compare |
| WorkOSworkos.comSee also Transparency alternatives to WorkOS | 48/100 | 3 Data processing agreement, Status page with history, Notice before subprocessors change | 3 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Zitadelzitadel.comSee also Transparency alternatives to Zitadel | 48/100 | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | 3 Data location stated, Certifications named, Uptime SLA with a figure | Compare |
| Dashlanedashlane.comSee also Transparency alternatives to Dashlane | 52/100 | 2 Subprocessor list, Named privacy contact | 2 Certifications named, Uptime SLA with a figure | Compare |
| Cerboscerbos.devSee also Transparency alternatives to Cerbos | 39/100 | 2 Data processing agreement, Notice before subprocessors change | 4 Data location stated, Certifications named, Uptime SLA with a figure, +1 | Compare |
| Descopedescope.comSee also Transparency alternatives to Descope | 39/100 | 2 Subprocessor list, Named privacy contact | 3 Data location stated, Certifications named, security.txt (RFC 9116) | Compare |
| Fronteggfrontegg.comSee also Transparency alternatives to Frontegg | 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.ioSee also Transparency alternatives to FusionAuth | 39/100 | 2 Status page with history, Named privacy contact | 2 Data location stated, 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.