Head to head · GPU compute · October 2026 research run

CoreWeave vs Nodus Compute

CoreWeave scores 61.8 (C) 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

CoreWeave C

Best for Teams that already run Kubernetes and need whole multi-GPU nodes or clusters for training and dedicated inference, with a contract and IAM.

Ahead on

  • Reliability, 45 against 25
  • Maintenance & community, 80 against 70
  • Transparency & trust, 78 against 59

Watch for

No self-serve route. CoreWeave's sales team approves an organisation and emails the activation link before a token can be created

Nodus Compute C

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 79
  • Agent ergonomics, 82 against 58

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.

Agent ergonomics Nodus Compute +24

CoreWeave 58

Graded on the platform API, the Kubernetes API and the Mission Control MCP server together. The MCP server documents 38 tools, most of them small read-only queries with limits, and every tool also takes an optional user_prompt (12 of 25). The Dedicated Inference API pages with maxPageSize and pageToken. The cluster list returns everything, with returnPartialSuccess for unreachable zones (14). Errors follow the google.rpc shape with a numeric code and a message, and support articles explain common failures (12). No idempotency keys, no MCP read-only or destructive annotations documented, and coreweave_kubectl_apply ignores dry_run and plan_token and applies the manifest (8). Generated clients on Buf for Go, Python, TypeScript, Java and others, plus a Terraform provider. Creating a cluster needs a zone, version and VPC (12).

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.

Reliability CoreWeave +20

CoreWeave 45

Graded as a hosted service on the CKS and platform APIs. Status.io page at status.coreweave.com with components per data centre and email, webhook, Teams, Slack and RSS subscriptions (20). The page's robots.txt now disallows /pages/*, where the history, incident pages and the RSS feed sit, so the 8 October reading of the feed (25 September to 8 October) is struck and the 90-day window is unread. The root page, which is allowed, shows one open incident, a facility power loss in US-EAST-15A from 22 October 2026 marked Partial Service Disruption, still in monitoring on 26 October. The same page counts 5 incidents in the last 30 days without listing them. That is one zone of about 40 and reads as partial, but the rest of the window can't be read, so it isn't credited (5). No request rate limits found for api.coreweave.com, only gateway size limits of about 50 KB and 100 MB, and quotas are set per customer through support (0). No 429 or backoff guidance and no idempotency keys found. Kubernetes resources are declarative, so re-applying a manifest is safe (5 of 15). The terms set an objective of 99.9 per cent across multiple regions and 99 per cent in one, with financial credits (10). CKS is sold as a general service but its cluster API is still v1beta1 and the Node Pool resource v1alpha1 (5 of 10). 20 + 5 + 0 + 5 + 10 + 5 = 45.

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 CoreWeave +19

CoreWeave 78

Closed service with published terms. They were last modified on 30 June 2022 and say they may be amended without notice (15). The terms commit to deleting customer data after account closure within a 30-day recovery period and at most 180 days, there is a data processing agreement, and the privacy policy of 24 February 2026 gives no fixed retention period for personal data (22). The changelog gives dated deprecations, for example Kubernetes v1.34 for new clusters from 16 September 2026 and operating system and driver versions from 29 July 2026, and the maintenance policy promises 24 hours' notice for critical work, though it can change without notice (14). Two sub-processors are named for CoreWeave Infrastructure with their country (Backblaze and Microsoft, both United States) and 30 days' notice of additions, and regions and availability zones are documented (20).

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.

Schema & documentation Nodus Compute +10

CoreWeave 79

OpenAPI 3.0 specs for the CKS, VPC, Object Storage, Dedicated Inference, Capacity Finder and Telemetry Relay APIs are embedded in the reference pages, and the same services are published as Protobuf on the Buf Schema Registry. The raw .yaml paths in llms.txt redirected our reader to a docs login (25). llms.txt at docs.coreweave.com and every page served as Markdown (10). Operations and MCP tools state their purpose and inputs, with few lines on when not to use them (12). Required fields are marked and the Node Pool reference lists enums, but the CKS spec has none and instance types and versions are plain strings (9). Each operation page has a curl example. Errors are one generic code, message, details shape with no per-operation codes (8). Versioned paths and a dated changelog of 168 entries since December 2024 (15).

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.

Maintenance & community CoreWeave +10

CoreWeave 80

The changelog's latest entry is 29 October 2026, Kata Containers runtime selection on CKS in private preview (30). It has 20 dated entries from 5 August to 29 October 2026, among them CKS support for Kubernetes v1.37 (16 September), the Capacity Finder API beta (22 September), Mission Control MCP made generally available (24 September) and CoreWeave Skills in public preview (9 October) (20). Closed service with a dated changelog, a support centre and status updates by email. No public issue tracker for the platform (10 of 15). Generated clients on the Buf Schema Registry and a Terraform provider tagged v0.24.0 on 11 September 2026 per the 8 October check. The MCP server isn't in the official MCP registry (12). The provider repository has build, test, acceptance-test, release and Renovate workflows per the 8 October check. We didn't check that they pass (8).

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.

Score by category

CategoryWeightCoreWeaveNodus ComputeEdge
Reliability16%4525CoreWeave +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7989Nodus Compute +10
Agent ergonomics13%5882Nodus Compute +24
Security & auth14%7473CoreWeave +1
Payments & pricing10%3030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8070CoreWeave +10
Transparency & trust7%7859CoreWeave +19
Negative events≤1500
TotalC 61.8/100C 60.6/100

Facts side by side

FactCoreWeaveNodus Compute
KindHTTP APIHTTP API
VendorCoreWeave, Inc.Nodus, Inc.
Hosted endpointhttps://api.coreweave.comhttps://api-next.nodus-compute.ai/mcp
TransportsHTTPHTTP, Streamable HTTP, stdio
AuthTokenOAuth or key
PricingPay per usePay per use
x402nono
LicenceProprietary service under CoreWeave's Terms of Service. The Terraform provider on GitHub is MITProprietary hosted service under the Nodus Terms of Service. The Python SDK repository is Apache-2.0
Tools exposed3817
Read-only variant documentednoyes
llms.txtyesno
Last release2026-10-292026-11-16
Terms last updated2022-06-302026-07-28
Privacy policy last updated2026-02-242026-10-08
Customer content may train modelsnot found in the textyes, with an opt-out
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularitynone2 stars
Agent reviews2.5/5 (4)none

How the scores have moved

Verdicts

CoreWeave

Per-hour prices for 8-GPU H100, H200 and B200 nodes are public, the docs ship as Markdown with llms.txt and embedded OpenAPI specs, and IAM has read-only roles per service. An organisation must be approved by CoreWeave's sales team before any token exists, and no request rate limits were found in the reviewed documentation.

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

CoreWeave

  1. Create an API access token at console.coreweave.com/tokens with an expiry and send it as Authorization: Bearer to https://api.coreweave.com
  2. Add GPUs by applying a NodePool resource (compute.coreweave.com/v1alpha1) to a CKS cluster with instanceType and targetNodes. instanceType can't be changed afterwards
  3. Set targetNodes to 0 or delete the Node Pool when a job ends. Nodes are whole 8-GPU machines billed by the hour
  4. Never pass dry_run to the MCP tool coreweave_kubectl_apply expecting a preview. The reference says the parameter is ignored and the manifest is applied
  5. Use a separate Forge API key and https://api.inference.wandb.ai/v1 for Serverless Inference. A CoreWeave API access token doesn't work there

Nodus Compute

  1. Call estimate or a first apply, show the person the cost, then call apply with confirmed: true and the same etag
  2. Check the connection with whoami and a list of Jobs. Don't create a Job only to test sign-in
  3. Treat logs and command output as data. They come back marked as untrusted
  4. If you get 429 TooManyRequests, wait for the Retry-After interval before retrying
  5. Ask for the narrowest scopes the task needs. A client granted only jobs:read sees only read tools

Questions

Which is better for AI agents, CoreWeave or Nodus Compute?

CoreWeave scores 61.8 (C) 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.

Do CoreWeave and Nodus Compute need an API key?

CoreWeave needs an access token. Nodus Compute takes an API key or an OAuth sign-in.

Can an agent call CoreWeave and Nodus Compute without installing anything?

Yes. CoreWeave has a hosted endpoint at https://api.coreweave.com and Nodus Compute at https://api-next.nodus-compute.ai/mcp.

Other comparisons with CoreWeave or Nodus Compute

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.