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