Transparency alternatives to Spectec
Other Maritime and port operations vendors we measure, sorted by how much we found at them and not at Spectec. This is a comparison of disclosure, not of features or fitness.
12 shown of 40 that differ from Spectec on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Spectec 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 “Found there, not found at Spectec” is the one that closes them.
| Vendor | Score | Found there, not found at Spectec | Found at Spectec, not found there | |
|---|---|---|---|---|
| Veson Nauticalveson.comSee also Transparency alternatives to Veson Nautical | 48/100 | 3 Subprocessor list, Status page with history, Notice before subprocessors change | nothing | Compare |
| ZeroNorthzeronorth.comSee also Transparency alternatives to ZeroNorth | 30/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | 2 Data location stated, Named privacy contact | Compare |
| Awake.AIawake.aiSee also Transparency alternatives to Awake.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.comSee also Transparency alternatives to Portchain | 22/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Data location stated, Named privacy contact | Compare |
| Solvermindssolverminds.comSee also Transparency alternatives to Solverminds | 22/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 1 Data location stated | Compare |
| Kaleriskaleris.comSee also Transparency alternatives to Kaleris | 30/100 | 2 Certifications named, HTTPS enforced with HSTS | nothing | Compare |
| Seasea.liveSee also Transparency alternatives to Sea | 26/100 | 2 Certifications named, HTTPS enforced with HSTS | 1 Named privacy contact | Compare |
| Vortexavortexa.comSee also Transparency alternatives to Vortexa | 26/100 | 2 Subprocessor list, HTTPS enforced with HSTS | 1 Data location stated | Compare |
| Kplerkpler.comSee also Transparency alternatives to Kpler | 22/100 | 2 Status page with history, HTTPS enforced with HSTS | 1 Data location stated | Compare |
| Windwardwindward.aiSee also Transparency alternatives to Windward | 22/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 1 Data location stated | Compare |
| Containerchaincontainerchain.comSee also Transparency alternatives to Containerchain | 17/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 1 Data location stated | Compare |
| Danelecdanelec.comSee also Transparency alternatives to Danelec | 17/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 Data location stated, 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.