Alternatives to Reev
Other EV charging software vendors we measure, sorted by how much they publish that Reev does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 27 that differ from Reev on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Reev has 9 gaps in what we could measure: 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 “publishes and Reev does not” is the one that closes them.
| Vendor | Score | Publishes, and Reev does not | Reev publishes, and they do not | |
|---|---|---|---|---|
| Driivzdriivz.com | 35/100 | 3 Certifications named, HTTPS enforced with HSTS, Notice before subprocessors change | 2 Data location stated, Named privacy contact | Compare |
| Virtavirta.global | 26/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 2 Data processing agreement, Data location stated | Compare |
| Hubjecthubject.com | 35/100 | 2 Public pricing, HTTPS enforced with HSTS | 1 Data processing agreement | Compare |
| Chargepointchargepoint.com | 32/100 | 2 Status page with history, Certifications named | 1 Data processing agreement | Compare |
| Chargecloudchargecloud.de | 22/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 Data processing agreement, Data location stated | Compare |
| Ellielli.eco | 17/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Data processing agreement, Data location stated | Compare |
| Go-ego-e.com | 17/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 3 Data processing agreement, Data location stated, Named privacy contact | Compare |
| Montamonta.com | 17/100 | 2 Public pricing, HTTPS enforced with HSTS | 3 Data processing agreement, Data location stated, Named privacy contact | Compare |
| Ampecoampeco.com | 13/100 | 2 Certifications named, HTTPS enforced with HSTS | 3 Data processing agreement, Data location stated, Named privacy contact | Compare |
| Kebakeba.com | 13/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 3 Data processing agreement, Data location stated, Named privacy contact | Compare |
| Atlanteatlante.energy | 26/100 | 1 HTTPS enforced with HSTS | 1 Data processing agreement | Compare |
| Easeeeasee.com | 26/100 | 1 Status page with history | 1 Data processing agreement | 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.