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