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