Transparency alternatives to GEOMAGIC GeoNAM
Other Maintenance management (CMMS) vendors we measure, sorted by how much they publish that GEOMAGIC GeoNAM does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 61 that differ from GEOMAGIC GeoNAM on at least one criterion we measured for both. Public transparency score, not a product or security rating.
GEOMAGIC GeoNAM has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “publishes and GEOMAGIC GeoNAM does not” is the one that closes them.
| Vendor | Score | Publishes, and GEOMAGIC GeoNAM does not | GEOMAGIC GeoNAM publishes, and they do not | |
|---|---|---|---|---|
| UpKeepupkeep.com | 35/100 | 4 Data location stated, Public pricing, Certifications named, +1 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | Compare |
| Fiixfiixsoftware.com | 30/100 | 3 Status page with history, Public pricing, Certifications named | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| MaintainXgetmaintainx.com | 30/100 | 3 Data location stated, Public pricing, Certifications named | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Accruentaccruent.com | 30/100 | 2 Data location stated, Public pricing | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Infraspeakinfraspeak.com | 30/100 | 2 Data location stated, Certifications named | 1 security.txt (RFC 9116) | Compare |
| Limblelimble.com | 30/100 | 2 Data location stated, Certifications named | 1 security.txt (RFC 9116) | Compare |
| ServiceChannelservicechannel.com | 30/100 | 2 Data processing agreement, Status page with history | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Ultimoultimo.com | 22/100 | 2 Status page with history, Certifications named | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Azzierazzier.com | 13/100 | 2 Public pricing, Certifications named | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | Compare |
| Asset Infinityassetinfinity.com | 22/100 | 1 Public pricing | 1 security.txt (RFC 9116) | Compare |
| Cenoscocenosco.com | 22/100 | 1 No third-party tracking before consent | 1 security.txt (RFC 9116) | Compare |
| eMaintemaint.com | 22/100 | 1 Data location stated | 2 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.