Transparency alternatives to CognitOps
Other Warehouse management vendors we measure, sorted by how much we found at them and not at CognitOps. This is a comparison of disclosure, not of features or fitness.
12 shown of 45 that differ from CognitOps on at least one criterion we measured for both. Public transparency score, not a product or security rating.
CognitOps has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116). The column “Found there, not found at CognitOps” is the one that closes them.
| Vendor | Score | Found there, not found at CognitOps | Found at CognitOps, not found there | |
|---|---|---|---|---|
| EasyEcomeasyecom.ioSee also Transparency alternatives to EasyEcom | 52/100 | 3 Data processing agreement, Certifications named, HTTPS enforced with HSTS | nothing | Compare |
| Infoplusinfopluscommerce.comSee also Transparency alternatives to Infoplus | 22/100 | 3 Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS | 3 Data location stated, Notice before subprocessors change, Named privacy contact | Compare |
| Balloon Oneballoonone.comSee also Transparency alternatives to Balloon One | 30/100 | 2 Public pricing, HTTPS enforced with HSTS | 2 Notice before subprocessors change, Named privacy contact | Compare |
| Datapel WMSdatapel.comSee also Transparency alternatives to Datapel WMS | 30/100 | 2 Public pricing, HTTPS enforced with HSTS | 2 Notice before subprocessors change, Named privacy contact | Compare |
| Generixgenerixgroup.comSee also Transparency alternatives to Generix | 30/100 | 2 Uptime SLA with a figure, HTTPS enforced with HSTS | 1 Notice before subprocessors change | Compare |
| Locus Roboticslocusrobotics.comSee also Transparency alternatives to Locus Robotics | 26/100 | 2 Certifications named, HTTPS enforced with HSTS | 2 Notice before subprocessors change, Named privacy contact | Compare |
| AutoStoreautostoresystem.comSee also Transparency alternatives to AutoStore | 22/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 Data location stated, Notice before subprocessors change | Compare |
| Fulfil.iofulfil.ioSee also Transparency alternatives to Fulfil.io | 22/100 | 2 Certifications named, security.txt (RFC 9116) | 2 Notice before subprocessors change, Named privacy contact | Compare |
| Optioryxoptioryx.comSee also Transparency alternatives to Optioryx | 22/100 | 2 Public pricing, HTTPS enforced with HSTS | 2 Data location stated, Notice before subprocessors change | Compare |
| Bitlog WMSbitlogwms.comSee also Transparency alternatives to Bitlog WMS | 17/100 | 2 Public pricing, HTTPS enforced with HSTS | 3 Data location stated, Notice before subprocessors change, Named privacy contact | Compare |
| Cadre Technologiescadretech.comSee also Transparency alternatives to Cadre Technologies | 17/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Data location stated, Notice before subprocessors change | Compare |
| Flowspaceflow.spaceSee also Transparency alternatives to Flowspace | 17/100 | 2 Public pricing, HTTPS enforced with HSTS | 3 Data location stated, Notice before subprocessors change, 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.