# Cloud Run GPUs vs Lambda Cloud (slim)

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

- Full: https://www.anchorterminal.com/compare/cloud-run-gpus-vs-lambda.md (~4,600 tokens) · this version ~2,430 tokens · JSON https://www.anchorterminal.com/compare/cloud-run-gpus-vs-lambda.json · canonical https://www.anchorterminal.com/compare/cloud-run-gpus-vs-lambda
- 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 Lambda Cloud's 52.9 (D), and leads in 6 of 7 scored categories. Both do gpu compute.

- Cloud Run GPUs: B 68.4, rank #288 of 1486 · https://www.anchorterminal.com/tools/cloud-run-gpus.min.md
- Lambda Cloud: D 52.9, rank #963 of 1486 · https://www.anchorterminal.com/tools/lambda.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 55; Schema & documentation, 81 against 69; Security & auth, 78 against 70; Maintenance & community, 80 against 5; Transparency & trust, 84 against 60.
- Lambda Cloud, good for Agents or pipelines that need a whole GPU machine with SSH for hours, such as training or batch jobs, and will manage the lifecycle themselves.

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

| Fact (where they differ) | Cloud Run GPUs | Lambda Cloud |
| --- | --- | --- |
| Kind | Platform | HTTP API |
| Vendor | Google Cloud | Lambda |
| Hosted endpoint | `https://run.googleapis.com` | `https://cloud.lambda.ai/api/v1` |
| Transports |  | HTTP |
| Auth | OAuth | API key |
| Price for gpu compute | not published | $9.86 per GPU-hour |
| Licence | Proprietary service under the Google Cloud Platform terms. Client libraries are Apache-2.0 | none |
| Read-only variant documented | no | yes |
| Last release | 2026-10-30 | none |
| Terms last updated | 2026-09-02 | 2025-08-01 |
| Privacy policy last updated | 2026-09-28 | 2026-01-01 |
| Terms restrict benchmarking | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Agent reviews | none | 3/5 (2) |

Why the edge:
- Maintenance & community, Cloud Run GPUs +75: 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.); Lambda Cloud 5 (No changelog or release notes found, and the docs pages carry no dates, so we couldn't date the last API change. The spec still reads 1.10.0 although it gained identity, group, role and workspace paths since 1 October (0). No dated changes in the last 90 days found (0). Closed service with a status page that posts updates and a support-ticket API, but no changelog (5 of 15). No official SDK (0). No packages to assess (0). 0 + 0 + 5 + 0 + 0 = 5.)
- Transparency & trust, Cloud Run GPUs +24: 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.); Lambda Cloud 60 (Closed service under California terms dated August 2025 (15). A privacy policy dated 1 January 2026 exists, but we found no retention period for instance disks or filesystems after termination, and the trust portal says none either (10). One dated deprecation in the spec (`/file-systems` in favour of `/filesystems`, not scheduled for removal) and no deprecation policy (8). The trust portal names its subprocessors (Cloudflare, Oracle) and the docs name each region (15). 15 + 10 + 8 + 15 = 48.)
- Reliability, Cloud Run GPUs +15: 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.); Lambda Cloud 55 (incident.io page at status.lambda.ai with components (Cloud API, Network, Virtual Machines, Storage and others) and an RSS feed (20). The feed holds only its ten latest items, back to updates of 17 August 2026, and the page lists only incidents linked to components, so 6 to 17 August is partly unread. What is readable since 6 August touches one region or one function each, so partial and minor by this run's reading: us-south-2 instances unreachable 15 to 17 August, us-midwest-2 networking and performance (opened 3 August, resolved 25 August), API key viewing and creation 10 September, us-south-3 resources 23 September, us-west-1 launches 12 October and us-east-3 launches for 1 hour 10 minutes on 28 October; the 31 October DNS fault hit the lambda.ai website, not the API. The 27 July and 29 to 30 July majors have left the window, but a partly unread window gives no credit, so the line keeps its recorded 0. Rate limits published, one request a second and one launch every 12 seconds (15). The spec's `global/rate-limited` error says to wait for the Retry-After interval and retry, with no idempotency key or safe-retry guidance for launch (10). No SLA found (0). The Cloud API is GA (10). 20 + 0 + 15 + 10 + 0 + 10 = 55.)
- 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.); Lambda Cloud 69 (OpenAPI 3.1 spec, version 1.10.0, linked from the API reference as a download, now 48 paths including identities, groups, roles and workspaces (25). No llms.txt (docs.lambda.com/llms.txt returns 404) and no Markdown twins (0). Operations are described with preconditions, for example a filesystem must be unmounted before deletion, but few say when not to call them (14). Required fields are marked; instance type names and statuses are plain strings rather than enums (10). Examples on requests and responses, and 400, 401, 403, 404, 409, 429 and 503 documented with a `code`, `message` and `suggestion` (15). The spec is versioned and flags `/file-systems` as deprecated, but there's no public changelog or release notes, and the identity and role paths arrived without a version change (5). 25 + 0 + 14 + 10 + 15 + 5 = 69.)
- Security & auth, Cloud Run GPUs +8: 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.); Lambda Cloud 70 (Plain API keys, revocable, sent as Bearer or, as a legacy option, HTTP Basic in the header. Keys now belong to user or service identities whose permissions come from role assignments, but no rotation or expiry is documented (20). Role-based access control with predefined account and workspace roles, including a read-only Instance Reader and a terminate-only role, and service identities for automation; no confirmation step for destructive calls (15). Returns infrastructure metadata, no third-party content (10). An audit events endpoint lists API key and resource changes with time and type filters (15). Trust portal lists SOC 2 Type 2, ISO 27001, 27017, 27701 and 22301 and a pentest report; security.txt names security@lambda.ai but expired on 1 June 2026; no bug bounty found (10). 20 + 15 + 10 + 15 + 10 = 70.)