Transparency alternatives to Last Mile Solutions
Other EV charging software vendors we measure, sorted by how much we found at them and not at Last Mile Solutions. This is a comparison of disclosure, not of features or fitness.
12 shown of 38 that differ from Last Mile Solutions on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Last Mile Solutions has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, 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. The column “Found there, not found at Last Mile Solutions” is the one that closes them.
| Vendor | Score | Found there, not found at Last Mile Solutions | Found at Last Mile Solutions, not found there | |
|---|---|---|---|---|
| Driivzdriivz.comSee also Transparency alternatives to Driivz | 35/100 | 4 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +1 | 2 Data location stated, Named privacy contact | Compare |
| Virtavirta.globalSee also Transparency alternatives to Virta | 26/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 1 Data location stated | Compare |
| Zeplugzeplug.comSee also Transparency alternatives to Zeplug | 22/100 | 3 Public pricing, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Data location stated, Named privacy contact | Compare |
| Chargepointchargepoint.comSee also Transparency alternatives to Chargepoint | 32/100 | 2 Status page with history, Certifications named | nothing | Compare |
| Hubjecthubject.comSee also Transparency alternatives to Hubject | 22/100 | 2 Public pricing, HTTPS enforced with HSTS | 1 Data location stated | Compare |
| Plugsurfingplugsurfing.comSee also Transparency alternatives to Plugsurfing | 22/100 | 2 Status page with history, HTTPS enforced with HSTS | 1 Data location stated | Compare |
| Chargepricechargeprice.appSee also Transparency alternatives to Chargeprice | 17/100 | 2 Public pricing, HTTPS enforced with HSTS | 2 Data location stated, Named privacy contact | Compare |
| Ellielli.ecoSee also Transparency alternatives to Elli | 17/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 1 Data location stated | Compare |
| Go-ego-e.comSee also Transparency alternatives to Go-e | 17/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 2 Data location stated, Named privacy contact | Compare |
| Montamonta.comSee also Transparency alternatives to Monta | 17/100 | 2 Public pricing, HTTPS enforced with HSTS | 2 Data location stated, Named privacy contact | Compare |
| Ampecoampeco.comSee also Transparency alternatives to Ampeco | 13/100 | 2 Certifications named, HTTPS enforced with HSTS | 2 Data location stated, Named privacy contact | Compare |
| Kebakeba.comSee also Transparency alternatives to Keba | 13/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Data location stated, Named privacy contact | 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.