Head to head · GPU compute · October 2026 research run

Nodus Compute vs Thunder Compute

Nodus Compute scores 60.6 (C) on agent readiness against Thunder Compute's 52.5 (D), and leads in 3 of 7 scored categories. Thunder Compute leads on reliability, maintenance & community and transparency & trust. Both do gpu compute.

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

Which one, for what

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 48
  • Security & auth, 73 against 51

Also in its favour

  • Runs on your own machine
  • No incidents deducted, where Thunder Compute loses 5 points for them

Watch for

The security page describes a pilot with no SOC 2, ISO certification or penetration test, and no private networking

Thunder Compute D

Best for Agents in coding tools that rent a single persistent GPU machine for development, fine-tuning or a model server, at low hourly prices and over MCP.

Ahead on

  • Reliability, 65 against 25
  • Maintenance & community, 79 against 70
  • Transparency & trust, 66 against 59

Watch for

No rate limits, 429 guidance or SLA were found in the reviewed documentation, and the terms disclaim availability

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 Thunder Compute +40

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.

Thunder Compute 65

Graded on the hosted lines for the REST API and the hosted MCP server. Thunder Compute's terms bar robots, scrapers and data-gathering tools on the Services, so its site, status page and API host weren't requested on 4 November and the readings below are per the 9 October check, not re-read on 4 November. Status page on incident.io at status.thundercompute.com with Website, API and Instances components and monthly history (20). No incidents listed for July to 9 October 2026. The rest of the window is unread and not credited, so the line keeps its recorded award (30). No rate limits with numbers were found in the docs or the OpenAPI document (0). No 429 or retry guidance in the docs. The CLI source reads a Retry-After header on errors, adding a duplicate SSH key is a no-op and port updates are atomic, but instance creation has no idempotency key (5 of 15, a partial value kept and flagged). No SLA found, and the terms say availability is not guaranteed (0). The API and MCP server carry no beta label (10). 20+30+0+5+0+10 = 65.

Agent ergonomics Nodus Compute +34

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.

Thunder Compute 48

No field selection, and GET /instances/list returns every instance in one map. The MCP server has 28 tools in one set, with no toolsets found (12 of 25). limit up to 100, page_token and a status filter on sandboxes and sandbox logs. No pagination on instances, snapshots or keys (8 of 20). Errors carry a numeric code, a string error such as invalid_request and a message, documented per operation (14 of 20). Duplicate SSH keys are a no-op and port changes are deduplicated in one transaction, but create calls have no idempotency key. MCP tool annotations were not read (7 of 20). A create call needs five fields. The official Python SDK covers sandboxes only, and the Go CLI covers instances (7 of 15). All of this is per the 9 October check, not re-read on 4 November. 12+8+14+7+7 = 48.

Security & auth Nodus Compute +22

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.

Thunder Compute 51

The MCP server uses OAuth 2.0 with discovery, refresh tokens and ten scopes that separate read from write for instances, snapshots and sandboxes. The REST API uses named API tokens that are created and revoked one at a time, with no scopes found. No secret travels in a URL (25 of 30). Read scopes exist, and the CLI requires --yes to delete without a prompt. No confirmation step for delete_instance or delete_snapshot was found in the MCP docs, and both are described as irreversible (8 of 20). Responses are infrastructure metadata, except run_command output and sandbox logs, with no guidance found on untrusted output (8 of 15). GET /tokens returns creation and last-used times and sandbox logs are listed by API. No audit log was found (4 of 15). No security.txt, disclosure policy or bug bounty was found. llms.txt states SOC 2 Type II and GDPR compliance with no report or trust page linked, and the DPA promises an audit summary on written request and incident notice within 72 hours (6 of 20). The site readings are per the 9 October check, not re-read on 4 November. 25+8+8+4+6 = 51.

Schema & documentation Nodus Compute +19

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.

Thunder Compute 70

Public OpenAPI 3.1 document at api.thundercompute.com:8443/openapi.json with 41 operations and 72 schemas (25). llms.txt, llms-full.txt and a Markdown copy of every docs page (10). 28 of 41 operations have a description. Instance operations state side effects such as the private key being returned once, while most sandbox operations have a summary only (12 of 20). Required fields are marked, but the document has six enums, gpu_type and template are free strings and the instance list is a map keyed by ID (8 of 15). 12 examples and one error schema with code, error and message. Most operations document 400, 401 and 500, and none documents 429 (9 of 15). /v1 and /v2 paths, with legacy endpoints and the mode field marked as retained or deprecated. No API changelog was found. The CLI has a dated one (6 of 15). No published copy of the MCP tool definitions was found, so they were not read. All of this is per the 9 October check, not re-read on 4 November. 25+10+12+8+9+6 = 70.

Maintenance & community Thunder Compute +9

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.

Thunder Compute 79

The newest CLI release is v2.2.0 of 27 October 2026, which adds tnr report and SSH and interface fixes (30). Three CLI releases in the 90 days from 6 August, v2.0.72 (15 September), v2.1.0 (16 September) and v2.2.0, each changing code (20). A dated CLI changelog, a support address and a Discord server the docs say the founders answer. No API changelog. GitHub issues weren't re-read (github.com refused), so 10 of 15 per the 9 October check. Listed in the official MCP registry as io.github.Thunder-Compute/thunder-compute per the 9 October check, and the CLI and the thunder-sandbox SDK are current (13 of 15). The CLI repository has tests, a lint configuration and release checksum verification, and still no CI workflow (.github holds only copilot-instructions.md) (6 of 10). 30+20+10+13+6 = 79.

Transparency & trust Thunder Compute +7

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.

Thunder Compute 66

Closed service under Terms and Conditions dated 28 September 2026 and Delaware law. The CLI is MIT. The OpenAPI document names Apache 2.0 and a placeholder terms address (15 of 30). The privacy policy of 28 September 2026 says instance data is not used to train AI models, the terms say instance data may be deleted 60 days after the account was last active, and a DPA is published. The sub-processor list names Firebase for sign-in while the MCP docs name Stytch, and the FAQ says instances are EC2 while the list names Azure (18 of 30). No deprecation policy. The terms allow changes without notice, and the billing docs say rates can change without notice. Legacy endpoints are marked as retained for compatibility (6 of 20). Five sub-processors with locations are listed and the DPA sets 10 business days' notice of changes. The list is dated 27 August 2025 and omits Stytch and Sentry, which the MCP docs and the CLI source name (12 of 20). The site readings are per the 9 October check, not re-read on 4 November. 15+18+6+12 = 51.

Score by category

CategoryWeightNodus ComputeThunder ComputeEdge
Reliability16%2565Thunder Compute +40
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8970Nodus Compute +19
Agent ergonomics13%8248Nodus Compute +34
Security & auth14%7351Nodus Compute +22
Payments & pricing10%3030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7079Thunder Compute +9
Transparency & trust7%5966Thunder Compute +7
Negative events≤150-5
TotalC 60.6/100D 52.5/100

Facts side by side

FactNodus ComputeThunder Compute
KindHTTP APIHTTP API
VendorNodus, Inc.Thunder Compute
Hosted endpointhttps://api-next.nodus-compute.ai/mcphttps://api.thundercompute.com:8443/v1
TransportsHTTP, Streamable HTTP, stdioHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPay per usePay per use
Price for gpu computenot published$0.219 per GB per month
x402nono
LicenceProprietary hosted service under the Nodus Terms of Service. The Python SDK repository is Apache-2.0Proprietary service under Thunder Compute's Terms and Conditions. The tnr CLI on GitHub is MIT
Tools exposed1728
Read-only variant documentedyesno
llms.txtnoyes
MCP registrynot listedio.github.Thunder-Compute/thunder-compute
Last release2026-11-162026-10-27
Terms last updated2026-07-282026-09-28
Privacy policy last updated2026-10-082026-09-28
Customer content may train modelsyes, with an opt-outnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textyes
Popularity2 stars34 stars

How the scores have moved

Verdicts

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.

Thunder Compute

The hosted MCP server signs in with OAuth and separate read and write scopes, and the REST API has a public OpenAPI 3.1 document. No rate limits, SLA or API changelog were found, instance creation has no idempotency key, and the CLI sends error reports to Sentry by default with no documented opt-out.

Before you call either

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

Thunder Compute

  1. Call GET /v2/status or the get_availability tool before creating an instance. Availability can change before launch, and creation fails when a type is sold out.
  2. List instances before retrying a failed create, because the call has no idempotency key.
  3. Pass public_key on create. If omitted, the response carries a generated private key that is returned once.
  4. To pause work, create a snapshot, delete the instance and later create a new instance from the snapshot. Snapshot storage keeps billing until deleted.
  5. For headless use set TNR_API_TOKEN to a token from the console, and upgrade the CLI to v2.1.0 or later, which stops copying that credential onto instances.

Questions

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

Nodus Compute scores 60.6 (C) on agent readiness against Thunder Compute's 52.5 (D), and leads in 3 of 7 scored categories. Thunder Compute leads on reliability, maintenance & community and transparency & trust.

Do Nodus Compute and Thunder Compute need an API key?

Both take an API key or an OAuth sign-in.

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

Yes. Nodus Compute has a hosted endpoint at https://api-next.nodus-compute.ai/mcp and Thunder Compute at https://api.thundercompute.com:8443/v1.

Other comparisons with Nodus Compute or Thunder 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.