Transparency alternatives to NextBillion.ai
Other Route planning and delivery vendors we measure, sorted by how much we found at them and not at NextBillion.ai. This is a comparison of disclosure, not of features or fitness.
12 shown of 64 that differ from NextBillion.ai on at least one criterion we measured for both. Public transparency score, not a product or security rating.
NextBillion.ai has 6 gaps in what we could measure: Subprocessor list, Data location stated, Status page with history, No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact. The column “Found there, not found at NextBillion.ai” is the one that closes them.
| Vendor | Score | Found there, not found at NextBillion.ai | Found at NextBillion.ai, not found there | |
|---|---|---|---|---|
| Lytxlytx.comSee also Transparency alternatives to Lytx | 48/100 | 4 Subprocessor list, Data location stated, Status page with history, +1 | 5 Data processing agreement, Public pricing, Certifications named, +2 | Compare |
| RideCorideco.comSee also Transparency alternatives to RideCo | 52/100 | 3 Subprocessor list, Data location stated, Named privacy contact | 3 Data processing agreement, Public pricing, Uptime SLA with a figure | Compare |
| Routalroutal.comSee also Transparency alternatives to Routal | 43/100 | 3 Data location stated, No third-party tracking before consent, Named privacy contact | 4 Data processing agreement, Certifications named, Uptime SLA with a figure, +1 | Compare |
| Netradynenetradyne.comSee also Transparency alternatives to Netradyne | 43/100 | 2 Data location stated, Named privacy contact | 3 Public pricing, Uptime SLA with a figure, Notice before subprocessors change | Compare |
| One Step GPSonestepgps.comSee also Transparency alternatives to One Step GPS | 35/100 | 2 Status page with history, Named privacy contact | 3 Data processing agreement, Uptime SLA with a figure, Notice before subprocessors change | Compare |
| Detrackdetrack.comSee also Transparency alternatives to Detrack | 30/100 | 2 Data location stated, Named privacy contact | 4 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +1 | Compare |
| TripShottripshot.comSee also Transparency alternatives to TripShot | 30/100 | 2 Data location stated, Named privacy contact | 4 Data processing agreement, Public pricing, Uptime SLA with a figure, +1 | Compare |
| Routewarerouteware.comSee also Transparency alternatives to Routeware | 26/100 | 2 Data location stated, Named privacy contact | 5 Data processing agreement, Public pricing, Certifications named, +2 | Compare |
| Trackunittrackunit.comSee also Transparency alternatives to Trackunit | 22/100 | 2 Status page with history, Named privacy contact | 5 Data processing agreement, Public pricing, Certifications named, +2 | Compare |
| Radiusradius.comSee also Transparency alternatives to Radius | 18/100 | 2 Data location stated, Named privacy contact | 6 Data processing agreement, Public pricing, Certifications named, +3 | Compare |
| ABAXabax.comSee also Transparency alternatives to ABAX | 17/100 | 2 security.txt (RFC 9116), Named privacy contact | 5 Data processing agreement, Public pricing, Certifications named, +2 | Compare |
| DA Systemsda-systems.co.ukSee also Transparency alternatives to DA Systems | 17/100 | 2 Data location stated, Named privacy contact | 6 Data processing agreement, Public pricing, Certifications named, +3 | 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.