Transparency alternatives to Incenergy
Other Energy management vendors we measure, sorted by how much we found at them and not at Incenergy. This is a comparison of disclosure, not of features or fitness.
12 shown of 33 that differ from Incenergy on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Incenergy has 12 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, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Incenergy” is the one that closes them.
| Vendor | Score | Found there, not found at Incenergy | Found at Incenergy, not found there | |
|---|---|---|---|---|
| Densitydensity.ioSee also Transparency alternatives to Density | 57/100 | 7 Data processing agreement, Status page with history, Public pricing, +4 | nothing | Compare |
| Measurablmeasurabl.comSee also Transparency alternatives to Measurabl | 48/100 | 5 Data processing agreement, Subprocessor list, Public pricing, +2 | nothing | Compare |
| Tangotangoanalytics.comSee also Transparency alternatives to Tango | 39/100 | 5 Data processing agreement, Uptime SLA with a figure, HTTPS enforced with HSTS, +2 | nothing | Compare |
| Deepkideepki.comSee also Transparency alternatives to Deepki | 33/100 | 4 Data location stated, Certifications named, HTTPS enforced with HSTS, +1 | nothing | Compare |
| Envelioenvelio.comSee also Transparency alternatives to Envelio | 30/100 | 4 Data location stated, Certifications named, HTTPS enforced with HSTS, +1 | nothing | Compare |
| Gridxgridx.aiSee also Transparency alternatives to Gridx | 30/100 | 4 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | nothing | Compare |
| Meteocontrolmeteocontrol.comSee also Transparency alternatives to Meteocontrol | 30/100 | 4 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | nothing | Compare |
| Arbncoarbnco.comSee also Transparency alternatives to Arbnco | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| Butlrbutlr.comSee also Transparency alternatives to Butlr | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| Energycapenergycap.comSee also Transparency alternatives to Energycap | 23/100 | 3 Status page with history, HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| Arcadiaarcadia.comSee also Transparency alternatives to Arcadia | 22/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | nothing | Compare |
| Sensesense.comSee also Transparency alternatives to Sense | 22/100 | 3 Status page with history, 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.