# Cloud Run GPUs vs Nebius AI Cloud (slim)

> Nebius AI Cloud scores 71.2 (BB) to Cloud Run GPUs's 68.4 (B) for gpu compute. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/cloud-run-gpus-vs-nebius-ai-cloud.md (~4,450 tokens) · this version ~2,080 tokens · JSON https://www.anchorterminal.com/compare/cloud-run-gpus-vs-nebius-ai-cloud.json · canonical https://www.anchorterminal.com/compare/cloud-run-gpus-vs-nebius-ai-cloud
- 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)

Nebius AI Cloud scores 71.2 (BB) on agent readiness against Cloud Run GPUs's 68.4 (B), and leads in 4 of 7 scored categories. Cloud Run GPUs leads on transparency & trust. Both do gpu compute.

- Cloud Run GPUs: B 68.4, rank #288 of 1486 · https://www.anchorterminal.com/tools/cloud-run-gpus.min.md
- Nebius AI Cloud: BB 71.2, rank #167 of 1486 · https://www.anchorterminal.com/tools/nebius-ai-cloud.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 Transparency & trust, 84 against 77.
- Nebius AI Cloud, good for Teams that want whole GPU VMs or InfiniBand clusters in Europe, the UK, Israel or the US with IAM, Terraform and an SLA, and are content to manage endpoint lifecycles themselves. Ahead on Reliability, 77 against 70; Agent ergonomics, 77 against 66. Also Agent-ready, a grade of BB or better; Runs on your own machine.

| Category | Cloud Run GPUs | Nebius AI Cloud |
| --- | --- | --- |
| Reliability (16%) | 70 | 77 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 81 | 78 |
| Agent ergonomics (13%) | 66 | 77 |
| Security & auth (14%) | 78 | 81 |
| Payments & pricing (10%) | 20 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 80 | 82 |
| Transparency & trust (7%) | 84 | 77 |

| Fact (where they differ) | Cloud Run GPUs | Nebius AI Cloud |
| --- | --- | --- |
| Kind | Platform | HTTP API |
| Vendor | Google Cloud | Nebius |
| Hosted endpoint | `https://run.googleapis.com` | `https://api.nebius.cloud` |
| Transports |  | HTTP, stdio |
| Auth | OAuth | OAuth or key |
| Price for gpu compute | not published | $1.35 per GPU-hour |
| Licence | Proprietary service under the Google Cloud Platform terms. Client libraries are Apache-2.0 | Proprietary service under the Nebius Services Agreement. The API definitions, the Go, Python and JavaScript SDKs and the MCP server on GitHub are MIT |
| llms.txt | no | yes |
| Last release | 2026-10-30 | 2026-10-21 |
| Terms last updated | 2026-09-02 | 2026-09-28 |
| Privacy policy last updated | 2026-09-28 | 2026-09-23 |
| Terms restrict benchmarking | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | none | 4.1k npm/wk, 469k PyPI/wk |
| Agent reviews | none | 3/5 (4) |

Why the edge:
- Agent ergonomics, Nebius AI Cloud +11: 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.); Nebius AI Cloud 77 (Lists take `pageSize` and `pageToken`, gets take a `view` and there are get-by-name calls; no field selection (15 of 25). Token pagination everywhere, filters on audit events, lists otherwise scoped only by `parentId` (14). Errors use canonical gRPC codes mapped to HTTP, each documented with a cause and a fix, with field-level violations and a `retry_type` in the details (17). `X-Idempotency-Key` on modifying calls and `resourceVersion` for concurrent updates; the header is documented in the API repository with a gRPC example, not on the REST pages (18). An endpoint needs a parent project, image, platform and preset, the subnet defaults to the project's; SDKs for Go, Python and JavaScript, a CLI and a Terraform provider (13).)
- Reliability, Nebius AI Cloud +7: 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.); Nebius AI Cloud 77 (Graded as a hosted service on the REST API. Statuspage at status.nebius.com with component history (20). The 8 October reading came from the page's /api/ incident feed, which its robots.txt disallows, so it is struck. The history pages and history.atom, read on 1 November, list 27 incidents from 5 August to 31 October 2026 plus one scheduled maintenance. Each names one region, one service or a subset of nodes or users, among them the us-central1 degradation of 19 and 20 August (with a published post-mortem), InfiniBand faults in eu-west2, a power fault on several dozen nodes on 7 October and Token Factory errors, which is a separate product. The widest, on 18 October, says the console and IAM were unavailable for about ten minutes, and its incident page names only Identity and Access Management in EU-NORTH1, with impact none. This run reads incidents limited to one region, product or share of users as minor, whatever the vendor's label, so the line is minor only (20, 0 before). Resource quotas are published with numbers per region, but no request rate limits were found in the reviewed documentation or llms.txt on 1 November (5 of 15). `RESOURCE_EXHAUSTED` maps to HTTP 429, errors can carry a `TooManyRequests` detail and a `retry_type` of `CALL`, `UNIT_OF_WORK` or `NOTHING`, and `X-Idempotency-Key` covers modifying calls. No Retry-After or backoff intervals found (12 of 15). SLA of 99.5 per cent a month per virtual machine with credits of 10 to 30 per cent. Serverless AI is not on the list of services with a service level (10). Compute and Serverless AI are generally available. Audit Logs, Monitoring and Logging are in preview (10). 20 + 20 + 5 + 12 + 10 + 10 = 77.)
- Transparency & trust, Cloud Run GPUs +7: 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.); Nebius AI Cloud 77 (Closed service under a Services Agreement published 15 September 2026 and effective 28 September, with nine earlier versions archived; the API definitions, SDKs and MCP server are MIT (15). Privacy policy of 23 September 2026 and a DPA of 15 September agree that customer data is processed as a processor and deleted or returned at the customer's choice on termination; the agreement gives 72 hours for deletion after a suspension period lapses, and no retention period for disks after deletion was found (22). CLI release notes carry dated removals, such as the IAM v1 project and tenant services supported until 16 December 2026, and Kubernetes has a version deprecation policy; no general notice period for the API (13). The sub-processor list names each Nebius entity and outside processor with its location and transfer mechanism, and the docs name ten regions (20).)