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