Transparency alternatives to UpKeep
Other Maintenance management (CMMS) vendors we measure, sorted by how much we found at them and not at UpKeep. This is a comparison of disclosure, not of features or fitness.
12 shown of 60 that differ from UpKeep on at least one criterion we measured for both. Public transparency score, not a product or security rating.
UpKeep has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact. The column “Found there, not found at UpKeep” is the one that closes them.
| Vendor | Score | Found there, not found at UpKeep | Found at UpKeep, not found there | |
|---|---|---|---|---|
| ServiceChannelservicechannel.comSee also Transparency alternatives to ServiceChannel | 43/100 | 3 Data processing agreement, Status page with history, HTTPS enforced with HSTS | 3 Public pricing, Certifications named, Notice before subprocessors change | Compare |
| Fiixfiixsoftware.comSee also Transparency alternatives to Fiix | 35/100 | 3 Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS | 2 Data location stated, Notice before subprocessors change | Compare |
| Cenoscocenosco.comSee also Transparency alternatives to Cenosco | 22/100 | 3 HTTPS enforced with HSTS, No third-party tracking before consent, Named privacy contact | 4 Data location stated, Public pricing, Certifications named, +1 | Compare |
| GEOMAGIC GeoNAMgeomagic.deSee also Transparency alternatives to GEOMAGIC GeoNAM | 17/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | 4 Data location stated, Public pricing, Certifications named, +1 | Compare |
| Infraspeakinfraspeak.comSee also Transparency alternatives to Infraspeak | 30/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 2 Public pricing, Notice before subprocessors change | Compare |
| Limblelimble.comSee also Transparency alternatives to Limble | 30/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 2 Public pricing, Notice before subprocessors change | Compare |
| Asset Infinityassetinfinity.comSee also Transparency alternatives to Asset Infinity | 22/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 3 Data location stated, Certifications named, Notice before subprocessors change | Compare |
| Mendrhubmendrhub.comSee also Transparency alternatives to Mendrhub | 22/100 | 2 Subprocessor list, HTTPS enforced with HSTS | 4 Data location stated, Public pricing, Certifications named, +1 | Compare |
| Ultimoultimo.comSee also Transparency alternatives to Ultimo | 22/100 | 2 Status page with history, HTTPS enforced with HSTS | 3 Data location stated, Public pricing, Notice before subprocessors change | Compare |
| Fracttalfracttal.comSee also Transparency alternatives to Fracttal | 17/100 | 2 Status page with history, HTTPS enforced with HSTS | 4 Data location stated, Public pricing, Certifications named, +1 | Compare |
| MicroWest AMMSmicrowestsoftware.comSee also Transparency alternatives to MicroWest AMMS | 17/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 4 Data location stated, Public pricing, Certifications named, +1 | Compare |
| Accruentaccruent.comSee also Transparency alternatives to Accruent | 30/100 | 1 HTTPS enforced with HSTS | 2 Certifications named, Notice before subprocessors change | 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.