Head to head · Compute gpu · October 2026 research run

CoreWeave vs Nebius AI Cloud

Nebius AI Cloud scores 67.2 (B) on agent readiness against CoreWeave's 61.5 (C), and leads in 4 of 7 scored categories. Both do compute gpu.

Which one, for what

CoreWeave C

Good for Teams that already run Kubernetes and need whole multi-GPU nodes or clusters for training and dedicated inference, with a contract and IAM.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

No self-serve route. CoreWeave's sales team approves an organisation and emails the activation link before a token can be created

Nebius AI Cloud B

Good for Teams that want whole GPU VMs or InfiniBand clusters in Europe, the UK, Israel or the US with IAM, Terraform and an SLA, and are content to manage endpoint lifecycles themselves.

Ahead on

  • Reliability, 57 against 50
  • Agent ergonomics, 77 against 58
  • Security & auth, 81 against 74

Also in its favour

  • Runs on your own machine

Watch for

Status page lists 14 incidents marked major between 14 July and 8 October 2026, including about 21 hours of partial degradation in us-central1 on 19 August

Score by category

CategoryWeight this runCoreWeaveNebius AI CloudEdge
Reliability16%205057Nebius AI Cloud +7
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27978CoreWeave +1
Agent ergonomics13%16.25877Nebius AI Cloud +19
Security & auth14%17.57481Nebius AI Cloud +7
Payments & pricing10%12.52020even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88082Nebius AI Cloud +2
Transparency & trust7%8.87777even
Negative events≤1500
Total61.5 · C67.2 · B

Facts side by side

FactCoreWeaveNebius AI Cloud
KindHTTP APIHTTP API
VendorCoreWeave, Inc.Nebius
Hosted endpointhttps://api.coreweave.comhttps://api.nebius.cloud
TransportsHTTPHTTP, stdio
AuthTokenOAuth or key
PricingPay per usePay per use
Price for compute gpunot published$1.35 per GPU-hour
x402nono
LicenceProprietary service under CoreWeave's Terms of Service. The Terraform provider on GitHub is MITProprietary service under the Nebius Services Agreement. The API definitions, the Go, Python and JavaScript SDKs and the MCP server on GitHub are MIT
Tools exposed38none
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-022026-10-07
Terms last updated2022-06-302026-09-28
Privacy policy last updated2026-02-242026-09-23
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularitynone4.1k npm/wk, 469k PyPI/wk

Verdicts

CoreWeave

Per-hour prices for 8-GPU H100, H200 and B200 nodes are public, the docs ship as Markdown with llms.txt and embedded OpenAPI specs, and IAM has read-only roles per service. An organisation must be approved by CoreWeave's sales team before any token exists, and no request rate limits were found in the reviewed documentation.

Nebius AI Cloud

One API definition generates the REST and gRPC interfaces, the CLI, Terraform provider and three SDKs, with a 602-operation OpenAPI document, X-Idempotency-Key and role-scoped service accounts. The status page lists 14 major incidents between 14 July and 8 October 2026, no request rate limits were found, and signup needs a browser and a card.

Before you call either

CoreWeave

  1. Create an API access token at console.coreweave.com/tokens with an expiry and send it as Authorization: Bearer to https://api.coreweave.com
  2. Add GPUs by applying a NodePool resource (compute.coreweave.com/v1alpha1) to a CKS cluster with instanceType and targetNodes. instanceType can't be changed afterwards
  3. Set targetNodes to 0 or delete the Node Pool when a job ends. Nodes are whole 8-GPU machines billed by the hour
  4. Never pass dry_run to the MCP tool coreweave_kubectl_apply expecting a preview. The reference says the parameter is ignored and the manifest is applied
  5. Use a separate Forge API key and https://api.inference.wandb.ai/v1 for Serverless Inference. A CoreWeave API access token doesn't work there

Nebius AI Cloud

  1. Use a service account with an authorised key, then exchange a five-minute RS256 JWT at https://auth.eu.nebius.com/oauth2/token/exchange for a 12-hour Bearer token
  2. Send X-Idempotency-Key with a random UUID on every create, update and delete, since a 504 can follow a call that succeeded
  3. Poll the returned operation (/ai/v1/endpoints/operations/{id}) until status is set; concurrent operations on one resource are not supported
  4. Stop or delete endpoints when idle. A stopped endpoint bills nothing, a stopped Devlab or VM still bills for its disk
  5. Check region support first. Serverless AI is absent from eu-south1 and us-north1, and each GPU platform exists in one to four regions
  6. Run the beta nebius/mcp-server with safe mode on (the default); nebius_cli_execute can run any CLI command when SAFE_MODE=false

Questions

Which is better for AI agents, CoreWeave or Nebius AI Cloud?

Nebius AI Cloud scores 67.2 (B) on agent readiness against CoreWeave's 61.5 (C), and leads in 4 of 7 scored categories.

Do CoreWeave and Nebius AI Cloud need an API key?

CoreWeave needs an access token. Nebius AI Cloud takes an API key or an OAuth sign-in.

Can an agent call CoreWeave and Nebius AI Cloud without installing anything?

Yes. CoreWeave has a hosted endpoint at https://api.coreweave.com and Nebius AI Cloud at https://api.nebius.cloud.

Other comparisons with CoreWeave or Nebius AI Cloud

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.