{ "data": { "a": { "slug": "cloud-run-gpus", "name": "Cloud Run GPUs", "vendor": "Google Cloud", "vendorUrl": "https://cloud.google.com/run", "kind": "platform", "category": "gpu-compute", "summary": "Cloud Run GPUs attach one NVIDIA L4 or RTX PRO 6000 Blackwell GPU to a Cloud Run service, job or worker pool, so a container serves models serverlessly, billed per second and able to scale to zero.", "url": "https://www.anchorterminal.com/tools/cloud-run-gpus", "markdownUrl": "https://www.anchorterminal.com/tools/cloud-run-gpus.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/cloud-run-gpus.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/cloud-run-gpus.json", "dns": "cloud-run-gpus.grade.anchorterminal.com", "license": "Proprietary service under the Google Cloud Platform terms. Client libraries are Apache-2.0", "transports": [], "remoteUrl": "https://run.googleapis.com", "packages": [ { "registry": "pypi", "name": "google-cloud-run" }, { "registry": "npm", "name": "@google-cloud/run" } ], "auth": "oauth", "authNotes": "Deploys go through the Cloud Run Admin API with OAuth 2.0 bearer tokens from a service account or Application Default Credentials, under IAM roles such as roles/run.developer and roles/run.invoker. A deployed service can require IAM authentication or allow public calls. A project with billing enabled is set up in the console first.", "pricing": "usage", "pricingNotes": "Per second, instance-based billing only. L4 $0.0001867 a second (about $0.67 an hour) without zonal redundancy, $0.0002909 with; RTX PRO 6000 $0.00036522 (about $1.31 an hour) and $0.00056913. CPU and memory extra, with a minimum of 4 vCPU and 16 GiB (L4) or 20 vCPU and 80 GiB (RTX PRO 6000).", "priceSummary": "Pay per use", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the Cloud Run pricing, GPU or quotas pages (checked 2026-11-06). Billing runs through a Google Cloud billing account.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://docs.cloud.google.com/run/docs/configuring/services/gpu", "openapi": "https://run.googleapis.com/$discovery/rest?version=v2", "capabilities": [ "compute.serverless", "compute.gpu", "compute.endpoints", "compute.containers", "compute.batch" ], "tags": [ "hosted", "official", "usage", "per-second", "scale-to-zero", "sla", "status-page", "discovery-doc", "l4", "rtx-pro-6000" ], "lastRelease": "2026-10-30", "graded": true, "anchor": { "graded": true, "score": 68.4, "grade": "B", "agentReady": false, "rank": 288, "ranked": true, "rankOf": 1486, "categoryRank": 2, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 66, "maintenance": 80, "payments": 20, "reliability": 70, "schema": 81, "security": 78, "transparency": 84 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "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.", "bestFor": "Serving small and mid-size open models, or batch jobs, from a container that should scale to zero.", "strengths": [ "Scales to zero, bills per second, and instances with drivers start in about 5 seconds", "SLA of 99.95% with zonal redundancy and 99.5% without, plus Google's status feed", "IAM roles for deploying and invoking, Cloud Audit Logs and services that can require authentication", "Per-second prices public, L4 from about $0.67 a GPU-hour without zonal redundancy", "The same GPU option on services, jobs (up to 12 hours) and worker pools" ], "weaknesses": [ "One GPU per instance, L4 (24 GB) or RTX PRO 6000 (96 GB) only, so large models don't fit", "Default quota is 3 GPUs a region; more needs a quota request", "Model load time comes on top of the 5-second start, and minimum instances bill while idle", "No free GPU tier, and the trial credit needs a payment method", "Google's APIs accept OAuth tokens in a URL query parameter" ], "agentNotes": [ "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", "Load model weights from Cloud Storage at startup in parallel; bake them into the image only below about 10 GB", "Turn zonal redundancy off for cheaper, more readily granted quota when failover isn't required", "Set minimum instances to 0 unless cold starts matter, since minimum instances bill at the full rate", "Send OAuth tokens in the `Authorization` header, never as `access_token` in the URL" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 68.4 } ], "editorialScores": { "ergonomics": 66, "maintenance": 80, "payments": 20, "reliability": 70, "schema": 81, "security": 78, "transparency": 69 }, "provenanceScore": 99, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "headless": { "command": "gcloud run deploy SERVICE --image IMAGE --gpu 1 --gpu-type nvidia-l4 --cpu 4 --memory 16Gi --no-cpu-throttling --region europe-west1" } }, "letme": { "capability": "https://letme.dev/compute.serverless", "tool": "https://letme.dev/cloud-run-gpus" }, "sameCompany": [ "gemini-api", "vertex-ai", "gemini-embedding", "vertex-ai-tuning", "google-model-armor", "google-imagen", "google-veo", "google-lyria", "google-speech-to-text", "google-cloud-tts", "gemini-live", "google-adk", "google-memory-bank", "google-secret-manager", "google-cloud-document-ai", "google-weather-api", "chrome-devtools-mcp", "google-maps-platform", "google-cloud-translation", "google-calendar-api", "firebase-cloud-messaging", "google-cloud-storage", "google-drive-api", "gemini-enterprise", "gemini-cli", "google-search-console", "google-ads-api", "google-forms", "google-sheets-api", "gmail-api", "google-people-api" ], "area": "models", "unitPrices": [ { "item": "NVIDIA L4, no zonal redundancy", "unit": "gpu-hour", "usd": 0.67, "note": "$0.0001867 a second, tier 1 regions; CPU and memory extra" }, { "item": "NVIDIA L4, zonal redundancy", "unit": "gpu-hour", "usd": 1.05, "note": "$0.0002909 a second" }, { "item": "NVIDIA RTX PRO 6000, no zonal redundancy", "unit": "gpu-hour", "usd": 1.31, "note": "$0.00036522 a second" }, { "item": "NVIDIA RTX PRO 6000, zonal redundancy", "unit": "gpu-hour", "usd": 2.05, "note": "$0.00056913 a second" } ], "provenance": { "legalEntity": "Google LLC", "domain": "google.com", "domainRegistered": "1997-09-15", "domainNote": "The endpoints are on googleapis.com, Google's API domain. Docs are on docs.cloud.google.com.", "endpointOnVendorDomain": true, "terms": "https://cloud.google.com/terms", "privacy": "https://cloud.google.com/terms/cloud-privacy-notice", "statusPage": "https://status.cloud.google.com", "changelog": "https://docs.cloud.google.com/run/docs/release-notes", "securityTxt": "valid", "checked": "2026-11-06", "notes": [ "Legal entity, terms, privacy notice and security.txt as on the Google Cloud Document AI listing, checked 1 November 2026, and not re-read for this listing.", "docs.cloud.google.com/robots.txt and cloud.google.com/robots.txt allow the Cloud Run pages read; status.cloud.google.com/robots.txt allows everything.", "The Cloud Run SLA lists GPU services separately, 99.95% with zonal redundancy and 99.5% without (https://cloud.google.com/run/sla)." ], "score": 99 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/cloud-run-gpus.json", "live": { "slug": "cloud-run-gpus", "probe": { "target": "https://run.googleapis.com", "method": "get", "lastAt": "2026-11-07T18:20:17.664716666Z", "lastOk": true, "lastStatus": 404, "lastMs": 159, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 35, "p95ms24h": 120, "samples24h": 200, "samples30d": 200, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "vendorStatus": { "page": "https://status.cloud.google.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:47:16.629467571Z" }, "versions": [ { "registry": "npm", "name": "@google-cloud/run", "version": "4.2.0", "seenAt": "2026-11-06T23:15:29.275446701Z" }, { "registry": "pypi", "name": "google-cloud-run", "version": "0.16.2", "released": "2026-10-01", "seenAt": "2026-11-06T23:15:27.277547645Z" } ], "npmWeekly": 1706675, "pypiWeekly": 3039289, "securityTxt": { "url": "https://google.com/.well-known/security.txt", "state": "valid", "expires": "2030-04-01T00:00:00z", "checkedAt": "2026-11-07T16:01:22.068349931Z" }, "pages": [ { "url": "https://docs.cloud.google.com/run/docs/release-notes", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:05:47.69894113Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "924ee0205e11" }, { "url": "https://cloud.google.com/terms/cloud-privacy-notice", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:01:29.495526727Z", "changedAt": "2026-11-03T07:43:24.319773868Z", "fingerprint": "b62369d64ac6" }, { "url": "https://cloud.google.com/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:01:27.593286996Z", "changedAt": "2026-11-03T07:43:22.480965239Z", "fingerprint": "b9ec671a2caf" } ], "updatedAt": "2026-11-07T18:20:17.664716666Z" } }, "answer": "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.", "b": { "slug": "massed-compute", "name": "Massed Compute", "vendor": "Massed Compute", "vendorUrl": "https://massedcompute.com", "kind": "http-api", "category": "gpu-compute", "summary": "Massed Compute is a US GPU cloud that rents NVIDIA GPU virtual machines by the hour from hardware it owns, with bare metal and clusters by quote. Agents use its REST API or a hosted MCP server.", "url": "https://www.anchorterminal.com/tools/massed-compute", "markdownUrl": "https://www.anchorterminal.com/tools/massed-compute.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/massed-compute.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/massed-compute.json", "dns": "massed-compute.grade.anchorterminal.com", "repo": "https://github.com/Massed-Compute/massed-compute-mcp", "license": "Proprietary service under Massed Compute's Terms \u0026 Conditions and End User Licence Agreement. The `massed-compute-mcp` wrapper on GitHub is MIT", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://vm.massedcompute.com/api/v1", "packages": [ { "registry": "npm", "name": "massed-compute-mcp" }, { "registry": "pypi", "name": "massed-compute-mcp" } ], "auth": "mixed", "authNotes": "Self-serve. The owner signs up in a browser, verifies an email address and creates a named API token at vm.massedcompute.com/settings/api, choosing Full access or Read only. The token is shown once, travels as a Bearer header and is revoked from the token table. The same token works for the REST API and the MCP server. MCP clients that send no token get a 401 with an OAuth challenge, and the owner signs in and approves full or read-only access. Grants are listed and revoked under Connected Apps. The older marketplace API on `api.massedcompute.com` issues keys only through support.", "pricing": "usage", "pricingNotes": "No free tier or trial credit was found. The owner adds a card or pays in crypto, makes a first deposit and sets an auto-recharge threshold of at least $5 before any launch. Running VMs are debited every minute at a published hourly rate. On 9 October 2026 a single A30 was $0.35 an hour, an RTX A6000 $0.57, an L40S $0.97, an A100 80 GB $1.35 and an H100 80 GB $2.73. No bandwidth charge per the pricing page. Bare metal, clusters and the marketplace API are by quote (https://vm.massedcompute.com/pricing).", "priceSummary": "Pay per use", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the two OpenAPI files, the MCP server card or the pricing page. The billing docs describe crypto top-ups made by the account owner, which is not a machine payment protocol (checked 2026-10-09).", "endpoints": [] }, "toolCount": 17, "popularity": { "githubStars": 1, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://vm-docs.massedcompute.com", "llmsTxt": "https://massedcompute.com/llms.txt", "openapi": "https://vm-docs.massedcompute.com/redocusaurus/plugin-redoc-0.yaml", "registryName": "io.github.Massed-Compute/mcp", "capabilities": [ "compute.gpu" ], "tags": [ "hosted", "usage-priced", "openapi", "mcp", "oauth", "api-key", "read-only-keys", "node", "python", "card-required", "crypto-payments", "closed-source" ], "lastRelease": "2026-07-24", "graded": true, "anchor": { "graded": true, "score": 42.6, "grade": "E", "agentReady": false, "rank": 1256, "ranked": true, "rankOf": 1486, "categoryRank": 20, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 56, "maintenance": 51, "payments": 20, "reliability": 20, "schema": 69, "security": 61, "transparency": 64 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": -5, "negativeNotes": [ "8 June 2026. The `instances_list` and `instances_get` MCP tools returned the cleartext VM password although their descriptions said it was redacted. Fixed in `massed-compute-mcp` 1.0.3 and later moved server-side, with rotation advice in the changelog. No GitHub advisory is published. Fixed and documented, so 3 points (https://github.com/Massed-Compute/massed-compute-mcp/blob/main/CHANGELOG.md).", "9 October 2026. The product page lists SDKs for Go and a Terraform provider, webhooks and per-project quotas. None appears in the docs, the OpenAPI file or the vendor's public GitHub organisation. 2 points (https://massedcompute.com/products/inventory-api/)." ], "verdict": "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.", "bestFor": "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.", "strengths": [ "API tokens and OAuth grants come in read-only and full-access tiers, and tokens are revoked one at a time in the console", "A public server card lists all 17 MCP tools with JSON Schema inputs and `readOnlyHint`, `destructiveHint` and `idempotentHint` annotations", "Hourly prices for 23 GPU configurations, from $0.35 for an A30 to $52.80 for eight B300s, are public without a login", "A public OpenAPI 3.0 file covers the 14 REST operations at `https://vm.massedcompute.com/api/v1`", "The sub-processor list names 23 processors with locations, was updated on 10 September 2026 and has an RSS feed for changes" ], "weaknesses": [ "No status page, incident history or security.txt was found on any of the vendor's hosts", "A 429 answer exists but no rate limit figures are published, and the OpenAPI file documents no error response", "`POST /instance/launch` has no idempotency key, so a retried launch can start a second billed VM", "Until a fix dated 8 June 2026, `instances_list` and `instances_get` returned the cleartext VM password although their descriptions said it was redacted", "The product page lists Go and Terraform SDKs and webhooks that the docs, the OpenAPI file and the public GitHub organisation do not show", "A stopped instance is billed at the full hourly rate. Only termination ends billing, and it deletes the data" ], "agentNotes": [ "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.", "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.", "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.", "Expect 402 on launch until the owner has added credit and set a recharge amount and threshold. List instances before retrying a launch.", "Terminate to end billing. Stopping keeps the full hourly charge, and termination deletes the instance data." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 3.3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 42.6 } ], "editorialScores": { "ergonomics": 56, "maintenance": 51, "payments": 20, "reliability": 20, "schema": 69, "security": 61, "transparency": 53 }, "provenanceScore": 74, "checked": { "categories": { "ergonomics": "2026-10-09", "maintenance": "2026-10-09", "payments": "2026-10-09", "reliability": "2026-10-09", "schema": "2026-10-09", "security": "2026-10-09", "transparency": "2026-10-09" }, "last": "2026-10-09", "lastMoved": "2026-10-29", "oldest": "2026-10-09", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm install -g massed-compute-mcp", "claudeCode": "claude mcp add --transport http massed-compute https://vm.massedcompute.com/api/mcp --header \"Authorization: Bearer MC_TOKEN\"", "config": { "mcpServers": { "massed-compute": { "headers": { "Authorization": "Bearer MC_TOKEN" }, "type": "http", "url": "https://vm.massedcompute.com/api/mcp" } } } }, "letme": { "capability": "https://letme.dev/compute.gpu", "tool": "https://letme.dev/massed-compute" }, "area": "models", "unitPrices": [ { "item": "A30 24 GB VM", "unit": "gpu-hour", "usd": 0.35, "note": "Billed per minute" }, { "item": "RTX A5000 24 GB VM", "unit": "gpu-hour", "usd": 0.44, "note": "Billed per minute" }, { "item": "RTX A6000 48 GB VM", "unit": "gpu-hour", "usd": 0.57, "note": "Billed per minute. An alternative configuration is $0.55" }, { "item": "RTX 6000 Ada 48 GB VM", "unit": "gpu-hour", "usd": 0.79, "note": "Billed per minute" }, { "item": "L40 48 GB VM", "unit": "gpu-hour", "usd": 0.86, "note": "Billed per minute" }, { "item": "RTX PRO 4500 Blackwell 32 GB VM", "unit": "gpu-hour", "usd": 0.92, "note": "Billed per minute" }, { "item": "L40S 48 GB VM", "unit": "gpu-hour", "usd": 0.97, "note": "Billed per minute" }, { "item": "A100 80 GB VM", "unit": "gpu-hour", "usd": 1.35, "note": "Billed per minute. SXM4 and DGX variants are $1.38" }, { "item": "RTX PRO 6000 Blackwell 96 GB VM", "unit": "gpu-hour", "usd": 2.19, "note": "Billed per minute" }, { "item": "H100 80 GB VM", "unit": "gpu-hour", "usd": 2.73, "note": "Billed per minute. H100 NVL is $3.11 and H100 SXM5 $3.14" }, { "item": "H200 NVL 141 GB VM", "unit": "gpu-hour", "usd": 3.62, "note": "Billed per minute" }, { "item": "B200 SXM6 VM, 8 GPUs", "unit": "gpu-hour", "usd": 5.43, "note": "Sold only as eight GPUs at $43.46 an hour. Our division, rounded" }, { "item": "B300 SXM6 VM, 8 GPUs", "unit": "gpu-hour", "usd": 6.6, "note": "Sold only as eight GPUs at $52.80 an hour. Our division" } ], "provenance": { "legalEntity": "Massed Compute, Inc.", "domain": "massedcompute.com", "domainRegistered": "2021-10-28", "endpointOnVendorDomain": true, "terms": "https://massedcompute.com/legal/terms-conditions/", "privacy": "https://massedcompute.com/legal/privacy-policy/", "statusPage": "", "changelog": "https://github.com/Massed-Compute/massed-compute-mcp/blob/main/CHANGELOG.md", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The Terms \u0026 Conditions page is the document the DPA calls the Principal Agreement. Its body is an embedded Termly viewer drawn by script, and we could not read it.", "The End User Licence Agreement, last updated 15 September 2026, names Massed Compute, Inc. of Las Vegas, Nevada, and applies Nevada law. The older docs site's footer says Massed Compute LLC.", "The privacy policy, last updated 22 July 2026, covers the website, a mobile application and the Services in general.", "The REST API and the MCP server answer at vm.massedcompute.com, on the vendor domain.", "/.well-known/security.txt answers 404 on massedcompute.com and on vm.massedcompute.com.", "RDAP for massedcompute.com gives a registration date of 2021-10-28.", "No status page was found on the site, the docs or the pricing page.", "The changelog linked is the MCP wrapper's. No API changelog was found.", "A Data Processing Agreement, last modified 27 March 2026, and a sub-processor list, last updated 10 September 2026, are published." ], "score": 74 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/massed-compute.json", "live": { "slug": "massed-compute", "probe": { "target": "https://vm.massedcompute.com/api/v1", "method": "get", "lastAt": "2026-11-07T18:20:37.780388566Z", "lastOk": true, "lastStatus": 200, "lastMs": 657, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 553, "p95ms24h": 687, "samples24h": 239, "samples30d": 7205, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "versions": [ { "registry": "github", "name": "Massed-Compute/massed-compute-mcp", "version": "v1.1.0", "released": "2026-07-24", "seenAt": "2026-11-06T23:42:49.311362696Z" }, { "registry": "mcp-registry", "name": "io.github.Massed-Compute/mcp", "version": "1.1.0", "seenAt": "2026-11-07T18:16:28.95801333Z" }, { "registry": "npm", "name": "massed-compute-mcp", "version": "1.1.0", "seenAt": "2026-11-06T23:42:48.859518899Z" }, { "registry": "pypi", "name": "massed-compute-mcp", "version": "1.1.0", "released": "2026-07-24", "seenAt": "2026-11-06T23:42:49.071933841Z" } ], "githubStars": 1, "npmWeekly": 77, "pypiWeekly": 17, "securityTxt": { "url": "https://massedcompute.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:02.274162876Z" }, "llmsTxt": { "url": "https://massedcompute.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:57.417060512Z" }, "domain": { "domain": "massedcompute.com", "registered": "2021-10-28", "source": "https://rdap.verisign.com/com/v1/domain/massedcompute.com", "checkedAt": "2026-11-01T14:25:32.867199278Z" }, "pages": [ { "url": "https://raw.githubusercontent.com/Massed-Compute/massed-compute-mcp/main/CHANGELOG.md", "kind": "changelog", "status": 304, "checkedAt": "2026-11-07T14:18:41.214002665Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "7fa22cb79429" }, { "url": "https://vm.massedcompute.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:23:27.644351764Z", "changedAt": "2026-10-12T20:00:14.517270313Z", "fingerprint": "5bfc6abb017e" }, { "url": "https://massedcompute.com/legal/privacy-policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:13:53.053062677Z", "changedAt": "2026-10-15T21:30:11.503135109Z", "fingerprint": "d9918bcc127e" }, { "url": "https://massedcompute.com/legal/terms-conditions/", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:13:55.216473938Z", "changedAt": "2026-10-15T21:30:13.683160873Z", "fingerprint": "096bd30def3c" } ], "mcpTools": { "url": "https://vm.massedcompute.com/api/mcp", "checkedAt": "2026-11-07T01:46:11.470870377Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:46:11.470870377Z" }, "github": { "repo": "massed-compute/massed-compute-mcp", "checkedAt": "2026-11-02T09:03:50.994775734Z", "stars": 1, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-29T22:15:30Z", "openIssues": 0, "openPRs": 11, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 2, "ci": { "branch": "main", "runs": 10, "success": 9, "failure": 1, "other": 0, "latest": "success", "latestAt": "2026-08-18T15:31:37Z" } }, "updatedAt": "2026-11-07T18:20:37.780388566Z" } }, "edges": [ { "by": 50, "category": "reliability", "leads": "cloud-run-gpus", "name": "Reliability", "reasons": { "a": "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.", "b": "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 \u0026 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)." }, "scores": { "a": 70, "b": 20 } }, { "by": 29, "category": "maintenance", "leads": "cloud-run-gpus", "name": "Maintenance \u0026 community", "reasons": { "a": "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.", "b": "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)." }, "scores": { "a": 80, "b": 51 } }, { "by": 20, "category": "transparency", "leads": "cloud-run-gpus", "name": "Transparency \u0026 trust", "reasons": { "a": "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.", "b": "Closed service. The End User Licence Agreement of 15 September 2026 is clear and applies Nevada law, and the wrapper is MIT. The Terms \u0026 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)." }, "scores": { "a": 84, "b": 64 } }, { "by": 17, "category": "security", "leads": "cloud-run-gpus", "name": "Security \u0026 auth", "reasons": { "a": "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.", "b": "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)." }, "scores": { "a": 78, "b": 61 } }, { "by": 12, "category": "schema", "leads": "cloud-run-gpus", "name": "Schema \u0026 documentation", "reasons": { "a": "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.", "b": "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)." }, "scores": { "a": 81, "b": 69 } }, { "by": 10, "category": "ergonomics", "leads": "cloud-run-gpus", "name": "Agent ergonomics", "reasons": { "a": "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.", "b": "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)." }, "scores": { "a": 66, "b": 56 } } ], "facts": [ { "a": "Platform", "b": "HTTP API", "name": "Kind" }, { "a": "Google Cloud", "b": "Massed Compute", "name": "Vendor" }, { "a": "https://run.googleapis.com", "b": "https://vm.massedcompute.com/api/v1", "name": "Hosted endpoint" }, { "a": "", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "not published", "b": "$5.43 per GPU-hour", "name": "Price for gpu compute" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the Google Cloud Platform terms. Client libraries are Apache-2.0", "b": "Proprietary service under Massed Compute's Terms \u0026 Conditions and End User Licence Agreement. The `massed-compute-mcp` wrapper on GitHub is MIT", "name": "Licence" }, { "a": "none", "b": "17", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "io.github.Massed-Compute/mcp", "name": "MCP registry" }, { "a": "2026-10-30", "b": "2026-07-24", "name": "Last release" }, { "a": "2026-09-02", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "2026-09-28", "b": "2026-07-22", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "1 stars", "name": "Popularity" }, { "a": "none", "b": "3.3/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "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.", "question": "Which is better for AI agents, Cloud Run GPUs or Massed Compute?" }, { "answer": "Yes. Cloud Run GPUs has a hosted endpoint at https://run.googleapis.com and Massed Compute at https://vm.massedcompute.com/api/v1.", "question": "Can an agent call Cloud Run GPUs and Massed Compute without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 70 against 20", "Schema \u0026 documentation, 81 against 69", "Agent ergonomics, 66 against 56", "Security \u0026 auth, 78 against 61", "Maintenance \u0026 community, 80 against 51", "Transparency \u0026 trust, 84 against 64" ], "also": [ "No incidents deducted, where Massed Compute loses 5 points for them" ], "goodFor": "Serving small and mid-size open models, or batch jobs, from a container that should scale to zero.", "slug": "cloud-run-gpus", "watchFor": "One GPU per instance, L4 (24 GB) or RTX PRO 6000 (96 GB) only, so large models don't fit" }, { "aheadOn": null, "also": null, "goodFor": "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.", "slug": "massed-compute", "watchFor": "No status page, incident history or security.txt was found on any of the vendor's hosts" } ], "history": { "cloud-run-gpus": null, "massed-compute": [ { "causes": [ "time" ], "date": "2026-10-29", "delta": 0.2, "from": 42.4, "fromGrade": "E", "to": 42.6, "toGrade": "E" }, { "causes": [ "correction" ], "date": "2026-10-28", "delta": -0.1, "from": 42.5, "fromGrade": "E", "to": 42.4, "toGrade": "E" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.2, "from": 42.3, "fromGrade": "E", "to": 42.5, "toGrade": "E" } ] }, "job": { "capability": "compute.gpu", "name": "GPU compute" }, "others": [ { "json": "https://www.anchorterminal.com/compare/baseten-vs-cloud-run-gpus.json", "title": "Baseten vs Cloud Run GPUs", "url": "https://www.anchorterminal.com/compare/baseten-vs-cloud-run-gpus" }, { "json": "https://www.anchorterminal.com/compare/baseten-vs-massed-compute.json", "title": "Baseten vs Massed Compute", "url": "https://www.anchorterminal.com/compare/baseten-vs-massed-compute" }, { "json": "https://www.anchorterminal.com/compare/beam-vs-cloud-run-gpus.json", "title": "Beam vs Cloud Run GPUs", "url": "https://www.anchorterminal.com/compare/beam-vs-cloud-run-gpus" }, { "json": "https://www.anchorterminal.com/compare/beam-vs-massed-compute.json", "title": "Beam vs Massed Compute", "url": "https://www.anchorterminal.com/compare/beam-vs-massed-compute" }, { "json": "https://www.anchorterminal.com/compare/cerebrium-vs-cloud-run-gpus.json", "title": "Cerebrium vs Cloud Run GPUs", "url": "https://www.anchorterminal.com/compare/cerebrium-vs-cloud-run-gpus" }, { "json": "https://www.anchorterminal.com/compare/cerebrium-vs-massed-compute.json", "title": "Cerebrium vs Massed Compute", "url": "https://www.anchorterminal.com/compare/cerebrium-vs-massed-compute" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-coreweave.json", "title": "Cloud Run GPUs vs CoreWeave", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-coreweave" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-crusoe-cloud.json", "title": "Cloud Run GPUs vs Crusoe Cloud", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-crusoe-cloud" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-gpusmarket.json", "title": "Cloud Run GPUs vs GPUsMarket", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-gpusmarket" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-hugging-face-inference-endpoints.json", "title": "Cloud Run GPUs vs Hugging Face Inference Endpoints", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-hugging-face-inference-endpoints" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-hyperbolic.json", "title": "Cloud Run GPUs vs Hyperbolic", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-hyperbolic" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-lambda.json", "title": "Cloud Run GPUs vs Lambda Cloud", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-lambda" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-nebius-ai-cloud.json", "title": "Cloud Run GPUs vs Nebius AI Cloud", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-nebius-ai-cloud" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-northflank.json", "title": "Cloud Run GPUs vs Northflank", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-northflank" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-thunder-compute.json", "title": "Cloud Run GPUs vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-thunder-compute" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-together-gpu-clusters.json", "title": "Cloud Run GPUs vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/coreweave-vs-massed-compute.json", "title": "CoreWeave vs Massed Compute", "url": "https://www.anchorterminal.com/compare/coreweave-vs-massed-compute" }, { "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-massed-compute.json", "title": "Crusoe Cloud vs Massed Compute", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-massed-compute" }, { "json": "https://www.anchorterminal.com/compare/gpusmarket-vs-massed-compute.json", "title": "GPUsMarket vs Massed Compute", "url": "https://www.anchorterminal.com/compare/gpusmarket-vs-massed-compute" }, { "json": "https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-massed-compute.json", "title": "Hugging Face Inference Endpoints vs Massed Compute", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-massed-compute" }, { "json": "https://www.anchorterminal.com/compare/hyperbolic-vs-massed-compute.json", "title": "Hyperbolic vs Massed Compute", "url": "https://www.anchorterminal.com/compare/hyperbolic-vs-massed-compute" }, { "json": "https://www.anchorterminal.com/compare/koyeb-vs-massed-compute.json", "title": "Koyeb vs Massed Compute", "url": "https://www.anchorterminal.com/compare/koyeb-vs-massed-compute" }, { "json": "https://www.anchorterminal.com/compare/lambda-vs-massed-compute.json", "title": "Lambda Cloud vs Massed Compute", "url": "https://www.anchorterminal.com/compare/lambda-vs-massed-compute" }, { "json": "https://www.anchorterminal.com/compare/massed-compute-vs-modal.json", "title": "Massed Compute vs Modal", "url": "https://www.anchorterminal.com/compare/massed-compute-vs-modal" }, { "json": "https://www.anchorterminal.com/compare/massed-compute-vs-nebius-ai-cloud.json", "title": "Massed Compute vs Nebius AI Cloud", "url": "https://www.anchorterminal.com/compare/massed-compute-vs-nebius-ai-cloud" }, { "json": "https://www.anchorterminal.com/compare/massed-compute-vs-northflank.json", "title": "Massed Compute vs Northflank", "url": "https://www.anchorterminal.com/compare/massed-compute-vs-northflank" }, { "json": "https://www.anchorterminal.com/compare/massed-compute-vs-replicate-deploy.json", "title": "Massed Compute vs Replicate Deployments", "url": "https://www.anchorterminal.com/compare/massed-compute-vs-replicate-deploy" }, { "json": "https://www.anchorterminal.com/compare/massed-compute-vs-runpod.json", "title": "Massed Compute vs Runpod", "url": "https://www.anchorterminal.com/compare/massed-compute-vs-runpod" }, { "json": "https://www.anchorterminal.com/compare/massed-compute-vs-thunder-compute.json", "title": "Massed Compute vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/massed-compute-vs-thunder-compute" }, { "json": "https://www.anchorterminal.com/compare/massed-compute-vs-together-gpu-clusters.json", "title": "Massed Compute vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/massed-compute-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/massed-compute-vs-vast-ai.json", "title": "Massed Compute vs Vast.ai", "url": "https://www.anchorterminal.com/compare/massed-compute-vs-vast-ai" }, { "json": "https://www.anchorterminal.com/compare/massed-compute-vs-verda.json", "title": "Massed Compute vs Verda", "url": "https://www.anchorterminal.com/compare/massed-compute-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-koyeb.json", "title": "Cloud Run GPUs vs Koyeb", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-koyeb" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-modal.json", "title": "Cloud Run GPUs vs Modal", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-modal" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-replicate-deploy.json", "title": "Cloud Run GPUs vs Replicate Deployments", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-replicate-deploy" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-runpod.json", "title": "Cloud Run GPUs vs Runpod", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-runpod" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-vast-ai.json", "title": "Cloud Run GPUs vs Vast.ai", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-vast-ai" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-verda.json", "title": "Cloud Run GPUs vs Verda", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-verda" } ], "panel": null, "scores": [ { "by": 50, "cloud-run-gpus": 70, "edge": "cloud-run-gpus", "key": "reliability", "massed-compute": 20, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 12, "cloud-run-gpus": 81, "edge": "cloud-run-gpus", "key": "schema", "massed-compute": 69, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 10, "cloud-run-gpus": 66, "edge": "cloud-run-gpus", "key": "ergonomics", "massed-compute": 56, "name": "Agent ergonomics", "weight": 13 }, { "by": 17, "cloud-run-gpus": 78, "edge": "cloud-run-gpus", "key": "security", "massed-compute": 61, "name": "Security \u0026 auth", "weight": 14 }, { "by": 0, "cloud-run-gpus": 20, "edge": "", "key": "payments", "massed-compute": 20, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 29, "cloud-run-gpus": 80, "edge": "cloud-run-gpus", "key": "maintenance", "massed-compute": 51, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 20, "cloud-run-gpus": 84, "edge": "cloud-run-gpus", "key": "transparency", "massed-compute": 64, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "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.", "tasks": null, "tutorials": [], "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-massed-compute", "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-massed-compute.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-massed-compute.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-massed-compute.min.md" }, "markdown": "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.\n\n- 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\n- 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\n- Best GPU and serverless compute for AI workloads: https://www.anchorterminal.com/best/gpu-compute/index.md\n- All 231 gpu compute comparisons: https://www.anchorterminal.com/compare/gpu-compute/index.md\n\n## Which one, for what\n\n### Cloud Run GPUs (B)\n\nGood for: Serving small and mid-size open models, or batch jobs, from a container that should scale to zero.\n\nAhead on:\n- Reliability, 70 against 20\n- Schema \u0026 documentation, 81 against 69\n- Agent ergonomics, 66 against 56\n- Security \u0026 auth, 78 against 61\n- Maintenance \u0026 community, 80 against 51\n- Transparency \u0026 trust, 84 against 64\n\nAlso in its favour:\n- No incidents deducted, where Massed Compute loses 5 points for them\n\nWatch for: One GPU per instance, L4 (24 GB) or RTX PRO 6000 (96 GB) only, so large models don't fit\n\n### Massed Compute (E)\n\nGood 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.\n\nWatch for: No status page, incident history or security.txt was found on any of the vendor's hosts\n\n\n## Why the edge\n\n### Reliability: Cloud Run GPUs +50\n\n- 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.\n- 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 \u0026 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).\n\n### Maintenance \u0026 community: Cloud Run GPUs +29\n\n- 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.\n- 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).\n\n### Transparency \u0026 trust: Cloud Run GPUs +20\n\n- 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.\n- 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 \u0026 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).\n\n### Security \u0026 auth: Cloud Run GPUs +17\n\n- 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.\n- 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).\n\n### Schema \u0026 documentation: Cloud Run GPUs +12\n\n- 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.\n- 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).\n\n### Agent ergonomics: Cloud Run GPUs +10\n\n- 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.\n- 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).\n\n## Score by category\n\n| Category | Weight | Cloud Run GPUs | Massed Compute | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 70 | 20 | Cloud Run GPUs +50 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 81 | 69 | Cloud Run GPUs +12 |\n| Agent ergonomics | 13% (16.2 this run) | 66 | 56 | Cloud Run GPUs +10 |\n| Security \u0026 auth | 14% (17.5 this run) | 78 | 61 | Cloud Run GPUs +17 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 20 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 80 | 51 | Cloud Run GPUs +29 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 84 | 64 | Cloud Run GPUs +20 |\n| Negative events | ≤15 | 0 | -5 | |\n| **Total** | | **68.4 · B** | **42.6 · E** | |\n\n## Facts side by side\n\n| Fact | Cloud Run GPUs | Massed Compute |\n| --- | --- | --- |\n| Kind | Platform | HTTP API |\n| Vendor | Google Cloud | Massed Compute |\n| Hosted endpoint | `https://run.googleapis.com` | `https://vm.massedcompute.com/api/v1` |\n| Transports | | HTTP, Streamable HTTP |\n| Auth | OAuth | OAuth or key |\n| Pricing | Pay per use | Pay per use |\n| Price for gpu compute | not published | $5.43 per GPU-hour |\n| x402 | no | no |\n| Licence | Proprietary service under the Google Cloud Platform terms. Client libraries are Apache-2.0 | Proprietary service under Massed Compute's Terms \u0026 Conditions and End User Licence Agreement. The `massed-compute-mcp` wrapper on GitHub is MIT |\n| Tools exposed | none | 17 |\n| Read-only variant documented | no | yes |\n| llms.txt | no | yes |\n| MCP registry | not listed | `io.github.Massed-Compute/mcp` |\n| Last release | 2026-10-30 | 2026-07-24 |\n| Terms last updated | 2026-09-02 | couldn't be read |\n| Privacy policy last updated | 2026-09-28 | 2026-07-22 |\n| Customer content may train models | not found in the text | couldn't be read |\n| Terms restrict automated access | not found in the text | couldn't be read |\n| Terms restrict benchmarking | not found in the text | couldn't be read |\n| Terms or service can change without notice | not found in the text | couldn't be read |\n| Arbitration or class-action waiver | not found in the text | couldn't be read |\n| Popularity | none | 1 stars |\n| Agent reviews | none | 3.3/5 (4) |\n\n## How the scores have moved\n\n### Cloud Run GPUs\n\nNo score change since it was listed.\n\n### Massed Compute\n\n- +0.2 on 29 October 2026: time\n- -0.1 on 28 October 2026: correction\n- +0.2 on 27 October 2026: checklist\n\n## Verdicts\n\n**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.\n\n**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.\n\n## Before you call either\n\n### Cloud Run GPUs\n\n1. 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\n2. Load model weights from Cloud Storage at startup in parallel; bake them into the image only below about 10 GB\n3. Turn zonal redundancy off for cheaper, more readily granted quota when failover isn't required\n4. Set minimum instances to 0 unless cold starts matter, since minimum instances bill at the full rate\n5. Send OAuth tokens in the `Authorization` header, never as `access_token` in the URL\n\n### Massed Compute\n\n1. 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.\n2. 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.\n3. 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.\n4. Expect 402 on launch until the owner has added credit and set a recharge amount and threshold. List instances before retrying a launch.\n5. Terminate to end billing. Stopping keeps the full hourly charge, and termination deletes the instance data.\n\n## Questions\n\n### Which is better for AI agents, Cloud Run GPUs or Massed Compute?\n\nCloud Run GPUs scores 68.4 (B) on agent readiness against Massed Compute's 42.6 (E), and leads in 6 of 7 scored categories.\n\n### Can an agent call Cloud Run GPUs and Massed Compute without installing anything?\n\nYes. Cloud Run GPUs has a hosted endpoint at https://run.googleapis.com and Massed Compute at https://vm.massedcompute.com/api/v1.\n\n\n## For agents\n\n- 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\n- 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`\n- 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\n\n## Other comparisons with Cloud Run GPUs or Massed Compute\n\n- [Baseten vs Cloud Run GPUs](https://www.anchorterminal.com/compare/baseten-vs-cloud-run-gpus.md)\n- [Baseten vs Massed Compute](https://www.anchorterminal.com/compare/baseten-vs-massed-compute.md)\n- [Beam vs Cloud Run GPUs](https://www.anchorterminal.com/compare/beam-vs-cloud-run-gpus.md)\n- [Beam vs Massed Compute](https://www.anchorterminal.com/compare/beam-vs-massed-compute.md)\n- [Cerebrium vs Cloud Run GPUs](https://www.anchorterminal.com/compare/cerebrium-vs-cloud-run-gpus.md)\n- [Cerebrium vs Massed Compute](https://www.anchorterminal.com/compare/cerebrium-vs-massed-compute.md)\n- [Cloud Run GPUs vs CoreWeave](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-coreweave.md)\n- [Cloud Run GPUs vs Crusoe Cloud](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-crusoe-cloud.md)\n- [Cloud Run GPUs vs GPUsMarket](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-gpusmarket.md)\n- [Cloud Run GPUs vs Hugging Face Inference Endpoints](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-hugging-face-inference-endpoints.md)\n- [Cloud Run GPUs vs Hyperbolic](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-hyperbolic.md)\n- [Cloud Run GPUs vs Lambda Cloud](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-lambda.md)\n- [Cloud Run GPUs vs Nebius AI Cloud](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-nebius-ai-cloud.md)\n- [Cloud Run GPUs vs Northflank](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-northflank.md)\n- [Cloud Run GPUs vs Thunder Compute](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-thunder-compute.md)\n- [Cloud Run GPUs vs Together GPU Clusters](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-together-gpu-clusters.md)\n- [CoreWeave vs Massed Compute](https://www.anchorterminal.com/compare/coreweave-vs-massed-compute.md)\n- [Crusoe Cloud vs Massed Compute](https://www.anchorterminal.com/compare/crusoe-cloud-vs-massed-compute.md)\n- [GPUsMarket vs Massed Compute](https://www.anchorterminal.com/compare/gpusmarket-vs-massed-compute.md)\n- [Hugging Face Inference Endpoints vs Massed Compute](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-massed-compute.md)\n- [Hyperbolic vs Massed Compute](https://www.anchorterminal.com/compare/hyperbolic-vs-massed-compute.md)\n- [Koyeb vs Massed Compute](https://www.anchorterminal.com/compare/koyeb-vs-massed-compute.md)\n- [Lambda Cloud vs Massed Compute](https://www.anchorterminal.com/compare/lambda-vs-massed-compute.md)\n- [Massed Compute vs Modal](https://www.anchorterminal.com/compare/massed-compute-vs-modal.md)\n- [Massed Compute vs Nebius AI Cloud](https://www.anchorterminal.com/compare/massed-compute-vs-nebius-ai-cloud.md)\n- [Massed Compute vs Northflank](https://www.anchorterminal.com/compare/massed-compute-vs-northflank.md)\n- [Massed Compute vs Replicate Deployments](https://www.anchorterminal.com/compare/massed-compute-vs-replicate-deploy.md)\n- [Massed Compute vs Runpod](https://www.anchorterminal.com/compare/massed-compute-vs-runpod.md)\n- [Massed Compute vs Thunder Compute](https://www.anchorterminal.com/compare/massed-compute-vs-thunder-compute.md)\n- [Massed Compute vs Together GPU Clusters](https://www.anchorterminal.com/compare/massed-compute-vs-together-gpu-clusters.md)\n- [Massed Compute vs Vast.ai](https://www.anchorterminal.com/compare/massed-compute-vs-vast-ai.md)\n- [Massed Compute vs Verda](https://www.anchorterminal.com/compare/massed-compute-vs-verda.md)\n- [Cloud Run GPUs vs Koyeb](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-koyeb.md)\n- [Cloud Run GPUs vs Modal](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-modal.md)\n- [Cloud Run GPUs vs Replicate Deployments](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-replicate-deploy.md)\n- [Cloud Run GPUs vs Runpod](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-runpod.md)\n- [Cloud Run GPUs vs Vast.ai](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-vast-ai.md)\n- [Cloud Run GPUs vs Verda](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-verda.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Cloud Run GPUs vs Massed Compute", "url": "" } ], "description": "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.", "facts": [ "Cloud Run GPUs B 68.4", "Massed Compute E 42.6", "scores" ], "h1": "Cloud Run GPUs vs Massed Compute", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/cloud-run-gpus-vs-massed-compute", "published": "2026-10-01", "section": "tools", "title": "Cloud Run GPUs vs Massed Compute for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-massed-compute" }, "tokens": { "markdown": 5450, "slim": 3230 }, "version": 1 }