# Cloud Run GPUs vs Massed Compute

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

- Canonical: https://www.anchorterminal.com/compare/cloud-run-gpus-vs-massed-compute
- Markdown: https://www.anchorterminal.com/compare/cloud-run-gpus-vs-massed-compute.md (~5,450 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 Massed Compute's 42.6 (E), and leads in 6 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
- Massed Compute: grade E, 42.6/100, rank #1256 of 1486. Markdown https://www.anchorterminal.com/tools/massed-compute.md · JSON https://www.anchorterminal.com/api/v1/tools/massed-compute.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 20
- Schema & documentation, 81 against 69
- Agent ergonomics, 66 against 56
- Security & auth, 78 against 61
- Maintenance & community, 80 against 51
- Transparency & trust, 84 against 64

Also in its favour:
- No incidents deducted, where Massed Compute loses 5 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

### Massed Compute (E)

Good for: Agents that rent whole GPU VMs by the hour for training, fine-tuning or a model server and want a small MCP tool set with a read-only mode.

Watch for: No status page, incident history or security.txt was found on any of the vendor's hosts


## Why the edge

### Reliability: Cloud Run GPUs +50

- 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.
- Massed Compute (20): Graded on the hosted lines for the MCP server and the REST API. No status page was found on the site, the docs, the pricing page or the repository (0). No incident history to read (5). The troubleshooting page documents a 429 for request limits with no figures (0). The same page says to wait a minute and retry, and every tool carries an `idempotentHint`, but `instances_launch` has no idempotency key (5 of 15). The on-demand page says 99.999 per cent uptime is guaranteed. No SLA document was found, the End User Licence Agreement promises support only under an order form or SLA, and the Terms & Conditions could not be read (0). The API is `/api/v1`, the server card is version 1.0.0 and nothing is labelled beta (10).

### Maintenance & community: Cloud Run GPUs +29

- Cloud Run GPUs (80): Closed service with official SDKs. The newest GPU change is 30 October 2026, jobs with GPUs running up to 12 hours (30). Cloud Run release notes dated 4 November, 2 November, 30 October, 24 October and more in the 90 days (20). Release notes, Google Cloud support and public trackers for the client libraries, which were not read (10). Official client libraries in eight languages and gcloud (15). CI results not checked (5). 30+20+10+15+5 = 80.
- Massed Compute (51): The newest release of the MCP wrapper is v1.1.0 of 24 July 2026, 77 days before the check. The hosted server has changed since, with fields in the server card that the July definitions lack, but no dated API changelog records it (20 of 30). One release and one dated changelog entry in the last 90 days (0). A dated wrapper changelog and a Discord server named as the fastest support route. No API changelog, and the repository shows six open issues or pull requests whose answers we did not read (7 of 15). Listed in the official MCP registry as `io.github.Massed-Compute/mcp` at 1.1.0, published 31 July 2026, with current npm and PyPI packages (15). CI tests Node 20 and 22 and Python 3.10 to 3.13 on three operating systems, with Dependabot, static analysis and a nightly check of the hosted endpoint. The npm package has no runtime dependencies (9 of 10).

### 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.
- Massed Compute (64): Closed service. The End User Licence Agreement of 15 September 2026 is clear and applies Nevada law, and the wrapper is MIT. The Terms & Conditions, the principal agreement, are drawn by a script we could not read (13 of 30). The privacy policy of 22 July 2026, the DPA of 27 March 2026 and the EULA are published. The EULA says VM data is destroyed at termination and persistent storage is kept at most 60 days after non-payment. The privacy policy is a general template that names a mobile application and gives no retention periods (19 of 30). No deprecation policy was found. The wrapper's changelog documents what 1.1.0 removed, and the older docs site still documents `api.massedcompute.com` while the current docs say not to use it (4 of 20). The sub-processor list names 23 processors with locations, is dated 10 September 2026 and has an RSS feed. The DPA says primary processing is in the United States (17 of 20).

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

- 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.
- Massed Compute (61): OAuth with discovery from a 401 challenge, or named API tokens shown once and revoked one at a time. Both come in two tiers, read-only and full access, with no finer scopes. Secrets travel only in a header (26 of 30). The read-only tier blocks launch, restart, terminate and SSH key changes. Destructive tool descriptions ask the model to confirm with the user, and a published skill adds a disclosure step. No server-side confirmation was found (13 of 20). The MCP server redacts VM passwords from tool results. Recipes are vendor-written Markdown that tools tell the model to follow step by step, and the docs give no guidance on untrusted content (9 of 15). Connected Apps lists OAuth grants. No audit log or per-call history was found (3 of 15). The wrapper's SECURITY.md gives a disclosure address, a two-business-day acknowledgement and a 30-day fix target, and its CI runs static analysis and dependency audits. The site claims SOC 2 Type II and HIPAA with no report or trust page, and there is no security.txt or bug bounty (10 of 20).

### Schema & documentation: Cloud Run GPUs +12

- Cloud Run GPUs (81): API reading. A public Discovery document for the Cloud Run Admin API v2 (25). No llms.txt; Google's docs answer Markdown only at an unlinked `.md.txt` address, read as half, as for the Document AI listing (5). The GPU page says when to turn zonal redundancy on or off and the best-practices page when to bake models into images or load them from Cloud Storage (16). The GPU type is a free string in a node selector, with CPU and memory minimums stated in prose (9). gcloud, YAML, Terraform and console steps on each page, and errors follow Google's status model with no Cloud Run GPU error list (11). Versioned API (v1 and v2) and dated release notes (15). 25+5+16+9+11+15 = 81.
- Massed Compute (69): A public OpenAPI 3.0 file covers the 14 REST operations, and a public server card lists all 17 MCP tools with JSON Schema inputs (25). massedcompute.com has an `llms.txt` that indexes marketing pages, and the vendor publishes an agent catalogue, the server card and four Markdown skills files. The docs sites have no `llms.txt` or Markdown copies (6 of 10). Tool descriptions state the purpose, the cost of a launch, when to search recipes first and when to confirm with the user. REST descriptions are one line each (16 of 20). Required fields are marked and extra properties are refused, but there are no enums, `productName` and `regionName` are free strings, and the OpenAPI file's required lists name `image_id` and `couponCode` where the properties are `imageId` and `coupon` (8 of 15). Every REST operation has a response example. Only 200 and 202 are documented, and errors appear only in a troubleshooting table and a deployment errors page (7 of 15). The path is versioned as `/api/v1` and the MCP wrapper has a dated changelog. No API changelog was found (7 of 15).

### Agent ergonomics: Cloud Run GPUs +10

- 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.
- Massed Compute (56): 17 tools whose definitions total about 10.5 KB in the server card, and a read-only credential cannot use the six write tools (15 plus 5 of 25). List tools take no arguments, with no pagination, filters or field selection. Only `recipes_search` has a `limit`, default 3 and maximum 10 (4 of 20). The docs explain 401, 402 and 429, the changelog names `-32003 Forbidden` for an out-of-scope call, and six deployment messages have written resolutions. None is in the OpenAPI file (10 of 20). All 17 tools carry `readOnlyHint`, `destructiveHint`, `idempotentHint` and `openWorldHint`. A launch has no idempotency key (14 of 20). A launch needs three fields and `regionName` accepts `any`. The only official packages are the npm and PyPI MCP wrappers, and the Go SDK and Terraform provider named on the product page were not found (8 of 15).

## Score by category

| Category | Weight | Cloud Run GPUs | Massed Compute | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 70 | 20 | Cloud Run GPUs +50 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 81 | 69 | Cloud Run GPUs +12 |
| Agent ergonomics | 13% (16.2 this run) | 66 | 56 | Cloud Run GPUs +10 |
| Security & auth | 14% (17.5 this run) | 78 | 61 | Cloud Run GPUs +17 |
| 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 | 51 | Cloud Run GPUs +29 |
| Transparency & trust | 7% (8.8 this run) | 84 | 64 | Cloud Run GPUs +20 |
| Negative events | ≤15 | 0 | -5 | |
| **Total** | | **68.4 · B** | **42.6 · E** | |

## Facts side by side

| Fact | Cloud Run GPUs | Massed Compute |
| --- | --- | --- |
| Kind | Platform | HTTP API |
| Vendor | Google Cloud | Massed Compute |
| Hosted endpoint | `https://run.googleapis.com` | `https://vm.massedcompute.com/api/v1` |
| Transports |  | HTTP, Streamable HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Pay per use | Pay per use |
| Price for gpu compute | not published | $5.43 per GPU-hour |
| x402 | no | no |
| Licence | Proprietary service under the Google Cloud Platform terms. Client libraries are Apache-2.0 | Proprietary service under Massed Compute's Terms & Conditions and End User Licence Agreement. The `massed-compute-mcp` wrapper on GitHub is MIT |
| Tools exposed | none | 17 |
| Read-only variant documented | no | yes |
| llms.txt | no | yes |
| MCP registry | not listed | `io.github.Massed-Compute/mcp` |
| Last release | 2026-10-30 | 2026-07-24 |
| Terms last updated | 2026-09-02 | couldn't be read |
| Privacy policy last updated | 2026-09-28 | 2026-07-22 |
| 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 | 1 stars |
| Agent reviews | none | 3.3/5 (4) |

## How the scores have moved

### Cloud Run GPUs

No score change since it was listed.

### Massed Compute

- +0.2 on 29 October 2026: time
- -0.1 on 28 October 2026: correction
- +0.2 on 27 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.

**Massed Compute.** The hosted MCP server and REST API accept OAuth grants or API tokens in read-only and full-access tiers, and all 17 tools carry typed schemas and safety annotations in a public server card. No status page, rate limit figures or API changelog were found, a launch has no idempotency key, and the governing terms could not be read.

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

### Massed Compute

1. Use `https://vm.massedcompute.com/api/v1`. The older docs at api-docs.massedcompute.com describe a separate marketplace API on `api.massedcompute.com` whose keys come from support.
2. Ask the owner for a read-only token unless the task must launch or terminate. Read-only credentials cannot call launch, restart, terminate or SSH key changes.
3. Call `gpu_inventory_list` and `images_list` before `instances_launch`. Product names and image IDs are free values, and SXM-only images do not run on PCIe cards.
4. Expect 402 on launch until the owner has added credit and set a recharge amount and threshold. List instances before retrying a launch.
5. Terminate to end billing. Stopping keeps the full hourly charge, and termination deletes the instance data.

## Questions

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

Cloud Run GPUs scores 68.4 (B) on agent readiness against Massed Compute's 42.6 (E), and leads in 6 of 7 scored categories.

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

Yes. Cloud Run GPUs has a hosted endpoint at https://run.googleapis.com and Massed Compute at https://vm.massedcompute.com/api/v1.


## For agents

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

## Other comparisons with Cloud Run GPUs or Massed Compute

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