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