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