# Cloud Run GPUs vs Crusoe Cloud (slim)

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

- Full: https://www.anchorterminal.com/compare/cloud-run-gpus-vs-crusoe-cloud.md (~4,700 tokens) · this version ~2,430 tokens · JSON https://www.anchorterminal.com/compare/cloud-run-gpus-vs-crusoe-cloud.json · canonical https://www.anchorterminal.com/compare/cloud-run-gpus-vs-crusoe-cloud
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

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: B 68.4, rank #288 of 1486 · https://www.anchorterminal.com/tools/cloud-run-gpus.min.md
- Crusoe Cloud: B 62.4, rank #555 of 1486 · https://www.anchorterminal.com/tools/crusoe-cloud.min.md
- Cloud Run GPUs, 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 No incidents deducted, where Crusoe Cloud loses 3 points for them.
- Crusoe Cloud, 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 Runs on your own machine.

| Category | Cloud Run GPUs | Crusoe Cloud |
| --- | --- | --- |
| Reliability (16%) | 70 | 76 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 81 | 79 |
| Agent ergonomics (13%) | 66 | 45 |
| Security & auth (14%) | 78 | 74 |
| Payments & pricing (10%) | 20 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 80 | 76 |
| Transparency & trust (7%) | 84 | 77 |

| Fact (where they differ) | 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 |
| 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) |

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