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