SaaS Ranking

Alternatives to Gridx

Other Energy management vendors we measure, sorted by how much they publish that Gridx does not. This is a comparison of disclosure, not of features or fitness.

12 shown of 26 that differ from Gridx on at least one criterion we measured for both. Public transparency score, not a product or security rating.

Gridx has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “publishes and Gridx does not” is the one that closes them.

VendorScorePublishes, and Gridx does notGridx publishes, and they do not
Densitydensity.io 57/100 5 Data processing agreement, Status page with history, Public pricing, +2 2 Data location stated, security.txt (RFC 9116) Compare
Measurablmeasurabl.com 61/100 4 Data processing agreement, Subprocessor list, Public pricing, +1 2 security.txt (RFC 9116), Named privacy contact Compare
Tangotangoanalytics.com 39/100 3 Data processing agreement, Uptime SLA with a figure, Notice before subprocessors change 2 Data location stated, security.txt (RFC 9116) Compare
Arcadiaarcadia.com 22/100 2 Status page with history, Certifications named 3 Data location stated, security.txt (RFC 9116), Named privacy contact Compare
Deepkideepki.com 33/100 1 Certifications named 1 security.txt (RFC 9116) Compare
Centinelcentinelre.com 30/100 1 Public pricing 2 security.txt (RFC 9116), Named privacy contact Compare
Envelioenvelio.com 30/100 1 Certifications named 1 security.txt (RFC 9116) Compare
Sensesense.com 24/100 1 Status page with history 2 Data location stated, security.txt (RFC 9116) Compare
Energycapenergycap.com 23/100 1 Status page with history 1 Data location stated Compare
Kiwigridkiwigrid.com 17/100 1 No third-party tracking before consent 3 Data location stated, security.txt (RFC 9116), Named privacy contact Compare
75F75f.io 13/100 1 Certifications named 3 Data location stated, security.txt (RFC 9116), Named privacy contact Compare
AlsoEnergyalsoenergy.com 9/100 1 Status page with history 4 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 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.