Transparency alternatives to Cloudflare
Other Cloud hosting vendors we measure, sorted by how much we found at them and not at Cloudflare. This is a comparison of disclosure, not of features or fitness.
12 shown of 34 that differ from Cloudflare on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Cloudflare has 6 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. The column “Found there, not found at Cloudflare” is the one that closes them.
| Vendor | Score | Found there, not found at Cloudflare | Found at Cloudflare, not found there | |
|---|---|---|---|---|
| Exoscaleexoscale.comSee also Transparency alternatives to Exoscale | 87/100 | 5 Data location stated, Status page with history, Certifications named, +2 | nothing | Compare |
| Renderrender.comSee also Transparency alternatives to Render | 74/100 | 3 Data location stated, Status page with history, Certifications named | nothing | Compare |
| Kinstakinsta.comSee also Transparency alternatives to Kinsta | 70/100 | 3 Subprocessor list, Status page with history, Uptime SLA with a figure | 1 Named privacy contact | Compare |
| DigitalOceandigitalocean.comSee also Transparency alternatives to DigitalOcean | 65/100 | 3 Subprocessor list, Status page with history, Certifications named | 1 HTTPS enforced with HSTS | Compare |
| Vercelvercel.comSee also Transparency alternatives to Vercel | 65/100 | 3 Status page with history, Certifications named, Uptime SLA with a figure | nothing | Compare |
| Aptibleaptible.comSee also Transparency alternatives to Aptible | 48/100 | 3 Status page with history, Certifications named, Uptime SLA with a figure | 3 security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact | Compare |
| Hetznerhetzner.comSee also Transparency alternatives to Hetzner | 48/100 | 3 Data location stated, Status page with history, No third-party tracking before consent | 3 Data processing agreement, Public pricing, Notice before subprocessors change | Compare |
| Scalewayscaleway.comSee also Transparency alternatives to Scaleway | 48/100 | 3 Status page with history, Uptime SLA with a figure, No third-party tracking before consent | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Fly.iofly.ioSee also Transparency alternatives to Fly.io | 39/100 | 3 Subprocessor list, Data location stated, Certifications named | 5 Data processing agreement, HTTPS enforced with HSTS, security.txt (RFC 9116), +2 | Compare |
| MacStadium Orkamacstadium.comSee also Transparency alternatives to MacStadium Orka | 39/100 | 3 Data location stated, Status page with history, Certifications named | 4 Data processing agreement, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | Compare |
| Clever Cloudclever-cloud.comSee also Transparency alternatives to Clever Cloud | 35/100 | 3 Data location stated, Status page with history, Certifications named | 4 Data processing agreement, Public pricing, HTTPS enforced with HSTS, +1 | Compare |
| Cloudwayscloudways.comSee also Transparency alternatives to Cloudways | 27/100 | 3 Status page with history, Certifications named, Uptime SLA with a figure | 4 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | 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.