Transparency alternatives to Wallaroo
Other MLOps and model serving vendors we measure, sorted by how much they publish that Wallaroo does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 35 that differ from Wallaroo on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Wallaroo has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, 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. The column “publishes and Wallaroo does not” is the one that closes them.
| Vendor | Score | Publishes, and Wallaroo does not | Wallaroo publishes, and they do not | |
|---|---|---|---|---|
| RunPodrunpod.io | 52/100 | 6 Data processing agreement, Public pricing, Certifications named, +3 | 1 Data location stated | Compare |
| Basetenbaseten.co | 52/100 | 5 Data processing agreement, Status page with history, Public pricing, +2 | 1 Data location stated | Compare |
| Anyscaleanyscale.com | 48/100 | 5 Data processing agreement, Public pricing, Certifications named, +2 | 1 Data location stated | Compare |
| Vast.aivast.ai | 52/100 | 4 Data processing agreement, Public pricing, Certifications named, +1 | nothing | Compare |
| Paperspacepaperspace.com | 43/100 | 4 Status page with history, Public pricing, Certifications named, +1 | 1 Named privacy contact | Compare |
| H2O.aih2o.ai | 39/100 | 4 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +1 | 1 Data location stated | Compare |
| Modalmodal.com | 39/100 | 4 Data processing agreement, Public pricing, HTTPS enforced with HSTS, +1 | 2 Data location stated, Named privacy contact | Compare |
| Nscalenscale.com | 39/100 | 4 Subprocessor list, Status page with history, HTTPS enforced with HSTS, +1 | 2 Data location stated, Named privacy contact | Compare |
| Unionunion.ai | 39/100 | 4 Public pricing, Certifications named, Uptime SLA with a figure, +1 | 1 Named privacy contact | Compare |
| Cometcomet.com | 30/100 | 4 Status page with history, Public pricing, Certifications named, +1 | 2 Data location stated, Named privacy contact | Compare |
| Nebiusnebius.com | 30/100 | 4 Status page with history, Certifications named, HTTPS enforced with HSTS, +1 | 1 Data location stated | Compare |
| CoreWeavecoreweave.com | 35/100 | 3 Status page with history, Public pricing, Certifications named | 1 Named privacy contact | 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.