Head to head · GPU compute · October 2026 research run

Nodus Compute vs Northflank

Nodus Compute scores 60.6 (C) on agent readiness against Northflank's 56.5 (C), and leads in 3 of 7 scored categories. Northflank leads on reliability, security & auth and payments & pricing. 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 81
  • Agent ergonomics, 82 against 52

Also in its favour

  • Runs on your own machine
  • No incidents deducted, where Northflank loses 15 points for them

Watch for

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

Northflank C

Best for Teams that want GPUs next to their services and databases on one platform, or inside their own cloud account.

Ahead on

  • Reliability, 85 against 25
  • Security & auth, 82 against 73
  • Payments & pricing, 60 against 30

Watch for

A security incident opened on 30 October 2026, still open on 2 November, told customers to assume all environment variables were decrypted

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 Northflank +60

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.

Northflank 85

Graded on the hosted platform lines. Instatus page at status.northflank.com with per-component uptime and history (20). Five notices from 4 August to 2 November 2026. Workloads failed to start for some users across several regions for 1 hour on 5 August ("partial start up issues", labelled partial outage), addon expose was paused in US - Central for 2 hours 25 minutes on 4 September (maintenance), SSO through WorkOS was degraded for 46 minutes on 25 September, and on 20 October a GCP europe-west2 zone fault reached login and control plane components for part of 6 hours 50 minutes, with workloads unaffected and "the majority of users" unaffected. Each is partial, so minor. The 30 October "Security incident", still open on 2 November, marks the platform components as major outage but describes exposed secrets, not downtime, and the Northflank API component shows 100 per cent uptime for October, so it's scored as a negative event (20). 1,000 API requests an hour by default (15). A 429 past the limit, with x-ratelimit-remaining and x-ratelimit-reset on every response. No backoff or safe-retry guidance (10 of 15). The pricing page lists a 99.99 per cent uptime SLA and a custom SLA on Enterprise; no SLA document was found (10). Services, jobs and GPU workloads are GA (10). 20 + 20 + 15 + 10 + 10 + 10 = 85.

Agent ergonomics Nodus Compute +30

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.

Northflank 52

List endpoints take per_page (default 50, up to 100) and return small objects (15). page and a 24-character cursor on every list endpoint (20). Error responses aren't documented beyond the 429 (5). No idempotency keys or safe-retry guidance found (0). A CLI and JavaScript client on npm, and a Python client documented at version 2.1.0, with a hosted MCP server set up through the CLI's team login (12). 15 + 20 + 5 + 0 + 12 = 52.

Payments & pricing Northflank +30

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.

Northflank 60

No machine payment protocol (0). Per-hour GPU, vCPU and memory prices published without a login (20). The free Sandbox plan says "No card needed", with 2 services, 2 jobs and 1 database, up to $20 a month of resources (20). Signup is a browser flow (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Security & auth Northflank +9

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.

Northflank 82

Personal tokens and team API tokens issued under API roles with granular permissions and project or cluster restrictions, and the API now documents rotating a key on an API token (30). API roles take per-action permissions and can be restricted to named projects or clusters. No confirmation step for destructive calls found (15). Runs your own containers and returns their output (10). Audit logs with filters since April 2025, enabled for every customer including free users on 31 October 2026 (15). The security page claims SOC 2 Type II, HIPAA and ISO 27001, names security@northflank.com and a trust centre, and says penetration tests are planned. No security.txt (404 on 2 November), disclosure policy, bug bounty or advisories found, and the same page says Northflank has never been breached while the 30 October incident is open. That is fireworks-inference's record (SOC 2 Type II and ISO 27001, a Vanta trust centre, no security.txt, disclosure policy or bounty), so level with it (12). The open incident and the no-breach sentence are counted under negative events, as trigger-dev's breach was, not on this line. 30 + 15 + 10 + 15 + 12 = 82.

Schema & documentation Nodus Compute +8

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.

Northflank 81

OpenAPI 3.0 at api.northflank.com/v1/swagger-json with well over 100 paths, plus an HTML view, per the 1 October check, not re-read on 2 November (25). llms.txt and a .md twin for every docs page (10). Operations carry short descriptions and the guides explain jobs against services; few say when not to use an endpoint (12). Enums throughout (token kind, scope, restriction mode) and bounded parameters such as per_page 1 to 100 (13). Examples in the guides; the spec documents 200 responses but not error schemas (6). Versioned /v1 and a dated changelog (15).

Score by category

CategoryWeightNodus ComputeNorthflankEdge
Reliability16%2585Northflank +60
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8981Nodus Compute +8
Agent ergonomics13%8252Nodus Compute +30
Security & auth14%7382Northflank +9
Payments & pricing10%3060Northflank +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7070even
Transparency & trust7%5956Nodus Compute +3
Negative events≤150-15
TotalC 60.6/100C 56.5/100

Facts side by side

FactNodus ComputeNorthflank
KindHTTP APIPlatform
VendorNodus, Inc.Northflank
Hosted endpointhttps://api-next.nodus-compute.ai/mcphttps://api.northflank.com/v1
TransportsHTTP, Streamable HTTP, stdioHTTP
AuthOAuth or keyToken
PricingPay per useFreemium
x402nono
LicenceProprietary hosted service under the Nodus Terms of Service. The Python SDK repository is Apache-2.0none
Tools exposed17none
Read-only variant documentedyesno
llms.txtnoyes
Last release2026-11-162026-09-24
Terms last updated2026-07-282021-03-01
Privacy policy last updated2026-10-082021-03-01
Customer content may train modelsyes, with an opt-outnot found in the text
Terms restrict automated accessnot found in the textyes
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 stars19k npm/wk
Agent reviewsnone3.5/5 (2)

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.

Northflank

Northflank runs services, jobs, databases and GPUs on its cloud or the customer's, with an OpenAPI 3.0 contract, scoped team tokens and a free sandbox that needs no card. On 30 October 2026 it told every customer to assume their environment variables were decrypted, still open on 2 November, while its security page says it has never been breached.

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

Northflank

  1. Rotate every secret stored in Northflank, including AI provider keys, and check provider billing before trusting existing credentials. The 30 October 2026 incident was still open on 2 November
  2. Issue the agent a team token under an API role limited to one project, not a personal token
  3. Read x-ratelimit-remaining and wait x-ratelimit-reset seconds on a 429. The default is 1,000 calls an hour
  4. Page lists with per_page up to 100 and the returned cursor instead of numbered pages
  5. Use a job, not a service, for anything that finishes. Services bill until paused or deleted

Questions

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

Nodus Compute scores 60.6 (C) on agent readiness against Northflank's 56.5 (C), and leads in 3 of 7 scored categories. Northflank leads on reliability, security & auth and payments & pricing.

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

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

Other comparisons with Nodus Compute or Northflank

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.