SaaS Ranking

Alternatives to Sedna

Other Maritime and port operations vendors we measure, sorted by how much they publish that Sedna does not. This is a comparison of disclosure, not of features or fitness.

12 shown of 29 that differ from Sedna on at least one criterion we measured for both. Public transparency score, not a product or security rating.

Sedna has 11 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, 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 “publishes and Sedna does not” is the one that closes them.

VendorScorePublishes, and Sedna does notSedna publishes, and they do not
Veson Nauticalveson.com 48/100 4 Subprocessor list, Data location stated, Notice before subprocessors change, +1 nothing Compare
Kaleriskaleris.com 30/100 4 Data location stated, Certifications named, HTTPS enforced with HSTS, +1 1 Status page with history Compare
Solvermindssolverminds.com 30/100 4 Data location stated, Certifications named, HTTPS enforced with HSTS, +1 1 Status page with history Compare
ZeroNorthzeronorth.com 30/100 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change 1 Status page with history Compare
Hanseaticsofthanseaticsoft.com 26/100 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact 1 Status page with history Compare
Seasea.live 26/100 3 Data location stated, Certifications named, HTTPS enforced with HSTS 1 Status page with history Compare
Windwardwindward.ai 26/100 3 Data location stated, No third-party tracking before consent, Named privacy contact 1 Status page with history Compare
Marcuramarcura.com 17/100 3 Certifications named, HTTPS enforced with HSTS, Named privacy contact 1 Status page with history Compare
NAVTORnavtor.com 17/100 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact 1 Status page with history Compare
Awake.AIawake.ai 22/100 2 HTTPS enforced with HSTS, security.txt (RFC 9116) nothing Compare
Bearing AIbearing.ai 22/100 2 Data location stated, HTTPS enforced with HSTS 1 Status page with history Compare
Helm Operationshelmoperations.com 22/100 2 Data location stated, HTTPS enforced with HSTS 1 Status page with history 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.