Transparency alternatives to Solarius
Other Solar design and proposal vendors we measure, sorted by how much we found at them and not at Solarius. This is a comparison of disclosure, not of features or fitness.
12 shown of 18 that differ from Solarius on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Solarius 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 “Found there, not found at Solarius” is the one that closes them.
| Vendor | Score | Found there, not found at Solarius | Found at Solarius, not found there | |
|---|---|---|---|---|
| Aurora Solaraurorasolar.comSee also Transparency alternatives to Aurora Solar | 57/100 | 6 Data processing agreement, Data location stated, Status page with history, +3 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| RatedPowerratedpower.comSee also Transparency alternatives to RatedPower | 30/100 | 3 Data location stated, Certifications named, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Solargrafsolargraf.comSee also Transparency alternatives to Solargraf | 29/100 | 3 Data location stated, Public pricing, Named privacy contact | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| OpenSolaropensolar.comSee also Transparency alternatives to OpenSolar | 17/100 | 2 Data location stated, Certifications named | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| SolarEdgesolaredge.comSee also Transparency alternatives to SolarEdge | 17/100 | 2 Data location stated, Named privacy contact | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Valentin Softwarevalentin-software.comSee also Transparency alternatives to Valentin Software | 17/100 | 2 Data location stated, Named privacy contact | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| GreenLancergreenlancer.comSee also Transparency alternatives to GreenLancer | 24/100 | 1 Data location stated | 1 security.txt (RFC 9116) | Compare |
| Bodhibodhisolar.comSee also Transparency alternatives to Bodhi | 17/100 | 1 Public pricing | 1 security.txt (RFC 9116) | Compare |
| SolarPlussolarplus.coSee also Transparency alternatives to SolarPlus | 9/100 | 1 Public pricing | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| PVcasepvcase.comSee also Transparency alternatives to PVcase | 4/100 | 1 Certifications named | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Sologosolo.ioSee also Transparency alternatives to Solo | 4/100 | 1 Certifications named | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Terabase Energyterabase.energySee also Transparency alternatives to Terabase Energy | 4/100 | 1 Named privacy contact | 2 HTTPS enforced with HSTS, 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.