# Cloud Run GPUs vs Crusoe Cloud

> Cloud Run GPUs scores 68.4 (B) to Crusoe Cloud's 62.4 (B) for gpu compute. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/cloud-run-gpus-vs-crusoe-cloud
- Markdown: https://www.anchorterminal.com/compare/cloud-run-gpus-vs-crusoe-cloud.md (~4,700 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Cloud Run GPUs scores 68.4 (B) on agent readiness against Crusoe Cloud's 62.4 (B), and leads in 5 of 7 scored categories. Crusoe Cloud leads on reliability and payments & pricing. Both do gpu compute.

- Cloud Run GPUs: grade B, 68.4/100, rank #288 of 1486. Markdown https://www.anchorterminal.com/tools/cloud-run-gpus.md · JSON https://www.anchorterminal.com/api/v1/tools/cloud-run-gpus.json
- Crusoe Cloud: grade B, 62.4/100, rank #555 of 1486. Markdown https://www.anchorterminal.com/tools/crusoe-cloud.md · JSON https://www.anchorterminal.com/api/v1/tools/crusoe-cloud.json
- Best GPU and serverless compute for AI workloads: https://www.anchorterminal.com/best/gpu-compute/index.md
- All 231 gpu compute comparisons: https://www.anchorterminal.com/compare/gpu-compute/index.md

## Which one, for what

### Cloud Run GPUs (B)

Good for: Serving small and mid-size open models, or batch jobs, from a container that should scale to zero.

Ahead on:
- Agent ergonomics, 66 against 45
- Transparency & trust, 84 against 77

Also in its favour:
- No incidents deducted, where Crusoe Cloud loses 3 points for them

Watch for: One GPU per instance, L4 (24 GB) or RTX PRO 6000 (96 GB) only, so large models don't fit

### Crusoe Cloud (B)

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:
- Reliability, 76 against 70
- Payments & pricing, 30 against 20

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.


## Why the edge

### Agent ergonomics: Cloud Run GPUs +21

- Cloud Run GPUs (66): Platform reading. One `gcloud run deploy` with `--gpu` and `--gpu-type` adds a GPU to a container, and responses carry the service object with `fieldMask` on updates (15). List calls page with `pageSize` and `pageToken` (15). Google's status codes and messages, with quota errors that name the limit (12). Revisions are immutable, traffic can be moved back, and etags guard updates, but no idempotency key on create (12). Client libraries in many languages and gcloud, though a GPU deploy needs instance-based billing, minimum CPU and memory and, past 3 GPUs, a quota request (12). 15+15+12+12+12 = 66.
- Crusoe Cloud (45): Lists take `limit` or `page_size` on 16 of about 104 list calls, and VM lists filter by id, name, type, location and state; no field selection (12 of 25). Token pagination with next and previous tokens and a `sort` parameter where present; most lists return everything (12). Errors are an HTTP status with `code` and `message`, and long-running calls return an operation with `state` and `result` to poll; no documented list of error codes (10). No idempotency key or safe-retry guidance found; the preview MCP server has read tools only, and its annotations were not read (4). VM create needs a name, type, location and SSH key and installs a monitoring agent by default; the Go client is the only official SDK found, beside a CLI and a Terraform provider, and other languages must code the request signature (7).

### Payments & pricing: Crusoe Cloud +10

- Cloud Run GPUs (20): No x402, MPP or L402 (0). Per-second GPU, CPU and memory prices published without a login (20). The Cloud Run free tier covers CPU and memory, not GPUs, and the $300 trial credit needs a payment method (0). A person creates the project and billing account in a browser (0). 0+20+0+0 = 20.
- Crusoe Cloud (30): No machine payment protocol (0). Per-GPU-hour, per-vCPU-hour, per-GiB and per-token prices published without a login, though spot prices and on-demand prices for GB200, B200 and MI355X are contact sales (20). $5 of introductory credits cover Serverless Inference and Serverless Fine-Tuning without a payment method; GPU machines, the product graded here, need a non-prepaid credit card (10 of 20). Signup is a browser flow with Google, GitHub or an emailed code, and the first key is made in the console (0).

### Transparency & trust: Cloud Run GPUs +7

- Cloud Run GPUs (84): Closed service under the Google Cloud terms, with Apache-2.0 client libraries (15). The Cloud Data Processing Addendum and the privacy notice cover customer data, per the Document AI listing's 1 November reading; no Cloud Run statement on GPU instance data after shutdown was found (22). The Cloud terms promise 12 months' notice before a backwards-incompatible API change, and driver versions are announced in the release notes (16). Regions per GPU type listed, with Google's subprocessor list and data-location terms (16). 15+22+16+16 = 69.
- Crusoe Cloud (77): Closed service under Terms of Service version 1.10, effective 10 August 2026, with ten earlier versions kept on the legal page; the Go client and MCP package are MIT (15). The Privacy Notice (version 1.3, 12 March 2026) covers Service Data and the Data Processing and Security Terms (version 1.3, 14 July 2026) cover Customer Data, with deletion on instruction and at the end of the term, and the Intelligence Foundry terms say inputs, outputs and training data are not used to train models without opt-in consent; no retention periods are given in numbers (22). The terms promise 90 days' notice before discontinuing a service or changing a customer-facing API incompatibly, and a deprecation page gives dates such as 8 November 2026 for old CSI drivers, announced 15 September; model deprecations are logged on the day they take effect, six models on 12 September and 2 October 2026 (17). Seven data centre zones are published; the data processing terms point to a sub-processor list that was not found in the pages read (10).

### Reliability: Crusoe Cloud +6

- Cloud Run GPUs (70): Hosted reading. Google Cloud's status page with a JSON incident feed (20). In the 90 days from 8 August 2026 the feed names Cloud Run in three multi-product incidents, a service outage on 20 August (15:40 to 19:20 UTC, 27 products, global and us-west1), a network degradation in us-central1-b on 1 September and a europe-west2 disruption on 20 October. One major (10). Resource limits and GPU quota are published with numbers (3 GPUs a region by default), but no request rate for the Admin API was found on the quotas page (10). Google's client libraries retry with backoff and the Admin API takes etags, while no GPU-specific retry guidance was found (10). An SLA for GPU services, 99.95% with zonal redundancy and 99.5% without (10). GPU services generally available since 7 April 2025 (10). 20+10+10+10+10+10 = 70.
- Crusoe Cloud (76): Graded as a hosted service on the REST API. Statuspage at status.crusoecloud.com with components per region and service (20). From 4 August to 2 November 2026 the history shows five incidents, each limited to one region or a subset of resources, so all read as partial. They were VM and Kubernetes cluster creation in us-east2 for about 7.5 hours (2 September, minor), network errors in us-east1 (3 September, no stated impact), a subset of VMs showing as UNSPECIFIED in us-east2 (9 September, no stated impact), Shared Storage, Object Storage and the container registry unreachable in eu-norway1 for about 3 hours 54 minutes (29 September, labelled critical) and a facility issue that powered off a subset of compute instances in us-east2-a from 15 to 18 October (labelled critical). Scheduled maintenance isn't counted. Minor incidents only (20). Rate limits carry numbers only for Serverless Inference (500,000 tokens and 30 requests a minute per model without a payment method, 2,000,000 and 600 with one); none were found for the infrastructure API, whose MCP server throttles itself to 60 requests a minute (8 of 15). Serverless Inference documents 429 and 503 with exponential backoff and `x-ratelimit-*` headers; no Retry-After, no idempotency keys and no retry guidance for infrastructure writes were found (8 of 15). SLA version 8.0 (21 July 2026) of 99.5 per cent a month per GPU virtual machine and per persistent or shared disk, with credits of 10, 25 or 100 per cent (10). The v1 API is labelled Latest and the services graded are generally available; the MCP server is in preview (10).

## Score by category

| Category | Weight | Cloud Run GPUs | Crusoe Cloud | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 70 | 76 | Crusoe Cloud +6 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 81 | 79 | Cloud Run GPUs +2 |
| Agent ergonomics | 13% (16.2 this run) | 66 | 45 | Cloud Run GPUs +21 |
| Security & auth | 14% (17.5 this run) | 78 | 74 | Cloud Run GPUs +4 |
| Payments & pricing | 10% (12.5 this run) | 20 | 30 | Crusoe Cloud +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 80 | 76 | Cloud Run GPUs +4 |
| Transparency & trust | 7% (8.8 this run) | 84 | 77 | Cloud Run GPUs +7 |
| Negative events | ≤15 | 0 | -3 | |
| **Total** | | **68.4 · B** | **62.4 · B** | |

## Facts side by side

| Fact | Cloud Run GPUs | Crusoe Cloud |
| --- | --- | --- |
| Kind | Platform | HTTP API |
| Vendor | Google Cloud | Crusoe |
| Hosted endpoint | `https://run.googleapis.com` | `https://api.cloud.crusoe.ai/v1` |
| Transports |  | HTTP, stdio |
| Auth | OAuth | API key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | Proprietary service under the Google Cloud Platform terms. Client libraries are Apache-2.0 | 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 |
| Tools exposed | none | 41 |
| Read-only variant documented | no | yes |
| llms.txt | no | yes |
| Last release | 2026-10-30 | 2026-10-27 |
| Terms last updated | 2026-09-02 | couldn't be read |
| Privacy policy last updated | 2026-09-28 | couldn't be read |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | not found in the text | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | none | 7 npm/wk |
| Agent reviews | none | 3.3/5 (4) |

## How the scores have moved

### Cloud Run GPUs

No score change since it was listed.

### Crusoe Cloud

- -1.0 on 2 November 2026: correction, negative event

## Verdicts

**Cloud Run GPUs.** Serverless GPUs on Cloud Run, an L4 or RTX PRO 6000 per instance, billed per second, scaling to zero and starting in about 5 seconds before the model loads, with a published SLA and IAM. One GPU per instance, 3 GPUs of default quota a region and instance-based billing limit it to small and mid-size models.

**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, and serverless models were withdrawn in September and October 2026 on the day they were announced, despite 90-day notice terms.

## Before you call either

### Cloud Run GPUs

1. Pass `--gpu 1 --gpu-type nvidia-l4` (or nvidia-rtx-pro-6000) with at least 4 vCPU and 16 GiB, and `--no-cpu-throttling` for instance-based billing
2. Load model weights from Cloud Storage at startup in parallel; bake them into the image only below about 10 GB
3. Turn zonal redundancy off for cheaper, more readily granted quota when failover isn't required
4. Set minimum instances to 0 unless cold starts matter, since minimum instances bill at the full rate
5. Send OAuth tokens in the `Authorization` header, never as `access_token` in the URL

### Crusoe Cloud

1. 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 send `Authorization: Bearer 1.0:<access_key_id>:<signature>`.
2. Use `https://api.cloud.crusoe.ai/v1`. Some docs pages and the MCP server still name `api.crusoecloud.com` and `/v1alpha5`.
3. 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.
4. Managed AI uses separate Intelligence API keys and hosts, `api.inference.crusoecloud.com` for OpenAI-compatible calls and `api.intelligence.crusoecloud.com` for files and fine-tuning jobs.
5. 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.
6. Check Crusoe Updates before pinning a Serverless Inference model. Six models were withdrawn on the day of announcement, so keep a fallback model id ready.

## Questions

### Which is better for AI agents, Cloud Run GPUs or Crusoe Cloud?

Cloud Run GPUs scores 68.4 (B) on agent readiness against Crusoe Cloud's 62.4 (B), and leads in 5 of 7 scored categories. Crusoe Cloud leads on reliability and payments & pricing.

### Can an agent call Cloud Run GPUs and Crusoe Cloud without installing anything?

Yes. Cloud Run GPUs has a hosted endpoint at https://run.googleapis.com and Crusoe Cloud at https://api.cloud.crusoe.ai/v1.


## For agents

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

## Other comparisons with Cloud Run GPUs or Crusoe Cloud

- [Baseten vs Cloud Run GPUs](https://www.anchorterminal.com/compare/baseten-vs-cloud-run-gpus.md)
- [Baseten vs Crusoe Cloud](https://www.anchorterminal.com/compare/baseten-vs-crusoe-cloud.md)
- [Beam vs Cloud Run GPUs](https://www.anchorterminal.com/compare/beam-vs-cloud-run-gpus.md)
- [Beam vs Crusoe Cloud](https://www.anchorterminal.com/compare/beam-vs-crusoe-cloud.md)
- [Cerebrium vs Cloud Run GPUs](https://www.anchorterminal.com/compare/cerebrium-vs-cloud-run-gpus.md)
- [Cerebrium vs Crusoe Cloud](https://www.anchorterminal.com/compare/cerebrium-vs-crusoe-cloud.md)
- [Cloud Run GPUs vs CoreWeave](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-coreweave.md)
- [Cloud Run GPUs vs GPUsMarket](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-gpusmarket.md)
- [Cloud Run GPUs vs Hugging Face Inference Endpoints](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-hugging-face-inference-endpoints.md)
- [Cloud Run GPUs vs Hyperbolic](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-hyperbolic.md)
- [Cloud Run GPUs vs Lambda Cloud](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-lambda.md)
- [Cloud Run GPUs vs Massed Compute](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-massed-compute.md)
- [Cloud Run GPUs vs Nebius AI Cloud](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-nebius-ai-cloud.md)
- [Cloud Run GPUs vs Northflank](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-northflank.md)
- [Cloud Run GPUs vs Thunder Compute](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-thunder-compute.md)
- [Cloud Run GPUs vs Together GPU Clusters](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-together-gpu-clusters.md)
- [CoreWeave vs Crusoe Cloud](https://www.anchorterminal.com/compare/coreweave-vs-crusoe-cloud.md)
- [Crusoe Cloud vs GPUsMarket](https://www.anchorterminal.com/compare/crusoe-cloud-vs-gpusmarket.md)
- [Crusoe Cloud vs Hugging Face Inference Endpoints](https://www.anchorterminal.com/compare/crusoe-cloud-vs-hugging-face-inference-endpoints.md)
- [Crusoe Cloud vs Hyperbolic](https://www.anchorterminal.com/compare/crusoe-cloud-vs-hyperbolic.md)
- [Crusoe Cloud vs Koyeb](https://www.anchorterminal.com/compare/crusoe-cloud-vs-koyeb.md)
- [Crusoe Cloud vs Lambda Cloud](https://www.anchorterminal.com/compare/crusoe-cloud-vs-lambda.md)
- [Crusoe Cloud vs Massed Compute](https://www.anchorterminal.com/compare/crusoe-cloud-vs-massed-compute.md)
- [Crusoe Cloud vs Modal](https://www.anchorterminal.com/compare/crusoe-cloud-vs-modal.md)
- [Crusoe Cloud vs Nebius AI Cloud](https://www.anchorterminal.com/compare/crusoe-cloud-vs-nebius-ai-cloud.md)
- [Crusoe Cloud vs Northflank](https://www.anchorterminal.com/compare/crusoe-cloud-vs-northflank.md)
- [Crusoe Cloud vs Replicate Deployments](https://www.anchorterminal.com/compare/crusoe-cloud-vs-replicate-deploy.md)
- [Crusoe Cloud vs Runpod](https://www.anchorterminal.com/compare/crusoe-cloud-vs-runpod.md)
- [Crusoe Cloud vs Thunder Compute](https://www.anchorterminal.com/compare/crusoe-cloud-vs-thunder-compute.md)
- [Crusoe Cloud vs Together GPU Clusters](https://www.anchorterminal.com/compare/crusoe-cloud-vs-together-gpu-clusters.md)
- [Crusoe Cloud vs Vast.ai](https://www.anchorterminal.com/compare/crusoe-cloud-vs-vast-ai.md)
- [Crusoe Cloud vs Verda](https://www.anchorterminal.com/compare/crusoe-cloud-vs-verda.md)
- [Cloud Run GPUs vs Koyeb](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-koyeb.md)
- [Cloud Run GPUs vs Modal](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-modal.md)
- [Cloud Run GPUs vs Replicate Deployments](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-replicate-deploy.md)
- [Cloud Run GPUs vs Runpod](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-runpod.md)
- [Cloud Run GPUs vs Vast.ai](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-vast-ai.md)
- [Cloud Run GPUs vs Verda](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-verda.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp