# Cloud Run GPUs vs Runpod

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

- Canonical: https://www.anchorterminal.com/compare/cloud-run-gpus-vs-runpod
- Markdown: https://www.anchorterminal.com/compare/cloud-run-gpus-vs-runpod.md (~4,000 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 Runpod's 55.6 (C), and leads in 4 of 7 scored categories. Both do compute serverless.

- 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
- Runpod: grade C, 55.6/100, rank #859 of 1486. Markdown https://www.anchorterminal.com/tools/runpod.md · JSON https://www.anchorterminal.com/api/v1/tools/runpod.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 57
- Security & auth, 78 against 67
- Transparency & trust, 84 against 64

Also in its favour:
- No incidents deducted, where Runpod loses 6 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

### Runpod (C)

Good for: Cost-sensitive inference and batch work that wants the widest GPU choice, from consumer cards to B300, with an MCP control plane.

Also in its favour:
- Runs on your own machine

Watch for: Data-centre outages of 6 to 24 hours in each of July, August and September 2026, per the 1 October check


## Why the edge

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

- 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.
- Runpod (64): Per the 1 October check, not re-read on 4 November (terms bar automated access to runpod.io). Closed service under Delaware terms; the Python SDK is MIT (20). Sync results are kept 1 minute and async 30 minutes, and the docs claim GDPR compliance for EU regions, but no retention periods for pod disks or volumes after deletion and the DPA sits behind trust-centre access (15). Dated notices, REST v1 retiring on 15 November 2026 (announced 18 August) and GraphQL in early 2027; one model endpoint got two weeks' notice (15). 31 regions named with data-centre codes; subprocessor list not found (10).

### Reliability: Cloud Run GPUs +13

- 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.
- Runpod (57): Better Stack page at uptime.runpod.io with per-service and per-region history, per the 1 October check, not re-read on 4 November (Runpod's terms bar automated access to runpod.io and its subdomains) (20). Incident line kept at 0. The 1 October reading counted several majors, among them US-IL-1 without power for 6 hours 10 minutes on 14 and 15 August and serverless API errors for 1 hour 25 minutes on 6 September. The window since 1 October is unread, so the recorded award stands (0). The REST v2 OpenAPI file, in the copy Runpod keeps in its MCP repository (synced with production on 27 October), says limits are per user across every `/v2` route, with minute, hour and day windows, and gives `"minute";q=180;w=60, "hour";q=3600;w=3600, "day";q=43200;w=86400` as the policy header (15). The same file documents 429 with `Retry-After` and `RateLimit` headers, and the Python SDK's error guide (2.1.0, 3 November) honours `Retry-After`, backs off with jitter and does not retry other errors because a failed response can follow a successful mutation. Safe-retry guidance with no idempotency keys (12). No SLA found (0). Serverless and REST v2 are GA; batch jobs are beta (10). 20 + 0 + 15 + 12 + 0 + 10 = 57.

### Security & auth: Cloud Run GPUs +11

- Cloud Run GPUs (78): OAuth 2.0 tokens from service accounts under IAM. Google's APIs accept `access_token` as a query parameter, the 10-point deduction other Google API listings take (20). IAM roles separate viewing, deploying and invoking, and services can require IAM authentication for every call (16). The platform runs your own container and returns its output (10). Cloud Audit Logs record Admin API calls, and request logs go to Cloud Logging (15). Google's vulnerability reward programme, security.txt and certifications (17). 20+16+10+15+17 = 78.
- Runpod (67): API keys can be All, Read Only or Restricted per serverless endpoint, and can be disabled or deleted; the hosted MCP signs in with OAuth. The GraphQL docs still show the key as `?api_key=` in the URL per 1 October, which costs 10 (20). Read-only keys and per-endpoint restrictions, and the REST v2 file names a read or write scope for each operation; no confirmation for destructive calls found (15). Runs your own containers and returns their output (10). REST v2 now lists `GET /v2/audit-logs` (scope `audit:read`), an account or organisation audit trail of who acted on which resource, with filters and a retention window; no per-call API request log (12). security.txt valid until 31 January 2027, and the trust centre lists SOC 2 Type 2, SOC 3, ISO 27001 and HIPAA, per 1 October; no bug bounty, and osv.dev lists no advisory for runpod (10). 20 + 15 + 10 + 12 + 10 = 67.

## Score by category

| Category | Weight | Cloud Run GPUs | Runpod | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 70 | 57 | Cloud Run GPUs +13 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 81 | 81 | even |
| Agent ergonomics | 13% (16.2 this run) | 66 | 62 | Cloud Run GPUs +4 |
| Security & auth | 14% (17.5 this run) | 78 | 67 | Cloud Run GPUs +11 |
| 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 | 82 | Runpod +2 |
| Transparency & trust | 7% (8.8 this run) | 84 | 64 | Cloud Run GPUs +20 |
| Negative events | ≤15 | 0 | -6 | |
| **Total** | | **68.4 · B** | **55.6 · C** | |

## Facts side by side

| Fact | Cloud Run GPUs | Runpod |
| --- | --- | --- |
| Kind | Platform | HTTP API |
| Vendor | Google Cloud | Runpod |
| Hosted endpoint | `https://run.googleapis.com` | `https://api.runpod.ai/v2` |
| Transports |  | HTTP, Streamable HTTP, stdio |
| Auth | OAuth | OAuth or key |
| Pricing | Pay per use | Pay per use |
| Price for compute serverless | not published | $0.69 per GPU-hour |
| x402 | no | no |
| Licence | Proprietary service under the Google Cloud Platform terms. Client libraries are Apache-2.0 | MIT |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-10-30 | 2026-11-03 |
| Terms last updated | 2026-09-02 | 2026-03-24 |
| Privacy policy last updated | 2026-09-28 | 2025-08-07 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | none | 314 stars, 22k npm/wk |
| Agent reviews | none | 3/5 (2) |

## How the scores have moved

### Cloud Run GPUs

No score change since it was listed.

### Runpod

- +2.0 on 4 November 2026 (D to C): product, new evidence, negative event
- +0.1 on 27 October 2026: checklist
- -0.2 on 8 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.

**Runpod.** Per-second billing across more than a dozen serverless GPU classes, with a REST v2 contract that documents rate limits, 429 handling and cursor pagination. Data-centre outages ran 6 to 24 hours in July, August and September 2026, and two minor releases in late October and early November changed CLI and MCP behaviour without notice.

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

### Runpod

1. Create a Restricted or Read Only key per endpoint for the agent, not an All key
2. Use REST v2 at api.runpod.io/v2 with a Bearer header; avoid GraphQL, which puts the key in the URL, and read quotas from the `RateLimit-Policy` header
3. Fetch `/run` results within 30 minutes and `/runsync` results within 1 minute, or they're gone
4. Call `/retry` on a failed job ID rather than submitting a duplicate job
5. Check `/health` before relying on an endpoint idle for a week, since max workers drop to 0
6. Set `RUNPOD_API_KEY` or pass `--api-key` when running `rp login` without a terminal; since `runpod` 2.1.0 it fails fast otherwise

## Questions

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

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

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

Yes. Cloud Run GPUs has a hosted endpoint at https://run.googleapis.com and Runpod at https://api.runpod.ai/v2.


## For agents

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

## Other comparisons with Cloud Run GPUs or Runpod

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