Transparency alternatives to GISGRO
Other Maritime and port operations vendors we measure, sorted by how much they publish that GISGRO does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 39 that differ from GISGRO on at least one criterion we measured for both. Public transparency score, not a product or security rating.
GISGRO has 10 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), Notice before subprocessors change. The column “publishes and GISGRO does not” is the one that closes them.
| Vendor | Score | Publishes, and GISGRO does not | GISGRO publishes, and they do not | |
|---|---|---|---|---|
| Veson Nauticalveson.com | 48/100 | 3 Subprocessor list, Status page with history, Notice before subprocessors change | nothing | Compare |
| ZeroNorthzeronorth.com | 30/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | 2 Data location stated, Named privacy contact | Compare |
| Awake.AIawake.ai | 22/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Data location stated, Named privacy contact | Compare |
| Portchainportchain.com | 22/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Data location stated, Named privacy contact | Compare |
| Kaleriskaleris.com | 30/100 | 2 Certifications named, HTTPS enforced with HSTS | nothing | Compare |
| Seasea.live | 26/100 | 2 Certifications named, HTTPS enforced with HSTS | 1 Named privacy contact | Compare |
| Vortexavortexa.com | 26/100 | 2 Subprocessor list, HTTPS enforced with HSTS | 1 Data location stated | Compare |
| Kplerkpler.com | 22/100 | 2 Status page with history, HTTPS enforced with HSTS | 1 Data location stated | Compare |
| Windwardwindward.ai | 22/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 1 Data location stated | Compare |
| Containerchaincontainerchain.com | 17/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 1 Data location stated | Compare |
| Danelecdanelec.com | 17/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 Data location stated, Named privacy contact | Compare |
| Marcuramarcura.com | 17/100 | 2 Certifications named, HTTPS enforced with HSTS | 1 Data location stated | 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.