# Cloud Run GPUs vs GPUsMarket (slim)

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

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

Cloud Run GPUs scores 68.4 (B) on agent readiness against GPUsMarket's 39.6 (E), and leads in 6 of 7 scored categories. GPUsMarket leads on payments & pricing. Both do gpu compute.

- Cloud Run GPUs: B 68.4, rank #288 of 1486 · https://www.anchorterminal.com/tools/cloud-run-gpus.min.md
- GPUsMarket: E 39.6, rank #1318 of 1486 · https://www.anchorterminal.com/tools/gpusmarket.min.md
- Cloud Run GPUs, good for Serving small and mid-size open models, or batch jobs, from a container that should scale to zero. Ahead on Reliability, 70 against 33; Schema & documentation, 81 against 52; Agent ergonomics, 66 against 50; Security & auth, 78 against 30; Maintenance & community, 80 against 69; Transparency & trust, 84 against 50. Also No incidents deducted, where GPUsMarket loses 3 points for them.
- GPUsMarket, good for Cheap, short GPU rentals for open models behind an Ollama or OpenAI endpoint, where data sensitivity is low. Ahead on Payments & pricing, 30 against 20. Also Runs on your own machine.

| Category | Cloud Run GPUs | GPUsMarket |
| --- | --- | --- |
| Reliability (16%) | 70 | 33 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 81 | 52 |
| Agent ergonomics (13%) | 66 | 50 |
| Security & auth (14%) | 78 | 30 |
| Payments & pricing (10%) | 20 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 80 | 69 |
| Transparency & trust (7%) | 84 | 50 |

| Fact (where they differ) | Cloud Run GPUs | GPUsMarket |
| --- | --- | --- |
| Kind | Platform | HTTP API |
| Vendor | Google Cloud | Tyga.Cloud Ltd |
| Hosted endpoint | `https://run.googleapis.com` | `https://gpusmarket.com/api/v1` |
| Transports |  | stdio, SSE (legacy) |
| Auth | OAuth | API key |
| Licence | Proprietary service under the Google Cloud Platform terms. Client libraries are Apache-2.0 | Proprietary. The gpusmarket CLI and gpusmarket-host packages ship under Tyga.Cloud Ltd licences that allow use only with the platform, as obfuscated JavaScript |
| Tools exposed | none | 32 |
| llms.txt | no | yes |
| MCP registry | not listed | `io.github.jyswee/gpusmarket` |
| Last release | 2026-10-30 | 2026-10-16 |
| Terms last updated | 2026-09-02 | 2026-06-01 |
| Privacy policy last updated | 2026-09-28 | 2026-03-01 |
| Popularity | none | 1 stars, 79 npm/wk |

Why the edge:
- Security & auth, Cloud Run GPUs +48: 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.); GPUsMarket 30 (Account keys are all-powerful within the account, with no scopes, expiry or rotation documented, but each rental gets its own proxy token (15). The per-rental token limits inference access to one rental; no read-only key or confirmation for destructive calls (6). Peer rentals send prompts and outputs through individuals' machines, protected only by the terms, with no prompt-injection or untrusted-host guidance (2). Per-rental usage stats of requests, tokens and cost (5). No security.txt, disclosure policy, bug bounty or certification; a DPO address for breaches. The CLI and host packages are obfuscated, so they can't be audited (2). 15+6+2+5+2 = 30.)
- Reliability, Cloud Run GPUs +37: 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.); GPUsMarket 33 (Read with the hosted lines. No status page found; listing health is shown per listing only (0). No incident history to read (5). Rate limits published, 60 requests a minute per rental and 10 sign-ups an hour per IP (15). 429 is documented, but no Retry-After, backoff or idempotency guidance (3). The terms give no availability guarantee and put host outages on hosts (0). No beta label on the API (10). 0+5+15+3+0+10 = 33.)
- Transparency & trust, Cloud Run GPUs +34: 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.); GPUsMarket 50 (Closed, under Tyga.Cloud licences that are clear on use, but the docs call gpusmarket-host MIT open source while the package says otherwise (10). The privacy policy gives retention periods and names Stripe and MongoDB, while renter data on peer hosts falls outside its controls, which the terms disclaim (15). The terms promise 30 days' notice of material changes, with no deprecation policy or dated notices found (5). Processors partly named, with transfers under SCCs, and no host locations shown in the docs read (6). 10+15+5+6 = 36.)
- Schema & documentation, Cloud Run GPUs +29: 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.); GPUsMarket 52 (API and MCP reading. No OpenAPI or other machine-readable contract was found, and the MCP tool schemas couldn't be read because the published package is obfuscated; the repository's history says 2.4.7 added output schemas to all 32 tools, which is the vendor's claim (8). llms.txt as a complete API reference (10). llms.txt says when to use peer or cloud rentals, the proxy or the relay, and which workload each listing type serves (12). Parameters are listed by name without types, enums or required markers, apart from instance and workload types (6). curl examples for each flow, an error code list and a sample deploy response (11). npm versions, but no public changelog (5). 8+10+12+6+11+5 = 52.)
- Agent ergonomics, Cloud Run GPUs +16: 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.); GPUsMarket 50 (API and MCP reading. The README counts 32 MCP tools, and the decoded package includes 16 operator admin tools besides the renter tools, with no toolsets (5). Marketplace search takes `limit`, `offset`, `sort` and filters for GPU, price, VRAM, model, instance and workload type (20). Status codes with a one-line meaning each, no error bodies documented (10). No idempotency key on rent or deploy; stop and destroy return a cost summary (5). Only a Node CLI, though every proxy speaks the Ollama and OpenAI formats so existing SDKs work (10). 5+20+10+5+10 = 50.)
- Maintenance & community, Cloud Run GPUs +11: 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.); GPUsMarket 69 (gpusmarket 2.5.1 on 16 October 2026, 21 days before this check (30). Releases 2.4.18 to 2.5.1 between 17 August and 16 October, and gpusmarket-host 1.5.3 and 1.6.0 (20). Support by chat widget; the repository, which holds only a README, server.json and a licence, has no open issues and one star (5). Published in the official MCP registry under the verified io.github.jyswee namespace, though the newest registry version, 2.4.16, trails npm (12). No dependencies, but an obfuscated build and no public CI (2). 30+20+5+12+2 = 69.)