Transparency alternatives to Valohai
Other MLOps and model serving vendors we measure, sorted by how much we found at them and not at Valohai. This is a comparison of disclosure, not of features or fitness.
12 shown of 34 that differ from Valohai on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Valohai has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, 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 “Found there, not found at Valohai” is the one that closes them.
| Vendor | Score | Found there, not found at Valohai | Found at Valohai, not found there | |
|---|---|---|---|---|
| Superwisesuperwise.aiSee also Transparency alternatives to Superwise | 65/100 | 6 Subprocessor list, Data location stated, HTTPS enforced with HSTS, +3 | 1 Status page with history | Compare |
| H2O.aih2o.aiSee also Transparency alternatives to H2O.ai | 57/100 | 6 Data processing agreement, Data location stated, HTTPS enforced with HSTS, +3 | 2 Status page with history, Public pricing | Compare |
| Lightning AIlightning.aiSee also Transparency alternatives to Lightning AI | 65/100 | 5 Subprocessor list, Data location stated, HTTPS enforced with HSTS, +2 | 1 Certifications named | Compare |
| Anyscaleanyscale.comSee also Transparency alternatives to Anyscale | 61/100 | 5 Data processing agreement, Data location stated, HTTPS enforced with HSTS, +2 | 1 Status page with history | Compare |
| RunPodrunpod.ioSee also Transparency alternatives to RunPod | 52/100 | 5 Data processing agreement, HTTPS enforced with HSTS, security.txt (RFC 9116), +2 | 1 Status page with history | Compare |
| Nscalenscale.comSee also Transparency alternatives to Nscale | 52/100 | 4 Subprocessor list, Data location stated, HTTPS enforced with HSTS, +1 | 1 Public pricing | Compare |
| Vast.aivast.aiSee also Transparency alternatives to Vast.ai | 52/100 | 4 Data processing agreement, Data location stated, HTTPS enforced with HSTS, +1 | 1 Status page with history | Compare |
| Basetenbaseten.coSee also Transparency alternatives to Baseten | 43/100 | 4 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | 2 Status page with history, Certifications named | Compare |
| Nebiusnebius.comSee also Transparency alternatives to Nebius | 43/100 | 4 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 1 Public pricing | Compare |
| Modalmodal.comSee also Transparency alternatives to Modal | 39/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | 2 Status page with history, Certifications named | Compare |
| Unionunion.aiSee also Transparency alternatives to Union | 39/100 | 3 Data location stated, Uptime SLA with a figure, HTTPS enforced with HSTS | 1 Status page with history | Compare |
| Fireworks AIfireworks.aiSee also Transparency alternatives to Fireworks AI | 35/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 2 Status page with history, Certifications named | 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.