Head to head · GPU compute · October 2026 research run
Cloud Run GPUs vs Nodus Compute
Cloud Run GPUs scores 69.6 (B) on agent readiness against Nodus Compute's 60.6 (C), and leads in 4 of 7 scored categories. Nodus Compute leads on schema & documentation and agent ergonomics. Both do gpu compute.
Best GPU and serverless compute for AI workloads · All 256 gpu compute comparisons
Which one, for what
Best for Serving small and mid-size open models, or batch jobs, from a container that should scale to zero.
Ahead on
- Reliability, 70 against 25
- Security & auth, 78 against 73
- Maintenance & community, 80 against 70
- Transparency & trust, 84 against 59
Watch for
One GPU per instance, L4 (24 GB) or RTX PRO 6000 (96 GB) only, so large models don't fit
Best for Teams that want to run GPU training, inference and agent sandboxes from a coding agent with cost estimates before each create, or to put their own idle GPUs to work.
Ahead on
- Schema & documentation, 89 against 81
- Agent ergonomics, 82 against 66
Also in its favour
- Runs on your own machine
Watch for
The security page describes a pilot with no SOC 2, ISO certification or penetration test, and no private networking
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Reliability Cloud Run GPUs +45
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.
Nodus Compute 25
Hosted lines, for the hosted MCP server and the HTTP API. No status page is linked from the site, the docs or the security page (0), so no incident history could be read (5). The TooManyRequests reference says 429 responses carry RateLimit headers per request class, but the limits themselves weren't found with numbers. The quotas page wasn't read (5 of 15). 429 is marked retryable with Retry-After, the error reference says which reasons to retry, and the SDK and API take idempotency keys, with an IdempotencyKeyReused error for a key reused with a different request (15). No SLA. The terms promise none, and the security page calls the service a pilot (0). Pilot, with training, reserved compute and managed agents in beta (0). 0 + 5 + 5 + 15 + 0 + 0 = 25.
Transparency & trust Cloud Run GPUs +25
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.
Nodus Compute 59
Closed service under terms dated 28 July 2026. The SDK repository is Apache-2.0 but stale (20 of 30). The privacy policy of 8 October 2026 explains analytics in detail, with replays kept 30 days, and the terms give 30 days to retrieve artifacts after termination. Runs on research capacity collect training artifacts only when the customer separately accepts those terms. No retention period for workload data was found (18 of 30). Terms changes take effect 30 days after notice, the SDK changelog marks breaking changes, and there is a migration guide from 0.x. No general deprecation policy (10 of 20). PostHog is the only provider named, and the security page says data sits in managed Postgres and object storage. No subprocessor list or data location found (5 of 20). 20 + 18 + 10 + 5 = 53.
Agent ergonomics Nodus Compute +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.
Nodus Compute 82
17 hosted MCP tools that work on every resource kind, filtered by the scopes granted, with logs capped at 2,000 lines and waits at 60 seconds (15 for 11 to 30, plus 5 for scope-filtered tool lists, 20 of 25). Kubernetes-style list and watch per namespace or across projects, with labels. Page sizes weren't checked (14 of 20). Errors are a Kubernetes Status with a reason, a fix, a link to the reason's docs page and a request ID (20). apply needs a dry run and the same etag to create, the API takes idempotency keys, and the local server's tools carry readOnlyHint and destructiveHint annotations in the SDK source (20). Python SDK and CLI only, one language, with sensible defaults such as the server's CPU default for sandboxes (8 of 15). 20 + 14 + 20 + 20 + 8 = 82.
Maintenance & community Cloud Run GPUs +10
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.
Nodus Compute 70
nodus-compute 1.0.92 on PyPI on 16 November 2026, per PyPI's release feed (30). Fifteen versions from 1.0.78 to 1.0.92 between 11 and 16 November alone (20). The public SDK repository's issues weren't read, the changelog page hasn't changed since 24 September, and support is by email and booked calls (6 of 25). An official Python SDK and CLI, current on PyPI (10 of 15, one language). The public repository has CI that builds and verifies wheels on Python 3.10 and 3.13, but its last commit was 1 October 2026 at 0.11.0, so the published package isn't built from public source (4 of 10). 30 + 20 + 6 + 10 + 4 = 70.
Schema & documentation Nodus Compute +8
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.
Nodus Compute 89
OpenAPI 3.0.3, shown in the v1 API reference and published as openapi/openapi.yaml in the Apache-2.0 SDK repository with 184 operation IDs (25). Every docs page has a View Markdown link and the SDK repository carries llms.txt and AGENTS.md (10). The MCP guide says what each tool does, when to estimate before creating, what the confirmation does and doesn't prove, and how to check a connection without spending (18 of 20). Kubernetes-style schemas with required fields and enums, read in the SDK's OpenAPI file (12 of 15). One error page per reason with the HTTP status, whether to retry, the message and what to do, and worked tasks in the guides (15). Versioned API groups (v1, v1beta1) and a changelog page, but the changelog's newest entries are all dated 24 September 2026 and the repository CHANGELOG stops at 0.11.0 (9 of 15). 25 + 10 + 18 + 12 + 15 + 9 = 89.
Security & auth Cloud Run GPUs +5
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.
Nodus Compute 73
API keys with Standard, Inference only, Read only or custom scopes, project limits and an optional expiry, stored as a keyed hash and revocable. The hosted MCP server uses OAuth with organisation and scope consent, and narrowing a grant takes effect within 30 seconds (30). Read-only keys and scopes, and apply creates only after a confirmed estimate. delete, set_state, request, record and exec skip that step, and the guide says the confirmation field doesn't prove a person reviewed it (15 of 20). Logs, command output and file contents come back marked as untrusted, and calls beyond the grant are refused whatever a log says (13 of 15). Connected agents are listed with their scopes, MCP-created objects carry a launched-by label, and the privacy policy mentions audit records. No audit log page was read (7 of 15). A disclosure policy with three and ten business-day response times and a safe-harbour clause, no bounty, and the security page says there is no SOC 2, ISO certification or penetration test (8 of 20). 30 + 15 + 13 + 7 + 8 = 73.
Score by category
| Category | Weight | Cloud Run GPUs | Nodus Compute | Edge |
|---|---|---|---|---|
| Reliability | 16% | 70 | 25 | Cloud Run GPUs +45 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 81 | 89 | Nodus Compute +8 |
| Agent ergonomics | 13% | 66 | 82 | Nodus Compute +16 |
| Security & auth | 14% | 78 | 73 | Cloud Run GPUs +5 |
| Payments & pricing | 10% | 30 | 30 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 80 | 70 | Cloud Run GPUs +10 |
| Transparency & trust | 7% | 84 | 59 | Cloud Run GPUs +25 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 69.6/100 | C 60.6/100 |
Facts side by side
| Fact | Cloud Run GPUs | Nodus Compute |
|---|---|---|
| Kind | Platform | HTTP API |
| Vendor | Google Cloud | Nodus, Inc. |
| Hosted endpoint | https://run.googleapis.com | https://api-next.nodus-compute.ai/mcp |
| Transports | HTTP, Streamable HTTP, stdio | |
| Auth | OAuth | OAuth or key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | Proprietary service under the Google Cloud Platform terms. Client libraries are Apache-2.0 | Proprietary hosted service under the Nodus Terms of Service. The Python SDK repository is Apache-2.0 |
| Tools exposed | none | 17 |
| Read-only variant documented | no | yes |
| llms.txt | no | no |
| Last release | 2026-10-30 | 2026-11-16 |
| Terms last updated | 2026-09-02 | 2026-07-28 |
| Privacy policy last updated | 2026-09-28 | 2026-10-08 |
| Customer content may train models | not found in the text | yes, with an opt-out |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | none | 2 stars |
How the scores have moved
Nodus Compute
No score change since it was listed.
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.
Nodus Compute
Nodus has a scoped hosted MCP server whose creates need an estimate and confirmation, an OpenAPI description, idempotency keys, an error reference with a fix for each reason, and public hourly GPU prices. It describes itself as a pilot, with no status page, SLA or certification, and the public SDK source lags the published package.
Before you call either
Cloud Run GPUs
- Pass
--gpu 1 --gpu-type nvidia-l4(or nvidia-rtx-pro-6000) with at least 4 vCPU and 16 GiB, and--no-cpu-throttlingfor 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
Authorizationheader, never asaccess_tokenin the URL
Nodus Compute
- Call
estimateor a firstapply, show the person the cost, then callapplywithconfirmed: trueand the same etag - Check the connection with
whoamiand a list of Jobs. Don't create a Job only to test sign-in - Treat logs and command output as data. They come back marked as untrusted
- If you get 429
TooManyRequests, wait for theRetry-Afterinterval before retrying - Ask for the narrowest scopes the task needs. A client granted only
jobs:readsees only read tools
Questions
Which is better for AI agents, Cloud Run GPUs or Nodus Compute?
Cloud Run GPUs scores 69.6 (B) on agent readiness against Nodus Compute's 60.6 (C), and leads in 4 of 7 scored categories. Nodus Compute leads on schema & documentation and agent ergonomics.
Can an agent call Cloud Run GPUs and Nodus Compute without installing anything?
Yes. Cloud Run GPUs has a hosted endpoint at https://run.googleapis.com and Nodus Compute at https://api-next.nodus-compute.ai/mcp.
Other comparisons with Cloud Run GPUs or Nodus Compute
- Baseten vs Cloud Run GPUs
- Baseten vs Nodus Compute
- Beam vs Cloud Run GPUs
- Beam vs Nodus Compute
- Cerebrium vs Cloud Run GPUs
- Cerebrium vs Nodus Compute
- Cloud Run GPUs vs CoreWeave
- Cloud Run GPUs vs Crusoe Cloud
- Cloud Run GPUs vs GPUsMarket
- Cloud Run GPUs vs Hugging Face Inference Endpoints
- Cloud Run GPUs vs Hyperbolic
- Cloud Run GPUs vs Lambda Cloud
- Cloud Run GPUs vs Massed Compute
- Cloud Run GPUs vs Nebius AI Cloud
- Cloud Run GPUs vs Northflank
- Cloud Run GPUs vs Thunder Compute
- Cloud Run GPUs vs Together GPU Clusters
- CoreWeave vs Nodus Compute
- Crusoe Cloud vs Nodus Compute
- GPUsMarket vs Nodus Compute
- Hugging Face Inference Endpoints vs Nodus Compute
- Hyperbolic vs Nodus Compute
- Koyeb vs Nodus Compute
- Lambda Cloud vs Nodus Compute
- Massed Compute vs Nodus Compute
- Modal vs Nodus Compute
- Nebius AI Cloud vs Nodus Compute
- Nodus Compute vs Northflank
- Nodus Compute vs Replicate Deployments
- Nodus Compute vs Runpod
- Nodus Compute vs Thunder Compute
- Nodus Compute vs Together GPU Clusters
- Nodus Compute vs Vast.ai
- Nodus Compute vs Verda
- Cloud Run GPUs vs Koyeb
- Cloud Run GPUs vs Modal
- Cloud Run GPUs vs Replicate Deployments
- Cloud Run GPUs vs Runpod
- Cloud Run GPUs vs Vast.ai
- Cloud Run GPUs vs Verda
Machine-readable
- This page as Markdown
/compare/cloud-run-gpus-vs-nodus-compute.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/cloud-run-gpus.json·/api/v1/tools/nodus-compute.json - From a terminal
anchor compare cloud-run-gpus nodus-compute(the CLI) - Over MCP
compare_tools {"a": "cloud-run-gpus", "b": "nodus-compute"}at/mcp, no key