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