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