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