# CoreWeave vs Thunder Compute

> CoreWeave scores 61.5 (C) on agent readiness against Thunder Compute's 56.1 (C), and leads in 5 of 7 scored categories. Thunder Compute leads on reliability. Both do compute gpu. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/coreweave-vs-thunder-compute
- Markdown: https://www.anchorterminal.com/compare/coreweave-vs-thunder-compute.md (~2,650 tokens)
- Slim: https://www.anchorterminal.com/compare/coreweave-vs-thunder-compute.min.md (~680 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/coreweave-vs-thunder-compute.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-09

CoreWeave scores 61.5 (C) on agent readiness against Thunder Compute's 56.1 (C), and leads in 5 of 7 scored categories. Thunder Compute leads on reliability. Both do compute gpu.

- CoreWeave: grade C, 61.5/100, rank #421 of 842. Markdown https://www.anchorterminal.com/tools/coreweave.md · JSON https://www.anchorterminal.com/api/v1/tools/coreweave.json
- Thunder Compute: grade C, 56.1/100, rank #576 of 842. Markdown https://www.anchorterminal.com/tools/thunder-compute.md · JSON https://www.anchorterminal.com/api/v1/tools/thunder-compute.json

## 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.

Ahead on:
- Schema & documentation, 79 against 70
- Agent ergonomics, 58 against 48
- Security & auth, 74 against 51
- Transparency & trust, 77 against 64

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

### Thunder Compute (C)

Good for: Agents in coding tools that rent a single persistent GPU machine for development, fine-tuning or a model server, at low hourly prices and over MCP.

Ahead on:
- Reliability, 65 against 50

Watch for: No rate limits, 429 guidance or SLA were found in the reviewed documentation, and the terms disclaim availability


## Score by category

| Category | Weight | CoreWeave | Thunder Compute | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 50 | 65 | Thunder Compute +15 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 79 | 70 | CoreWeave +9 |
| Agent ergonomics | 13% (16.2 this run) | 58 | 48 | CoreWeave +10 |
| Security & auth | 14% (17.5 this run) | 74 | 51 | CoreWeave +23 |
| Payments & pricing | 10% (12.5 this run) | 20 | 20 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 80 | 79 | CoreWeave +1 |
| Transparency & trust | 7% (8.8 this run) | 77 | 64 | CoreWeave +13 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **61.5 · C** | **56.1 · C** | |

## Facts side by side

| Fact | CoreWeave | Thunder Compute |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | CoreWeave, Inc. | Thunder Compute |
| Hosted endpoint | `https://api.coreweave.com` | `https://api.thundercompute.com:8443/v1` |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | Token | OAuth or key |
| Pricing | Pay per use | Pay per use |
| Price for compute gpu | not published | $0.219 per GB per month |
| x402 | no | no |
| Licence | Proprietary service under CoreWeave's Terms of Service. The Terraform provider on GitHub is MIT | Proprietary service under Thunder Compute's Terms and Conditions. The `tnr` CLI on GitHub is MIT |
| Tools exposed | 38 | 28 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | `io.github.Thunder-Compute/thunder-compute` |
| Last release | 2026-10-02 | 2026-09-16 |
| Terms last updated | 2022-06-30 | 2026-09-28 |
| Privacy policy last updated | 2026-02-24 | 2026-09-28 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | none | 34 stars |

## 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.

**Thunder Compute.** The hosted MCP server signs in with OAuth and separate read and write scopes, and the REST API has a public OpenAPI 3.1 document with keyless price and availability endpoints. No rate limits, SLA or API changelog were found, instance creation has no idempotency key, and instances cannot be stopped, only deleted.

## 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

### Thunder Compute

1. Call `GET /v2/status` or the `get_availability` tool before creating an instance. Availability can change before launch, and creation fails when a type is sold out.
2. List instances before retrying a failed create, because the call has no idempotency key.
3. Pass `public_key` on create. If omitted, the response carries a generated private key that is returned once.
4. To pause work, create a snapshot, delete the instance and later create a new instance from the snapshot. Snapshot storage keeps billing until deleted.
5. For headless use set `TNR_API_TOKEN` to a token from the console. The MCP server needs a browser sign-in on first connection.

## Questions

### Which is better for AI agents, CoreWeave or Thunder Compute?

CoreWeave scores 61.5 (C) on agent readiness against Thunder Compute's 56.1 (C), and leads in 5 of 7 scored categories. Thunder Compute leads on reliability.

### Do CoreWeave and Thunder Compute need an API key?

CoreWeave needs an access token. Thunder Compute takes an API key or an OAuth sign-in.

### Can an agent call CoreWeave and Thunder Compute without installing anything?

Yes. CoreWeave has a hosted endpoint at https://api.coreweave.com and Thunder Compute at https://api.thundercompute.com:8443/v1.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/coreweave-vs-thunder-compute.json, and with the fewest tokens: https://www.anchorterminal.com/compare/coreweave-vs-thunder-compute.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "coreweave", "b": "thunder-compute"}`. From a terminal: `anchor compare coreweave thunder-compute`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/coreweave.json and https://www.anchorterminal.com/api/v1/tools/thunder-compute.json

## Other comparisons with CoreWeave or Thunder Compute

- [Baseten vs CoreWeave](https://www.anchorterminal.com/compare/baseten-vs-coreweave.md)
- [Baseten vs Thunder Compute](https://www.anchorterminal.com/compare/baseten-vs-thunder-compute.md)
- [Beam vs CoreWeave](https://www.anchorterminal.com/compare/beam-vs-coreweave.md)
- [Beam vs Thunder Compute](https://www.anchorterminal.com/compare/beam-vs-thunder-compute.md)
- [Cerebrium vs CoreWeave](https://www.anchorterminal.com/compare/cerebrium-vs-coreweave.md)
- [Cerebrium vs Thunder Compute](https://www.anchorterminal.com/compare/cerebrium-vs-thunder-compute.md)
- [CoreWeave vs Hugging Face Inference Endpoints](https://www.anchorterminal.com/compare/coreweave-vs-hugging-face-inference-endpoints.md)
- [CoreWeave vs Hyperbolic](https://www.anchorterminal.com/compare/coreweave-vs-hyperbolic.md)
- [CoreWeave vs Koyeb](https://www.anchorterminal.com/compare/coreweave-vs-koyeb.md)
- [CoreWeave vs Lambda Cloud](https://www.anchorterminal.com/compare/coreweave-vs-lambda.md)
- [CoreWeave vs Modal](https://www.anchorterminal.com/compare/coreweave-vs-modal.md)
- [CoreWeave vs Nebius AI Cloud](https://www.anchorterminal.com/compare/coreweave-vs-nebius-ai-cloud.md)
- [CoreWeave vs Northflank](https://www.anchorterminal.com/compare/coreweave-vs-northflank.md)
- [CoreWeave vs Replicate Deployments](https://www.anchorterminal.com/compare/coreweave-vs-replicate-deploy.md)
- [CoreWeave vs Runpod](https://www.anchorterminal.com/compare/coreweave-vs-runpod.md)
- [CoreWeave vs Vast.ai](https://www.anchorterminal.com/compare/coreweave-vs-vast-ai.md)
- [CoreWeave vs Verda](https://www.anchorterminal.com/compare/coreweave-vs-verda.md)
- [Hugging Face Inference Endpoints vs Thunder Compute](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-thunder-compute.md)
- [Hyperbolic vs Thunder Compute](https://www.anchorterminal.com/compare/hyperbolic-vs-thunder-compute.md)
- [Koyeb vs Thunder Compute](https://www.anchorterminal.com/compare/koyeb-vs-thunder-compute.md)
- [Lambda Cloud vs Thunder Compute](https://www.anchorterminal.com/compare/lambda-vs-thunder-compute.md)
- [Modal vs Thunder Compute](https://www.anchorterminal.com/compare/modal-vs-thunder-compute.md)
- [Nebius AI Cloud vs Thunder Compute](https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-thunder-compute.md)
- [Northflank vs Thunder Compute](https://www.anchorterminal.com/compare/northflank-vs-thunder-compute.md)
- [Replicate Deployments vs Thunder Compute](https://www.anchorterminal.com/compare/replicate-deploy-vs-thunder-compute.md)
- [Runpod vs Thunder Compute](https://www.anchorterminal.com/compare/runpod-vs-thunder-compute.md)
- [Thunder Compute vs Vast.ai](https://www.anchorterminal.com/compare/thunder-compute-vs-vast-ai.md)
- [Thunder Compute vs Verda](https://www.anchorterminal.com/compare/thunder-compute-vs-verda.md)