Alternatives to CoreWeave
Other MLOps and model serving vendors we measure, sorted by how much they publish that CoreWeave does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 25 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 “publishes and CoreWeave does not” is the one that closes them.
| Vendor | Score | Publishes, and CoreWeave does not | CoreWeave publishes, and they do not | |
|---|---|---|---|---|
| Anyscaleanyscale.com | 61/100 | 4 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | 1 Status page with history | Compare |
| Basetenbaseten.co | 52/100 | 4 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | 2 Data location stated, Certifications named | Compare |
| H2O.aih2o.ai | 39/100 | 4 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | 3 Data location stated, Status page with history, Public pricing | Compare |
| Modalmodal.com | 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 |
| Nscalenscale.com | 39/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Notice before subprocessors change | 3 Data location stated, Public pricing, Certifications named | Compare |
| Nebiusnebius.com | 30/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | 2 Data location stated, Public pricing | Compare |
| Northern Datanortherndata.de | 30/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | 3 Status page with history, Public pricing, Certifications named | Compare |
| Dataikudataiku.com | 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.com | 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 |
| DataRobotdatarobot.com | 43/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 1 Certifications named | Compare |
| ClearMLclear.ml | 22/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 3 Data location stated, Status page with history, Certifications named | Compare |
| Fireworks AIfireworks.ai | 22/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 3 Data location stated, 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.