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