Transparency alternatives to DigitalOcean
Other Cloud hosting vendors we measure, sorted by how much we found at them and not at DigitalOcean. This is a comparison of disclosure, not of features or fitness.
12 shown of 34 that differ from DigitalOcean on at least one criterion we measured for both. Public transparency score, not a product or security rating.
DigitalOcean has 4 gaps in what we could measure: Data location stated, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent. The column “Found there, not found at DigitalOcean” is the one that closes them.
| Vendor | Score | Found there, not found at DigitalOcean | Found at DigitalOcean, not found there | |
|---|---|---|---|---|
| Exoscaleexoscale.comSee also Transparency alternatives to Exoscale | 87/100 | 4 Data location stated, Uptime SLA with a figure, HTTPS enforced with HSTS, +1 | 1 Subprocessor list | Compare |
| Hetznerhetzner.comSee also Transparency alternatives to Hetzner | 48/100 | 3 Data location stated, HTTPS enforced with HSTS, No third-party tracking before consent | 5 Data processing agreement, Subprocessor list, Public pricing, +2 | Compare |
| Scalewayscaleway.comSee also Transparency alternatives to Scaleway | 48/100 | 3 Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent | 4 Data processing agreement, Subprocessor list, Certifications named, +1 | Compare |
| Renderrender.comSee also Transparency alternatives to Render | 74/100 | 2 Data location stated, HTTPS enforced with HSTS | 1 Subprocessor list | Compare |
| Kinstakinsta.comSee also Transparency alternatives to Kinsta | 70/100 | 2 Uptime SLA with a figure, HTTPS enforced with HSTS | 2 Certifications named, Named privacy contact | Compare |
| Vercelvercel.comSee also Transparency alternatives to Vercel | 65/100 | 2 Uptime SLA with a figure, HTTPS enforced with HSTS | 1 Subprocessor list | Compare |
| Aptibleaptible.comSee also Transparency alternatives to Aptible | 48/100 | 2 Uptime SLA with a figure, HTTPS enforced with HSTS | 4 Subprocessor list, security.txt (RFC 9116), Notice before subprocessors change, +1 | Compare |
| UpCloudupcloud.comSee also Transparency alternatives to UpCloud | 43/100 | 2 Data location stated, HTTPS enforced with HSTS | 5 Data processing agreement, Subprocessor list, Certifications named, +2 | Compare |
| Herokuheroku.comSee also Transparency alternatives to Heroku | 39/100 | 2 Data location stated, HTTPS enforced with HSTS | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | Compare |
| AccelByte Gaming Servicesaccelbyte.ioSee also Transparency alternatives to AccelByte Gaming Services | 35/100 | 2 Data location stated, No third-party tracking before consent | 6 Data processing agreement, Subprocessor list, Status page with history, +3 | Compare |
| WP Enginewpengine.comSee also Transparency alternatives to WP Engine | 35/100 | 2 Uptime SLA with a figure, HTTPS enforced with HSTS | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | Compare |
| Contabocontabo.comSee also Transparency alternatives to Contabo | 26/100 | 2 Data location stated, HTTPS enforced with HSTS | 7 Data processing agreement, Subprocessor list, Status page with history, +4 | 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.