Head to head · GPU compute · October 2026 research run

Cerebrium vs Nodus Compute

Nodus Compute scores 60.6 (C) on agent readiness against Cerebrium's 54.4 (C), and leads in 4 of 7 scored categories. Cerebrium leads on reliability, payments & pricing and transparency & trust. Both do gpu compute.

Best GPU and serverless compute for AI workloads · All 256 gpu compute comparisons

Which one, for what

Cerebrium C

Best for Teams serving their own models as real-time endpoints (voice, LLM, image) who want per-second billing, multi-region placement and a scriptable management API.

Ahead on

  • Reliability, 48 against 25
  • Payments & pricing, 45 against 30
  • Transparency & trust, 64 against 59

Watch for

disable_auth defaults to true, so a deployed endpoint answers without a token unless the owner changes it

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 70
  • Agent ergonomics, 82 against 49
  • Security & auth, 73 against 60
  • Maintenance & community, 70 against 65

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 +33

Cerebrium 49

No field selection. A limit parameter on five list operations, and app and run objects are small (12 of 25). The audit log and runs page with limit and nextToken and filter by status, status code and time, though other lists use page, pageSize or offset (14 of 20). Errors are a message string with 400 or 401. Deployed endpoints return 200, 401, 403, 404 or 5xx, and a function can set its own status_code (10 of 20). No idempotency keys. Async calls return a run_id that can be listed and cancelled (5 of 20). Defaults are sensible (min_replicas 0, cooldown 60) and cerebrium init writes a working config, but there is a CLI only and no language SDK (8 of 15). Docs per the 8 October check, not re-read on 4 November; the CLI clone confirms --output json on list commands since 10 August. 12 + 14 + 10 + 5 + 8 = 49.

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 Cerebrium +23

Cerebrium 48

Graded as a hosted service. Status page at status.cerebrium.ai with 11 components and 90 days of history, per the 8 October check, not re-read on 4 November (cerebrium.ai's terms bar robots and automatic means) (20). The 8 October reading covered the window to that day. Since 6 August it held degradations of 5 hours 7 minutes on 19 August (US, upstream) and 7 hours 20 minutes on 2 September (EU, provider network), both partial; 9 October to 4 November is unread, so the line keeps its recorded award (10). No request rate limits found. Plans publish concurrency caps of 5 GPUs and 500 containers on Hobby and 30 and 1,000 on Standard (5 of 15). No 429 or backoff guidance for callers found. Webhook forwarding retries failed deliveries and the docs ask for idempotent webhook receivers, partly met, kept (3 of 15). No SLA found. The 99.9 and 99.999 per cent uptime figures on the site are claims without terms (0). Endpoints, the CLI and the REST API are GA, while multi-region deployment and checkpointing are marked beta (10). Docs and status per the 8 October check, not re-read on 4 November. 20 + 10 + 5 + 3 + 0 + 10 = 48.

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.

Schema & documentation Nodus Compute +19

Cerebrium 70

Public OpenAPI 3.0 spec for the management API with 94 operations on 73 paths. Deployed endpoints take whatever the owner's function defines (25). llms.txt and a .md twin of every docs page (10). Operation descriptions are one line each. The guides say when to use the protected tier, async runs or a custom runtime (12 of 20). Required fields are marked, but the spec has no enums (valid values such as member and billing sit in prose) and several arrays and objects are untyped (7 of 15). The guides carry many worked examples. The spec has no examples and documents only 400 and 401 errors with a message string (8 of 15). Paths are versioned v2, v3 and v4 and CLI releases are dated on GitHub, but the spec version is a fixed 1.0.0 and no platform changelog was found (8 of 15). Docs and spec per the 8 October check, not re-read on 4 November. 25 + 10 + 12 + 7 + 8 + 8 = 70.

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.

Payments & pricing Cerebrium +15

Cerebrium 45

No machine payment protocol (0). Per-second GPU, CPU and memory prices and the storage price are published without a login (20). The Hobby plan has no fee, but compute is billed from the first second, no free compute allowance is stated and the pricing page does not say whether a card is needed, partly met, kept (10 of 20). Signup and cerebrium login are browser flows (0). Pricing per the 8 October check, not re-read on 4 November. 0 + 20 + 10 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Nodus Compute 30

No x402, MPP or L402. A TopUp through MCP returns a checkout link for a person (0). Hourly prices per GPU and CPU configuration are public without a login (30). A new organisation needs a verified email and card, so no card-free start was found (0). A person signs up and approves OAuth in a browser (0). 0 + 30 + 0 + 0 = 30.

Security & auth Nodus Compute +13

Cerebrium 60

Service account tokens expire after up to one year (or never, if set to 0), are limited to 1 to 50 named projects and are revoked by deleting the account. Inference API keys are separate and can be deleted. No per-action scopes, and the CLI's SECURITY.md says tokens sit in plaintext in a config file with mode 0644 (20 of 30). Users have owner, member and billing roles, but tokens have no read-only form, and disable_auth defaults to true, so deployed endpoints answer without a token unless the owner changes it (5 of 20). Runs the owner's code and returns its output (10). Docs readings per the 8 October check, not re-read on 4 November. Audit log of 22 actions with actor, IP address and outcome, in the dashboard and over the API, on Standard (7 days) and Enterprise (30 days) only (12 of 15). SOC 2 Type II announced on 8 July 2026, HIPAA BAA on request, a trust centre, and disclosure to security@cerebrium.ai. No security.txt and no bug bounty found (13 of 20). No advisory for cerebrium on OSV on 4 November. 20 + 5 + 10 + 12 + 13 = 60.

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.

Maintenance & community Nodus Compute +5

Cerebrium 65

CLI v2.9.0 tagged on 16 September 2026, 49 days before the check, the newest tag in the repository; commits since (20 and 21 October, licence notices and a Go 1.26.10 upgrade) are untagged (20). Five tagged releases since 6 August 2026 (v2.5.4 on 7 August, v2.6.0, v2.7.0, v2.8.0, v2.9.0) (20). Closed service with a Discord community and Slack or Intercom support by plan. No platform changelog, and we couldn't read the GitHub issue tracker (8 of 25). The CLI ships on PyPI, Homebrew and as binaries. There is no language SDK (10 of 15). The repository has lint and test workflows and now pins Go 1.26.10. CI status wasn't visible in the clone (7 of 10). 20 + 20 + 8 + 10 + 7 = 65.

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

CategoryWeightCerebriumNodus ComputeEdge
Reliability16%4825Cerebrium +23
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7089Nodus Compute +19
Agent ergonomics13%4982Nodus Compute +33
Security & auth14%6073Nodus Compute +13
Payments & pricing10%4530Cerebrium +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6570Nodus Compute +5
Transparency & trust7%6459Cerebrium +5
Negative events≤15-20
TotalC 54.4/100C 60.6/100

Facts side by side

FactCerebriumNodus Compute
KindPlatformHTTP API
VendorCerebrium Inc.Nodus, Inc.
Hosted endpointhttps://rest.cerebrium.aihttps://api-next.nodus-compute.ai/mcp
TransportsHTTPHTTP, Streamable HTTP, stdio
AuthAPI keyOAuth or key
PricingFreemiumPay per use
x402nono
LicenceProprietary service under Cerebrium's terms of service. The CLI is MITProprietary hosted service under the Nodus Terms of Service. The Python SDK repository is Apache-2.0
Tools exposednone17
Read-only variant documentednoyes
llms.txtyesno
Last release2026-09-162026-11-16
Terms last updatedno date given2026-07-28
Privacy policy last updatedno date given2026-10-08
Customer content may train modelsnot found in the textyes, with an opt-out
Terms restrict automated accessyesnot 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

How the scores have moved

Verdicts

Cerebrium

Per-second GPU prices are public, a 94-operation OpenAPI spec covers the management API, and service account tokens expire and are limited to named projects. Deployed endpoints are callable without a token unless disable_auth = false is set, and no request rate limits, 429 handling or SLA 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

Cerebrium

  1. Set disable_auth = false in cerebrium.toml before deploying. The default leaves the endpoint callable by anyone with the URL
  2. Authenticate headless with CEREBRIUM_SERVICE_ACCOUNT_TOKEN. cerebrium login opens a browser
  3. Raise response_grace_period for long work. It defaults to 15 minutes and async runs stop at 12 hours
  4. Send ?async=true to get a run_id with HTTP 202, and add webhookEndpoint because async calls return no result to the caller
  5. Check the plan before choosing hardware. A100, H100, H200, B200 and RTX PRO 6000 need Standard, and protected compute bills at twice the listed rate

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, Cerebrium or Nodus Compute?

Nodus Compute scores 60.6 (C) on agent readiness against Cerebrium's 54.4 (C), and leads in 4 of 7 scored categories. Cerebrium leads on reliability, payments & pricing and transparency & trust.

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

Yes. Cerebrium has a hosted endpoint at https://rest.cerebrium.ai and Nodus Compute at https://api-next.nodus-compute.ai/mcp.

Other comparisons with Cerebrium 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.