Alternatives to Cargoson
Other Shipping and logistics vendors we measure, sorted by how much they publish that Cargoson does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 29 that differ from Cargoson on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Cargoson has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “publishes and Cargoson does not” is the one that closes them.
| Vendor | Score | Publishes, and Cargoson does not | Cargoson publishes, and they do not | |
|---|---|---|---|---|
| AfterShipaftership.com | 83/100 | 7 Data processing agreement, Subprocessor list, Data location stated, +4 | 1 security.txt (RFC 9116) | Compare |
| FourKitesfourkites.com | 52/100 | 6 Data processing agreement, Data location stated, Status page with history, +3 | 3 Public pricing, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Sendcloudsendcloud.com | 61/100 | 5 Data processing agreement, Data location stated, Certifications named, +2 | 1 security.txt (RFC 9116) | Compare |
| Bringgbringg.com | 43/100 | 4 Data processing agreement, Status page with history, Notice before subprocessors change, +1 | 2 Public pricing, security.txt (RFC 9116) | Compare |
| EasyPosteasypost.com | 43/100 | 3 Data location stated, Status page with history, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Easyshipeasyship.com | 43/100 | 3 Data processing agreement, Status page with history, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Metapackmetapack.com | 43/100 | 3 Data processing agreement, Uptime SLA with a figure, Notice before subprocessors change | 1 security.txt (RFC 9116) | Compare |
| Onfleetonfleet.com | 43/100 | 3 Data location stated, Status page with history, Certifications named | 1 security.txt (RFC 9116) | Compare |
| Locuslocus.sh | 30/100 | 3 Data location stated, Certifications named, Named privacy contact | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Freightosfreightos.com | 30/100 | 2 Data location stated, Status page with history | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Wise Systemswisesystems.com | 26/100 | 2 Data location stated, Named privacy contact | 2 Public pricing, security.txt (RFC 9116) | Compare |
| nShiftnshift.com | 22/100 | 2 Status page with history, Named privacy contact | 2 Public pricing, 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.