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