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