Transparency alternatives to Stadtwerke Cloud
Other Utility billing vendors we measure, sorted by how much we found at them and not at Stadtwerke Cloud. This is a comparison of disclosure, not of features or fitness.
12 shown of 21 that differ from Stadtwerke Cloud on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Stadtwerke Cloud 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 Stadtwerke Cloud” is the one that closes them.
| Vendor | Score | Found there, not found at Stadtwerke Cloud | Found at Stadtwerke Cloud, not found there | |
|---|---|---|---|---|
| Kraken Technologieskraken.techSee also Transparency alternatives to Kraken Technologies | 39/100 | 5 Subprocessor list, Certifications named, HTTPS enforced with HSTS, +2 | nothing | Compare |
| Cogsdalecogsdale.comSee also Transparency alternatives to Cogsdale | 22/100 | 2 Data location stated, HTTPS enforced with HSTS | nothing | Compare |
| Harris Utilitiesharriscomputer.comSee also Transparency alternatives to Harris Utilities | 22/100 | 2 Data location stated, HTTPS enforced with HSTS | nothing | Compare |
| Springbrookspringbrooksoftware.comSee also Transparency alternatives to Springbrook | 22/100 | 2 Data location stated, Status page with history | nothing | Compare |
| Starnikstarnik.comSee also Transparency alternatives to Starnik | 22/100 | 2 Data location stated, HTTPS enforced with HSTS | nothing | Compare |
| EnergyHubenergyhub.comSee also Transparency alternatives to EnergyHub | 17/100 | 2 Data location stated, Named privacy contact | nothing | Compare |
| Bidgelybidgely.comSee also Transparency alternatives to Bidgely | 13/100 | 2 HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| Lumenazalumenaza.deSee also Transparency alternatives to Lumenaza | 13/100 | 2 HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| Schleupenschleupen.deSee also Transparency alternatives to Schleupen | 13/100 | 2 HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| Soptimsoptim.deSee also Transparency alternatives to Soptim | 13/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | nothing | Compare |
| Wilkenwilken.deSee also Transparency alternatives to Wilken | 13/100 | 2 HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| Advanced Utilityadvancedutility.comSee also Transparency alternatives to Advanced Utility | 13/100 | 1 Data location stated | 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.