Transparency alternatives to Tensorlake
Other Cloud hosting vendors we measure, sorted by how much they publish that Tensorlake does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 34 that differ from Tensorlake on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Tensorlake has 8 gaps in what we could measure: Subprocessor list, Data location stated, Status page with history, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact. The column “publishes and Tensorlake does not” is the one that closes them.
| Vendor | Score | Publishes, and Tensorlake does not | Tensorlake publishes, and they do not | |
|---|---|---|---|---|
| Renderrender.com | 74/100 | 5 Data location stated, Status page with history, Certifications named, +2 | nothing | Compare |
| DigitalOceandigitalocean.com | 65/100 | 5 Subprocessor list, Status page with history, Certifications named, +2 | 1 HTTPS enforced with HSTS | Compare |
| Vercelvercel.com | 65/100 | 5 Status page with history, Certifications named, Uptime SLA with a figure, +2 | nothing | Compare |
| Clever Cloudclever-cloud.com | 35/100 | 5 Data location stated, Status page with history, Certifications named, +2 | 4 Data processing agreement, Public pricing, HTTPS enforced with HSTS, +1 | Compare |
| Kinstakinsta.com | 70/100 | 4 Subprocessor list, Status page with history, Uptime SLA with a figure, +1 | nothing | Compare |
| Fly.iofly.io | 48/100 | 4 Subprocessor list, Data location stated, Status page with history, +1 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | Compare |
| Scalewayscaleway.com | 43/100 | 4 Status page with history, No third-party tracking before consent, security.txt (RFC 9116), +1 | 2 Data processing agreement, Notice before subprocessors change | Compare |
| MacStadium Orkamacstadium.com | 39/100 | 4 Data location stated, Status page with history, Certifications named, +1 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | Compare |
| Hetznerhetzner.com | 35/100 | 4 Status page with history, No third-party tracking before consent, security.txt (RFC 9116), +1 | 3 Data processing agreement, Public pricing, Notice before subprocessors change | Compare |
| Railwayrailway.com | 52/100 | 3 Data location stated, Certifications named, Named privacy contact | 1 HTTPS enforced with HSTS | Compare |
| Aptibleaptible.com | 48/100 | 3 Status page with history, Certifications named, Uptime SLA with a figure | 1 Notice before subprocessors change | Compare |
| Netlifynetlify.com | 43/100 | 3 Status page with history, Certifications named, Named privacy contact | 1 Data processing agreement | 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.