Transparency alternatives to Atlassys TMS
Other Shipping and logistics vendors we measure, sorted by how much we found at them and not at Atlassys TMS. This is a comparison of disclosure, not of features or fitness.
12 shown of 81 that differ from Atlassys TMS on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Atlassys TMS 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, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Atlassys TMS” is the one that closes them.
| Vendor | Score | Found there, not found at Atlassys TMS | Found at Atlassys TMS, not found there | |
|---|---|---|---|---|
| AfterShipaftership.comSee also Transparency alternatives to AfterShip | 86/100 | 9 Data processing agreement, Subprocessor list, Data location stated, +6 | 1 No third-party tracking before consent | Compare |
| Sendcloudsendcloud.comSee also Transparency alternatives to Sendcloud | 70/100 | 8 Data processing agreement, Data location stated, Status page with history, +5 | 1 No third-party tracking before consent | Compare |
| FourKitesfourkites.comSee also Transparency alternatives to FourKites | 48/100 | 5 Data processing agreement, Data location stated, Status page with history, +2 | 1 No third-party tracking before consent | Compare |
| Bringgbringg.comSee also Transparency alternatives to Bringg | 43/100 | 5 Data processing agreement, Status page with history, HTTPS enforced with HSTS, +2 | 1 No third-party tracking before consent | Compare |
| EasyPosteasypost.comSee also Transparency alternatives to EasyPost | 43/100 | 5 Data location stated, Status page with history, Public pricing, +2 | 1 No third-party tracking before consent | Compare |
| Easyshipeasyship.comSee also Transparency alternatives to Easyship | 43/100 | 5 Data processing agreement, Status page with history, Public pricing, +2 | 1 No third-party tracking before consent | Compare |
| Metapackmetapack.comSee also Transparency alternatives to Metapack | 43/100 | 5 Data processing agreement, Public pricing, Uptime SLA with a figure, +2 | 1 No third-party tracking before consent | Compare |
| ShipStationshipstation.comSee also Transparency alternatives to ShipStation | 43/100 | 5 Data location stated, Status page with history, Public pricing, +2 | 1 No third-party tracking before consent | Compare |
| Elromcoelromco.comSee also Transparency alternatives to Elromco | 35/100 | 4 Public pricing, Certifications named, HTTPS enforced with HSTS, +1 | nothing | Compare |
| Seven Senderssevensenders.comSee also Transparency alternatives to Seven Senders | 35/100 | 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 | 1 No third-party tracking before consent | Compare |
| Locuslocus.shSee also Transparency alternatives to Locus | 30/100 | 4 Data location stated, Public pricing, Certifications named, +1 | 1 No third-party tracking before consent | Compare |
| Shippogoshippo.comSee also Transparency alternatives to Shippo | 30/100 | 4 Status page with history, Public pricing, Certifications named, +1 | 1 No third-party tracking before consent | 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.