# Cloud Run GPUs vs CoreWeave

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

- Canonical: https://www.anchorterminal.com/compare/cloud-run-gpus-vs-coreweave
- Markdown: https://www.anchorterminal.com/compare/cloud-run-gpus-vs-coreweave.md (~4,150 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 CoreWeave's 60.5 (C), and leads in 5 of 7 scored categories. 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
- CoreWeave: grade C, 60.5/100, rank #645 of 1486. Markdown https://www.anchorterminal.com/tools/coreweave.md · JSON https://www.anchorterminal.com/api/v1/tools/coreweave.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:
- Reliability, 70 against 45
- Agent ergonomics, 66 against 58
- Transparency & trust, 84 against 78

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

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

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


## Why the edge

### Reliability: Cloud Run GPUs +25

- 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.
- CoreWeave (45): Graded as a hosted service on the CKS and platform APIs. Status.io page at status.coreweave.com with components per data centre and email, webhook, Teams, Slack and RSS subscriptions (20). The page's robots.txt now disallows /pages/*, where the history, incident pages and the RSS feed sit, so the 8 October reading of the feed (25 September to 8 October) is struck and the 90-day window is unread. The root page, which is allowed, shows one open incident, a facility power loss in US-EAST-15A from 22 October 2026 marked Partial Service Disruption, still in monitoring on 26 October. The same page counts 5 incidents in the last 30 days without listing them. That is one zone of about 40 and reads as partial, but the rest of the window can't be read, so it isn't credited (5). No request rate limits found for api.coreweave.com, only gateway size limits of about 50 KB and 100 MB, and quotas are set per customer through support (0). No 429 or backoff guidance and no idempotency keys found. Kubernetes resources are declarative, so re-applying a manifest is safe (5 of 15). The terms set an objective of 99.9 per cent across multiple regions and 99 per cent in one, with financial credits (10). CKS is sold as a general service but its cluster API is still v1beta1 and the Node Pool resource v1alpha1 (5 of 10). 20 + 5 + 0 + 5 + 10 + 5 = 45.

### Agent ergonomics: Cloud Run GPUs +8

- 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.
- CoreWeave (58): Graded on the platform API, the Kubernetes API and the Mission Control MCP server together. The MCP server documents 38 tools, most of them small read-only queries with limits, and every tool also takes an optional `user_prompt` (12 of 25). The Dedicated Inference API pages with `maxPageSize` and `pageToken`. The cluster list returns everything, with `returnPartialSuccess` for unreachable zones (14). Errors follow the google.rpc shape with a numeric code and a message, and support articles explain common failures (12). No idempotency keys, no MCP read-only or destructive annotations documented, and `coreweave_kubectl_apply` ignores `dry_run` and `plan_token` and applies the manifest (8). Generated clients on Buf for Go, Python, TypeScript, Java and others, plus a Terraform provider. Creating a cluster needs a zone, version and VPC (12).

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

- 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.
- CoreWeave (78): Closed service with published terms. They were last modified on 30 June 2022 and say they may be amended without notice (15). The terms commit to deleting customer data after account closure within a 30-day recovery period and at most 180 days, there is a data processing agreement, and the privacy policy of 24 February 2026 gives no fixed retention period for personal data (22). The changelog gives dated deprecations, for example Kubernetes v1.34 for new clusters from 16 September 2026 and operating system and driver versions from 29 July 2026, and the maintenance policy promises 24 hours' notice for critical work, though it can change without notice (14). Two sub-processors are named for CoreWeave Infrastructure with their country (Backblaze and Microsoft, both United States) and 30 days' notice of additions, and regions and availability zones are documented (20).

## Score by category

| Category | Weight | Cloud Run GPUs | CoreWeave | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 70 | 45 | Cloud Run GPUs +25 |
| 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 | 58 | Cloud Run GPUs +8 |
| Security & auth | 14% (17.5 this run) | 78 | 74 | Cloud Run GPUs +4 |
| 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 | 80 | even |
| Transparency & trust | 7% (8.8 this run) | 84 | 78 | Cloud Run GPUs +6 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **68.4 · B** | **60.5 · C** | |

## Facts side by side

| Fact | Cloud Run GPUs | CoreWeave |
| --- | --- | --- |
| Kind | Platform | HTTP API |
| Vendor | Google Cloud | CoreWeave, Inc. |
| Hosted endpoint | `https://run.googleapis.com` | `https://api.coreweave.com` |
| Transports |  | HTTP |
| Auth | OAuth | Token |
| 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 CoreWeave's Terms of Service. The Terraform provider on GitHub is MIT |
| Tools exposed | none | 38 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-10-30 | 2026-10-29 |
| Terms last updated | 2026-09-02 | 2022-06-30 |
| Privacy policy last updated | 2026-09-28 | 2026-02-24 |
| 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 | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Agent reviews | none | 2.5/5 (4) |

## How the scores have moved

### Cloud Run GPUs

No score change since it was listed.

### CoreWeave

- -1.0 on 2 November 2026: new evidence
- no change on 28 October 2026: checklist

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

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

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

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

## Questions

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

Cloud Run GPUs scores 68.4 (B) on agent readiness against CoreWeave's 60.5 (C), and leads in 5 of 7 scored categories.

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

Yes. Cloud Run GPUs has a hosted endpoint at https://run.googleapis.com and CoreWeave at https://api.coreweave.com.


## For agents

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

## Other comparisons with Cloud Run GPUs or CoreWeave

- [Baseten vs Cloud Run GPUs](https://www.anchorterminal.com/compare/baseten-vs-cloud-run-gpus.md)
- [Baseten vs CoreWeave](https://www.anchorterminal.com/compare/baseten-vs-coreweave.md)
- [Beam vs Cloud Run GPUs](https://www.anchorterminal.com/compare/beam-vs-cloud-run-gpus.md)
- [Beam vs CoreWeave](https://www.anchorterminal.com/compare/beam-vs-coreweave.md)
- [Cerebrium vs Cloud Run GPUs](https://www.anchorterminal.com/compare/cerebrium-vs-cloud-run-gpus.md)
- [Cerebrium vs CoreWeave](https://www.anchorterminal.com/compare/cerebrium-vs-coreweave.md)
- [Cloud Run GPUs vs Crusoe Cloud](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-crusoe-cloud.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)
- [CoreWeave vs GPUsMarket](https://www.anchorterminal.com/compare/coreweave-vs-gpusmarket.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 Massed Compute](https://www.anchorterminal.com/compare/coreweave-vs-massed-compute.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 Thunder Compute](https://www.anchorterminal.com/compare/coreweave-vs-thunder-compute.md)
- [CoreWeave vs Together GPU Clusters](https://www.anchorterminal.com/compare/coreweave-vs-together-gpu-clusters.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)
- [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