Transparency alternatives to localhost.run
Other Network connectivity vendors we measure, sorted by how much they publish that localhost.run does not. This is a comparison of disclosure, not of features or fitness.
6 shown of 6 that differ from localhost.run on at least one criterion we measured for both. Public transparency score, not a product or security rating.
localhost.run has 12 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and localhost.run does not” is the one that closes them.
| Vendor | Score | Publishes, and localhost.run does not | localhost.run publishes, and they do not | |
|---|---|---|---|---|
| ngrokngrok.com | 70/100 | 8 Data processing agreement, Data location stated, Status page with history, +5 | nothing | Compare |
| Pangolinpangolin.net | 57/100 | 7 Data processing agreement, Public pricing, Uptime SLA with a figure, +4 | nothing | Compare |
| ZeroTier Centralzerotier.com | 39/100 | 5 Data processing agreement, Public pricing, Certifications named, +2 | nothing | Compare |
| Netmakernetmaker.io | 17/100 | 2 Public pricing, HTTPS enforced with HSTS | nothing | Compare |
| Packetriotpacketriot.com | 9/100 | 1 Public pricing | nothing | Compare |
| Pinggypinggy.io | 9/100 | 1 HTTPS enforced with HSTS | 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.