Alternatives to AlsoEnergy
Other Energy management vendors we measure, sorted by how much they publish that AlsoEnergy does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 27 that differ from AlsoEnergy on at least one criterion we measured for both. Public transparency score, not a product or security rating.
AlsoEnergy has 11 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, 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, Named privacy contact. The column “publishes and AlsoEnergy does not” is the one that closes them.
| Vendor | Score | Publishes, and AlsoEnergy does not | AlsoEnergy publishes, and they do not | |
|---|---|---|---|---|
| Measurablmeasurabl.com | 61/100 | 6 Data processing agreement, Subprocessor list, Data location stated, +3 | 1 Status page with history | Compare |
| Densitydensity.io | 57/100 | 6 Data processing agreement, Public pricing, Uptime SLA with a figure, +3 | nothing | Compare |
| Tangotangoanalytics.com | 39/100 | 5 Data processing agreement, Uptime SLA with a figure, HTTPS enforced with HSTS, +2 | 1 Status page with history | Compare |
| Deepkideepki.com | 33/100 | 4 Data location stated, Certifications named, HTTPS enforced with HSTS, +1 | 1 Status page with history | Compare |
| Envelioenvelio.com | 30/100 | 4 Data location stated, Certifications named, HTTPS enforced with HSTS, +1 | 1 Status page with history | Compare |
| Gridxgridx.ai | 30/100 | 4 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 1 Status page with history | Compare |
| Meteocontrolmeteocontrol.com | 30/100 | 4 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 1 Status page with history | Compare |
| Centinelcentinelre.com | 30/100 | 3 Data location stated, Public pricing, HTTPS enforced with HSTS | 1 Status page with history | Compare |
| Butlrbutlr.com | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 1 Status page with history | Compare |
| Janitzajanitza.com | 17/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | 1 Status page with history | Compare |
| Sensesense.com | 24/100 | 2 HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| Energycapenergycap.com | 23/100 | 2 HTTPS enforced with HSTS, Named privacy contact | nothing | 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.