Transparency alternatives to GAT Labs
Other Identity governance vendors we measure, sorted by how much we found at them and not at GAT Labs. This is a comparison of disclosure, not of features or fitness.
12 shown of 25 that differ from GAT Labs on at least one criterion we measured for both. Public transparency score, not a product or security rating.
GAT Labs has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “Found there, not found at GAT Labs” is the one that closes them.
| Vendor | Score | Found there, not found at GAT Labs | Found at GAT Labs, not found there | |
|---|---|---|---|---|
| Oasis Securityoasis.securitySee also Transparency alternatives to Oasis Security | 43/100 | 5 Data processing agreement, Uptime SLA with a figure, HTTPS enforced with HSTS, +2 | 2 Status page with history, Public pricing | Compare |
| Access Owlaccessowl.comSee also Transparency alternatives to Access Owl | 39/100 | 4 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 2 Status page with history, Certifications named | Compare |
| Hyprhypr.comSee also Transparency alternatives to Hypr | 48/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Notice before subprocessors change | 1 Certifications named | Compare |
| Imprivataimprivata.comSee also Transparency alternatives to Imprivata | 43/100 | 3 Data processing agreement, Data location stated, HTTPS enforced with HSTS | 2 Public pricing, Certifications named | Compare |
| Simeiosimeio.comSee also Transparency alternatives to Simeio | 35/100 | 3 Data processing agreement, Data location stated, HTTPS enforced with HSTS | 3 Status page with history, Public pricing, Certifications named | Compare |
| Avatieravatier.comSee also Transparency alternatives to Avatier | 30/100 | 3 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Status page with history, Public pricing | Compare |
| Beta Systemsbetasystems.comSee also Transparency alternatives to Beta Systems | 29/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 3 Status page with history, Public pricing, Certifications named | Compare |
| Clear Skyeclearskye.comSee also Transparency alternatives to Clear Skye | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 3 Status page with history, Public pricing, Certifications named | Compare |
| Ipgipg-group.comSee also Transparency alternatives to Ipg | 23/100 | 3 HTTPS enforced with HSTS, No third-party tracking before consent, Named privacy contact | 3 Status page with history, Public pricing, Certifications named | Compare |
| Identityautomationidentityautomation.comSee also Transparency alternatives to Identityautomation | 26/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 1 Public pricing | Compare |
| Gluugluu.orgSee also Transparency alternatives to Gluu | 22/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 2 Status page with history, Public pricing | Compare |
| Radiantlogicradiantlogic.comSee also Transparency alternatives to Radiantlogic | 22/100 | 2 Data location stated, HTTPS enforced with HSTS | 3 Status page with history, Public pricing, Certifications named | 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.