Head to head · GPU compute · October 2026 research run
Crusoe Cloud vs Thunder Compute
Crusoe Cloud scores 63.4 (B) on agent readiness against Thunder Compute's 56.1 (C), and leads in 5 of 7 scored categories. Both do gpu compute.
Best GPU and serverless compute for AI workloads · All 167 gpu compute comparisons
Which one, for what
Good for Teams that want whole GPU machines or clusters with managed Kubernetes or Slurm in the US, Iceland or Norway, under an SLA, and are content to manage lifecycles themselves.
Ahead on
- Schema & documentation, 79 against 70
- Security & auth, 74 against 51
- Payments & pricing, 30 against 20
- Transparency & trust, 77 against 64
Also in its favour
- Runs on your own machine
Watch for
No idempotency key or safe-retry guidance was found for create and delete calls, which return asynchronous operations to poll.
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.
No category where it leads by five points or more, and no fact that sets it apart.
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 this run | Crusoe Cloud | Thunder Compute | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 66 | 65 | Crusoe Cloud +1 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 79 | 70 | Crusoe Cloud +9 |
| Agent ergonomics | 13%16.2 | 45 | 48 | Thunder Compute +3 |
| Security & auth | 14%17.5 | 74 | 51 | Crusoe Cloud +23 |
| Payments & pricing | 10%12.5 | 30 | 20 | Crusoe Cloud +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 76 | 79 | Thunder Compute +3 |
| Transparency & trust | 7%8.8 | 77 | 64 | Crusoe Cloud +13 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 63.4 · B | 56.1 · C |
Facts side by side
| Fact | Crusoe Cloud | Thunder Compute |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Crusoe | Thunder Compute |
| Hosted endpoint | https://api.cloud.crusoe.ai/v1 | https://api.thundercompute.com:8443/v1 |
| Transports | HTTP, stdio | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Pay per use |
| Price for gpu compute | not published | $0.219 per GB per month |
| x402 | no | no |
| Licence | Proprietary service under the Crusoe Cloud Platform Terms of Service. The Go client and the MCP server package are MIT. The CLI ships as binaries, and no licence file was found in the Terraform provider repository | Proprietary service under Thunder Compute's Terms and Conditions. The tnr CLI on GitHub is MIT |
| Tools exposed | 41 | 28 |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.github.Thunder-Compute/thunder-compute |
| Last release | 2026-10-08 | 2026-09-16 |
| Terms last updated | couldn't be read | 2026-09-28 |
| Privacy policy last updated | couldn't be read | 2026-09-28 |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | not found in the text |
| Terms restrict benchmarking | couldn't be read | yes |
| Terms or service can change without notice | couldn't be read | yes |
| Arbitration or class-action waiver | couldn't be read | yes |
| Popularity | 7 npm/wk | 34 stars |
Verdicts
Crusoe Cloud
The v1 REST API has a published OpenAPI description, Markdown docs, HMAC-signed keys, reader roles and a 90-day audit log, with on-demand GPU prices public. No idempotency keys or control-plane rate limits were found, spot and B200 prices go through sales, and a storage outage in eu-norway1 lasted about four hours on 29 September 2026.
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
Crusoe Cloud
- Sign every request. Build the payload from path, sorted query string, verb and
X-Crusoe-Timestamp, HMAC-SHA256 it with the base64url-decoded secret, and sendAuthorization: Bearer 1.0:<access_key_id>:<signature>. - Use
https://api.cloud.crusoe.ai/v1. Some docs pages and the MCP server still nameapi.crusoecloud.comand/v1alpha5. - Creates, updates and deletes return an operation. Poll the matching operations endpoint for
state, and list existing resources by name before retrying a create, because no idempotency key was found. - Managed AI uses separate Intelligence API keys and hosts,
api.inference.crusoecloud.comfor OpenAI-compatible calls andapi.intelligence.crusoecloud.comfor files and fine-tuning jobs. - Delete a VM and its disks to stop charges. A stopped on-demand VM is not billed for compute, but its 128 GB OS disk still bills at $0.08 a GiB-month.
Thunder Compute
- Call
GET /v2/statusor theget_availabilitytool before creating an instance. Availability can change before launch, and creation fails when a type is sold out. - List instances before retrying a failed create, because the call has no idempotency key.
- Pass
public_keyon create. If omitted, the response carries a generated private key that is returned once. - To pause work, create a snapshot, delete the instance and later create a new instance from the snapshot. Snapshot storage keeps billing until deleted.
- For headless use set
TNR_API_TOKENto a token from the console. The MCP server needs a browser sign-in on first connection.
Questions
Which is better for AI agents, Crusoe Cloud or Thunder Compute?
Crusoe Cloud scores 63.4 (B) on agent readiness against Thunder Compute's 56.1 (C), and leads in 5 of 7 scored categories.
Do Crusoe Cloud and Thunder Compute need an API key?
Crusoe Cloud needs an API key. Thunder Compute takes an API key or an OAuth sign-in.
Can an agent call Crusoe Cloud and Thunder Compute without installing anything?
Yes. Crusoe Cloud has a hosted endpoint at https://api.cloud.crusoe.ai/v1 and Thunder Compute at https://api.thundercompute.com:8443/v1.
Other comparisons with Crusoe Cloud or Thunder Compute
- Baseten vs Crusoe Cloud
- Baseten vs Thunder Compute
- Beam vs Crusoe Cloud
- Beam vs Thunder Compute
- Cerebrium vs Crusoe Cloud
- Cerebrium vs Thunder Compute
- CoreWeave vs Crusoe Cloud
- CoreWeave vs Thunder Compute
- Crusoe Cloud vs Hugging Face Inference Endpoints
- Crusoe Cloud vs Hyperbolic
- Crusoe Cloud vs Koyeb
- Crusoe Cloud vs Lambda Cloud
- Crusoe Cloud vs Massed Compute
- Crusoe Cloud vs Modal
- Crusoe Cloud vs Nebius AI Cloud
- Crusoe Cloud vs Northflank
- Crusoe Cloud vs Replicate Deployments
- Crusoe Cloud vs Runpod
- Crusoe Cloud vs Vast.ai
- Crusoe Cloud vs Verda
- Hugging Face Inference Endpoints vs Thunder Compute
- Hyperbolic vs Thunder Compute
- Koyeb vs Thunder Compute
- Lambda Cloud vs Thunder Compute
- Massed Compute vs Thunder Compute
- Modal vs Thunder Compute
- Nebius AI Cloud vs Thunder Compute
- Northflank vs Thunder Compute
- Replicate Deployments vs Thunder Compute
- Runpod vs Thunder Compute
- Thunder Compute vs Vast.ai
- Thunder Compute vs Verda
Machine-readable
- This page as Markdown
/compare/crusoe-cloud-vs-thunder-compute.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/crusoe-cloud.json·/api/v1/tools/thunder-compute.json - From a terminal
anchor compare crusoe-cloud thunder-compute(the CLI) - Over MCP
compare_tools {"a": "crusoe-cloud", "b": "thunder-compute"}at/mcp, no key