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