Transparency alternatives to Rezolve
Other IT service management vendors we measure, sorted by how much we found at them and not at Rezolve. This is a comparison of disclosure, not of features or fitness.
12 shown of 29 that differ from Rezolve on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Rezolve has 6 gaps in what we could measure: Subprocessor list, Data location stated, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact. The column “Found there, not found at Rezolve” is the one that closes them.
| Vendor | Score | Found there, not found at Rezolve | Found at Rezolve, not found there | |
|---|---|---|---|---|
| Atlassianatlassian.comSee also Transparency alternatives to Atlassian | 71/100 | 4 Subprocessor list, Uptime SLA with a figure, security.txt (RFC 9116), +1 | 2 Public pricing, Certifications named | Compare |
| Ivantiivanti.comSee also Transparency alternatives to Ivanti | 39/100 | 3 Data location stated, security.txt (RFC 9116), Named privacy contact | 4 Data processing agreement, Public pricing, Certifications named, +1 | Compare |
| ManageEnginemanageengine.comSee also Transparency alternatives to ManageEngine | 35/100 | 3 Data location stated, security.txt (RFC 9116), Named privacy contact | 4 Data processing agreement, Status page with history, Public pricing, +1 | Compare |
| OTRSotrs.comSee also Transparency alternatives to OTRS | 35/100 | 3 Data location stated, security.txt (RFC 9116), Named privacy contact | 4 Data processing agreement, Status page with history, Public pricing, +1 | Compare |
| Atomicworkatomicwork.comSee also Transparency alternatives to Atomicwork | 48/100 | 2 Subprocessor list, Named privacy contact | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Xurrentxurrent.comSee also Transparency alternatives to Xurrent | 41/100 | 2 Data location stated, Named privacy contact | 3 Data processing agreement, Public pricing, Notice before subprocessors change | Compare |
| Alloy Softwarealloysoftware.comSee also Transparency alternatives to Alloy Software | 39/100 | 2 No third-party tracking before consent, Named privacy contact | 3 Status page with history, HTTPS enforced with HSTS, Notice before subprocessors change | Compare |
| GLPIglpi-project.orgSee also Transparency alternatives to GLPI | 35/100 | 2 Data location stated, Named privacy contact | 4 Data processing agreement, Status page with history, Certifications named, +1 | Compare |
| Dreamtsoftdreamtsoft.comSee also Transparency alternatives to Dreamtsoft | 22/100 | 2 No third-party tracking before consent, security.txt (RFC 9116) | 5 Data processing agreement, Status page with history, Public pricing, +2 | Compare |
| Motadatamotadata.comSee also Transparency alternatives to Motadata | 13/100 | 2 No third-party tracking before consent, Named privacy contact | 6 Data processing agreement, Status page with history, Public pricing, +3 | Compare |
| Siitsiit.ioSee also Transparency alternatives to Siit | 35/100 | 1 Data location stated | 3 Data processing agreement, Status page with history, Notice before subprocessors change | Compare |
| SysAidsysaid.comSee also Transparency alternatives to SysAid | 30/100 | 1 Data location stated | 4 Data processing agreement, Status page with history, Certifications named, +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.