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