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