{
  "data": {
    "a": {
      "slug": "beam",
      "name": "Beam",
      "vendor": "Beam",
      "vendorUrl": "https://www.beam.cloud",
      "company": "beam.cloud",
      "kind": "platform",
      "category": "gpu-compute",
      "summary": "Beam runs persistent VMs, sandboxes, serverless GPU endpoints, task queues and functions for agents and Python code, billed by the millisecond (VMs by the second), on the open-source beta9 runtime.",
      "url": "https://www.anchorterminal.com/tools/beam",
      "markdownUrl": "https://www.anchorterminal.com/tools/beam.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/beam.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/beam.json",
      "dns": "beam.grade.anchorterminal.com",
      "repo": "https://github.com/beam-cloud/beta9",
      "license": "AGPL-3.0",
      "transports": [
        "http"
      ],
      "remoteUrl": "https://app.beam.cloud/api/v1",
      "packages": [
        {
          "registry": "pypi",
          "name": "beam-client"
        }
      ],
      "auth": "api-key",
      "authNotes": "API token from platform.beam.cloud, read from `BEAM_TOKEN` by the SDK and CLI or stored by `beam login` in `~/.beam/config.ini`, with named contexts for several workspaces. Deployed endpoints take the same token as `Authorization: Bearer`. The TypeScript SDK sets `beamOpts.token` server-side.",
      "pricing": "paid",
      "pricingNotes": "Developer plan $20 a month with $20 of monthly credits, Team $89 a month plus usage, Growth on request; no free plan. Serverless work is billed by the millisecond only while a container runs, which includes `on_start` and `keep_warm_seconds`; cold starts and image pulls aren't billed. Serverless GPUs are RTX 4090 24 GB $0.000192 a second ($0.69 an hour) and RTX 5090 32 GB $0.000303. On-demand machines from $0.44 an hour (RTX 4090), $1.36 (A100 80 GB), $1.83 (H100 PCIe), $2.09 (H200), $4.11 (B200), billed until released even when idle. CPU $0.0000125 a core-second and RAM $0.0000021 a GiB-second on CPU-only work, $0.000105 and $0.0000055 when attached to a GPU, $0.0000375 and $0.0000064 in sandboxes. VMs $0.0306 an hour for 1 vCPU and 1 GiB with a 50 GiB disk. Storage 1 TB included, then $0.021 a GB-month; no egress fees (https://www.beam.cloud/pricing, https://docs.beam.cloud/v2/resources/pricing-and-billing).",
      "priceSummary": "$0.045 / vCPU-hr",
      "where": "hosted",
      "x402": {
        "level": "no",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": 1800,
        "npmWeekly": null,
        "pypiWeekly": 8481,
        "asOf": "2026-09-30"
      },
      "docsUrl": "https://docs.beam.cloud",
      "llmsTxt": "https://docs.beam.cloud/llms.txt",
      "capabilities": [
        "compute.gpu",
        "compute.serverless",
        "compute.endpoints",
        "compute.batch",
        "compute.containers"
      ],
      "tags": [
        "hosted",
        "open-source",
        "self-hosted",
        "python",
        "typescript",
        "llms-txt",
        "async-jobs"
      ],
      "lastRelease": "2026-10-16",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 57.4,
        "grade": "C",
        "agentReady": false,
        "rank": 888,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 13,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 58,
          "maintenance": 85,
          "payments": 30,
          "reliability": 55,
          "schema": 58,
          "security": 65,
          "transparency": 80
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-04"
        },
        "negative": -2,
        "negativeNotes": [
          "-2: `beam deploy --format json` writes the full workspace bearer token into the JSON logs array that CI systems keep. Filed by a Beam engineer on 2026-08-04 and still open on 2026-10-01 (https://github.com/beam-cloud/beta9/issues/1828)"
        ],
        "verdict": "Per-millisecond billing for serverless GPUs and sandboxes and per-second billing for VMs, with cold starts and image pulls free and the beta9 engine self-hostable under AGPL-3.0. The remote MCP server signs in by OAuth with scopes and a read-only mode. There is no free plan, request rate limit, 429 guidance or SLA.",
        "bestFor": "Python teams and agents running bursty GPU functions, sandboxes or persistent dev VMs on consumer or PCIe cards, with the option to self-host the same runtime.",
        "strengths": [
          "Per-millisecond billing with cold starts and image pulls free, RTX 4090 at $0.69 an hour serverless",
          "beta9, the engine the hosted cloud runs on, is AGPL-3.0 and self-hostable",
          "Remote MCP server with OAuth scopes, a read-only mode and confirmation for destructive operations",
          "Workspace REST API, Python and TypeScript SDKs on the same token",
          "Privacy policy with retention periods per category and a published subprocessor list"
        ],
        "weaknesses": [
          "No free plan; the Developer plan costs $20 a month, with $20 of credits",
          "No published request rate limits, 429 handling or SLA",
          "Workspace API tokens have no scopes or read-only mode, and every member has the same permissions",
          "The changelog stops in June 2025 and there are no deprecation notices",
          "`beam deploy --format json` was reported on 1 October as leaking the workspace token into its logs, with no fix found"
        ],
        "agentNotes": [
          "Check the response body for `ok: false` on gateway calls; a failure can arrive as HTTP 200",
          "Connect MCP clients with OAuth and add `?readonly=true` for agents that only need to read",
          "Route anything over 180 seconds to a task queue and poll the task instead of holding the endpoint request",
          "Set `keep_warm_seconds` deliberately; the 180-second endpoint default bills three minutes of GPU after every call",
          "Keep `beam deploy` JSON output out of CI logs until the token-in-logs report is closed"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 2,
        "avgRating": 3,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "C",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 57.4
          }
        ],
        "editorialScores": {
          "ergonomics": 58,
          "maintenance": 85,
          "payments": 30,
          "reliability": 55,
          "schema": 58,
          "security": 65,
          "transparency": 71
        },
        "provenanceScore": 88,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-04",
            "maintenance": "2026-11-04",
            "payments": "2026-11-04",
            "reliability": "2026-11-04",
            "schema": "2026-11-04",
            "security": "2026-11-04",
            "transparency": "2026-11-04"
          },
          "last": "2026-11-04",
          "lastMoved": "2026-11-13",
          "oldest": "2026-11-04",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "install": "pip install beam-client \u0026\u0026 beam login",
        "http": "curl -X POST \"https://my-function-$BEAM_DEPLOYMENT_ID-v1.app.beam.cloud\" \\\n  -H \"Authorization: Bearer $BEAM_TOKEN\" -H \"Content-Type: application/json\" \\\n  -d '{\"x\":10}'"
      },
      "letme": {
        "capability": "https://letme.dev/compute.gpu",
        "tool": "https://letme.dev/beam"
      },
      "area": "models",
      "unitPrices": [
        {
          "item": "RTX 5090 32 GB serverless",
          "unit": "gpu-hour",
          "usd": 1.09,
          "note": "$0.000303 a second"
        },
        {
          "item": "RTX 4090 24 GB serverless",
          "unit": "gpu-hour",
          "usd": 0.69,
          "note": "$0.000192 a second"
        },
        {
          "item": "B200 180 GB reserved machine",
          "unit": "gpu-hour",
          "usd": 4.11,
          "note": "From price, billed while reserved"
        },
        {
          "item": "H200 141 GB reserved machine",
          "unit": "gpu-hour",
          "usd": 2.09,
          "note": "From price, billed while reserved"
        },
        {
          "item": "A100 80 GB reserved machine",
          "unit": "gpu-hour",
          "usd": 1.36,
          "note": "From price, billed while reserved"
        },
        {
          "item": "CPU-only compute",
          "unit": "vcpu-hour",
          "usd": 0.045,
          "note": "$0.0000125 a core-second, RAM extra at $0.0000021 a GiB-second"
        },
        {
          "item": "Team plan",
          "unit": "month",
          "usd": 89,
          "note": "Plus usage"
        },
        {
          "item": "Developer plan",
          "unit": "month",
          "usd": 20,
          "note": "Includes $20 of credits a month"
        }
      ],
      "provenance": {
        "legalEntity": "Smartshare, Inc.",
        "domain": "beam.cloud",
        "domainRegistered": "2019-07-31",
        "endpointOnVendorDomain": true,
        "terms": "https://docs.beam.cloud/v2/security/terms-and-conditions",
        "privacy": "https://docs.beam.cloud/v2/security/privacy-policy",
        "statusPage": "https://status.beam.cloud",
        "changelog": "https://docs.beam.cloud/v2/releases",
        "securityTxt": "none",
        "checked": "2026-11-04",
        "notes": [
          "Terms dated 14 September 2026 name Smartshare, Inc., a Delaware corporation doing business as Beam. The site footer reads © 2026 Smartshare, Inc.",
          "Deployed endpoints run on app.beam.cloud, a subdomain of the vendor domain. There's no public REST base URL for deploying.",
          "www.beam.cloud/.well-known/security.txt and www.beam.cloud/terms return 404; the legal pages live under docs.beam.cloud.",
          "A changelog at docs.beam.cloud/v2/releases is linked from the site footer, but its newest entry is 2 June 2025; releases since show up as tags and commits in the beam-client and beta9 repositories."
        ],
        "score": 88
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/beam.json",
      "live": {
        "slug": "beam",
        "probe": {
          "target": "https://app.beam.cloud/api/v1",
          "method": "get",
          "lastAt": "2026-11-18T23:01:19.437413204Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 297,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 265,
          "p95ms24h": 395,
          "samples24h": 241,
          "samples30d": 7840,
          "days": [
            {
              "date": "2026-10-18",
              "probes": 256,
              "ok": 256
            },
            {
              "date": "2026-10-19",
              "probes": 255,
              "ok": 255
            },
            {
              "date": "2026-10-20",
              "probes": 252,
              "ok": 252
            },
            {
              "date": "2026-10-21",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-22",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-23",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-10-24",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-10-25",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-10-26",
              "probes": 252,
              "ok": 252
            },
            {
              "date": "2026-10-27",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-28",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-10-29",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-30",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-10-31",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-11-01",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-11-02",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-11-03",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-11-04",
              "probes": 246,
              "ok": 246
            },
            {
              "date": "2026-11-05",
              "probes": 185,
              "ok": 185
            },
            {
              "date": "2026-11-06",
              "probes": 241,
              "ok": 241
            },
            {
              "date": "2026-11-07",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-08",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-09",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-10",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-11",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-12",
              "probes": 245,
              "ok": 245
            },
            {
              "date": "2026-11-13",
              "probes": 238,
              "ok": 238
            },
            {
              "date": "2026-11-14",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-15",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-16",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-17",
              "probes": 242,
              "ok": 242
            },
            {
              "date": "2026-11-18",
              "probes": 231,
              "ok": 231
            }
          ],
          "since": "2026-10-08T00:00:00Z"
        },
        "vendorStatus": {
          "page": "https://status.beam.cloud",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-11-18T22:59:51.558058999Z"
        },
        "versions": [
          {
            "registry": "github",
            "name": "beam-cloud/beta9",
            "version": "gateway-0.1.860",
            "released": "2026-11-18",
            "seenAt": "2026-11-18T17:32:03.24845961Z"
          },
          {
            "registry": "pypi",
            "name": "beam-client",
            "version": "0.2.241",
            "released": "2026-11-18",
            "seenAt": "2026-11-18T17:32:03.130369269Z"
          }
        ],
        "githubStars": 1855,
        "pypiWeekly": 18386,
        "securityTxt": {
          "url": "https://beam.cloud/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-18T16:31:08.223083597Z"
        },
        "llmsTxt": {
          "url": "https://docs.beam.cloud/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-18T16:13:31.230724914Z"
        },
        "domain": {
          "domain": "beam.cloud",
          "registered": "2019-07-31",
          "source": "https://rdap.registry.cloud/rdap/domain/beam.cloud",
          "checkedAt": "2026-11-15T15:17:02.913977505Z"
        },
        "pages": [
          {
            "url": "https://docs.beam.cloud/v2/releases",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-11-18T21:39:04.726493878Z",
            "changedAt": "2026-11-18T21:39:04.726493878Z",
            "fingerprint": "f906584be1bf"
          },
          {
            "url": "https://docs.beam.cloud/v2/resources/pricing-and-billing",
            "kind": "pricing",
            "status": 200,
            "checkedAt": "2026-11-18T21:39:07.146850171Z",
            "changedAt": "2026-11-18T21:39:07.146850171Z",
            "fingerprint": "a64f2dd42868"
          },
          {
            "url": "https://www.beam.cloud/pricing",
            "kind": "pricing",
            "status": 304,
            "checkedAt": "2026-11-18T21:59:51.528546391Z",
            "changedAt": "2026-11-17T21:19:04.485737072Z",
            "fingerprint": "1faef72f5ada"
          },
          {
            "url": "https://docs.beam.cloud/v2/security/privacy-policy",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-11-18T21:39:08.985375187Z",
            "changedAt": "2026-11-18T21:39:08.985375187Z",
            "fingerprint": "95f53be5f3ab"
          },
          {
            "url": "https://docs.beam.cloud/v2/security/terms-and-conditions",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-11-18T21:39:11.012100622Z",
            "changedAt": "2026-11-18T21:39:11.012100622Z",
            "fingerprint": "65c7576fd83c"
          }
        ],
        "github": {
          "repo": "beam-cloud/beta9",
          "checkedAt": "2026-11-16T11:46:54.69544413Z",
          "stars": 1852,
          "archived": false,
          "issuesEnabled": true,
          "pushedAt": "2026-11-16T04:46:07Z",
          "openIssues": 11,
          "openPRs": 42,
          "issuesOpened90d": 7,
          "issuesClosed90d": 4,
          "prsMerged90d": 219,
          "ci": {
            "branch": "main",
            "runs": 50,
            "success": 47,
            "failure": 3,
            "other": 0,
            "latest": "success",
            "latestAt": "2026-11-12T18:15:21Z"
          },
          "replies": {
            "sampled": 25,
            "unanswered": 9,
            "medianDays": 9.2
          }
        },
        "updatedAt": "2026-11-18T23:01:19.437413204Z"
      },
      "streak": {
        "days": 41,
        "from": "2026-10-08",
        "sinceWatching": true,
        "best": 41
      }
    },
    "answer": "Nodus Compute scores 60.6 (C) on agent readiness against Beam's 57.4 (C), and leads in 3 of 7 scored categories. Beam leads on reliability, maintenance \u0026 community and transparency \u0026 trust.",
    "b": {
      "slug": "nodus-compute",
      "name": "Nodus Compute",
      "vendor": "Nodus, Inc.",
      "vendorUrl": "https://www.nodus-compute.ai",
      "company": "nodus-compute.ai",
      "kind": "http-api",
      "category": "gpu-compute",
      "summary": "Nodus Compute runs training, fine-tuning, inference endpoints, agent sandboxes and batch jobs on rented GPUs or on the customer's own machines, through a Kubernetes-style HTTP API, a Python SDK and CLI, and a hosted MCP server.",
      "url": "https://www.anchorterminal.com/tools/nodus-compute",
      "markdownUrl": "https://www.anchorterminal.com/tools/nodus-compute.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/nodus-compute.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/nodus-compute.json",
      "dns": "nodus-compute.grade.anchorterminal.com",
      "repo": "https://github.com/nodus-compute/Nodus-sdk-python",
      "license": "Proprietary hosted service under the Nodus Terms of Service. The Python SDK repository is Apache-2.0",
      "transports": [
        "http",
        "streamable-http",
        "stdio"
      ],
      "remoteUrl": "https://api-next.nodus-compute.ai/mcp",
      "packages": [
        {
          "registry": "pypi",
          "name": "nodus-compute"
        }
      ],
      "auth": "mixed",
      "authNotes": "API keys (`nodus_sk_live_`) sent as `Authorization: Bearer` or `NODUS_API_KEY`, created in the console or with `nodus create apikey`. Each key has Standard, Inference only, Read only or custom scopes, optional project limits and an optional expiry, and is stored as a keyed hash. The hosted MCP server uses OAuth, with a consent page that picks the organisation and scopes. Grants can be narrowed or deleted, taking effect within 30 seconds. A new organisation needs a verified email and card.",
      "pricing": "usage",
      "pricingNotes": "Hourly prices are published per GPU and CPU configuration, such as $2.600 for an H100 SXM, $1.090 for an A100 80 GB, $0.290 for an RTX 4090 and $0.0075 for 1 vCPU with 1 GiB. Usage draws on prepaid credits, with auto-recharge, budgets and spending caps. A new organisation needs a verified card, though verification buys no credits. Reserved GPUs and clusters are quoted on request.",
      "priceSummary": "$0.0075 / vCPU-hr",
      "where": "both",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the docs index, the MCP guide, the pricing page or the error reference (checked 2026-11-18). Applying a TopUp through MCP returns a checkout link for the person to open.",
        "endpoints": []
      },
      "toolCount": 17,
      "popularity": {
        "githubStars": 2,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-18"
      },
      "docsUrl": "https://www.nodus-compute.ai/docs/",
      "openapi": "https://github.com/nodus-compute/Nodus-sdk-python/blob/main/openapi/openapi.yaml",
      "capabilities": [
        "compute.gpu",
        "compute.batch",
        "compute.endpoints",
        "compute.containers",
        "sandbox.code"
      ],
      "tags": [
        "hosted",
        "usage",
        "gpu",
        "mcp",
        "remote-mcp",
        "oauth",
        "api-key",
        "openapi",
        "python",
        "cli",
        "webhooks",
        "sandbox",
        "yc"
      ],
      "lastRelease": "2026-11-16",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 60.6,
        "grade": "C",
        "agentReady": false,
        "rank": 763,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 10,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 82,
          "maintenance": 70,
          "payments": 30,
          "reliability": 25,
          "schema": 89,
          "security": 73,
          "transparency": 59
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-18"
        },
        "negative": 0,
        "warnings": [
          {
            "kind": "operator-unidentified",
            "name": "Operator not identified",
            "text": "Nodus' pages name Nodus, Inc. under Delaware law, with \"San Francisco \u0026 New York\" and no place of registration, registration number or address. OpenCorporates refused our reader (403) and Delaware's entity search is a form it can't submit, so no register entry was found.",
            "deduct": 0,
            "capGrade": "B",
            "since": "2026-11-18",
            "sources": [
              "https://www.nodus-compute.ai/terms/",
              "https://www.nodus-compute.ai/privacy/"
            ]
          }
        ],
        "verdict": "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.",
        "bestFor": "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.",
        "strengths": [
          "Hosted MCP server with OAuth scopes chosen at sign-in, and tool lists filtered to those scopes",
          "`apply` creates nothing until a second call confirms the same estimate and etag",
          "An error reference with one page per reason, giving the HTTP status, whether to retry and what to do",
          "API keys with read-only, inference-only or custom scopes, project limits and optional expiry",
          "Hourly GPU and CPU prices published without a login, from $0.0075 for 1 vCPU to $6.943 for a B300"
        ],
        "weaknesses": [
          "The security page describes a pilot with no SOC 2, ISO certification or penetration test, and no private networking",
          "No status page or SLA found",
          "A new organisation needs a verified card, so there is no card-free start",
          "The public SDK repository was last changed on 1 October 2026 at 0.11.0, while PyPI has 1.0.92",
          "`delete`, `exec` and other write tools skip the estimate and confirmation step"
        ],
        "agentNotes": [
          "Call `estimate` or a first `apply`, show the person the cost, then call `apply` with `confirmed: true` and the same etag",
          "Check the connection with `whoami` and 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 the `Retry-After` interval before retrying",
          "Ask for the narrowest scopes the task needs. A client granted only `jobs:read` sees only read tools"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "C",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 60.6
          }
        ],
        "editorialScores": {
          "ergonomics": 82,
          "maintenance": 70,
          "payments": 30,
          "reliability": 25,
          "schema": 89,
          "security": 73,
          "transparency": 53
        },
        "provenanceScore": 65,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-18",
            "maintenance": "2026-11-18",
            "payments": "2026-11-18",
            "reliability": "2026-11-18",
            "schema": "2026-11-18",
            "security": "2026-11-18",
            "transparency": "2026-11-18"
          },
          "last": "2026-11-18",
          "oldest": "2026-11-18",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "install": "pip install nodus-compute",
        "claudeCode": "claude mcp add --transport http nodus https://api-next.nodus-compute.ai/mcp",
        "config": {
          "mcpServers": {
            "nodus": {
              "type": "http",
              "url": "https://api-next.nodus-compute.ai/mcp"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/compute.gpu",
        "tool": "https://letme.dev/nodus-compute"
      },
      "area": "models",
      "unitPrices": [
        {
          "item": "H100 SXM 80 GB",
          "unit": "gpu-hour",
          "usd": 2.6
        },
        {
          "item": "A100 80 GB",
          "unit": "gpu-hour",
          "usd": 1.09
        },
        {
          "item": "RTX 4090",
          "unit": "gpu-hour",
          "usd": 0.29
        },
        {
          "item": "B300",
          "unit": "gpu-hour",
          "usd": 6.943
        },
        {
          "item": "CPU, 1 vCPU and 1 GiB",
          "unit": "vcpu-hour",
          "usd": 0.0075
        }
      ],
      "provenance": {
        "legalEntity": "Nodus, Inc.",
        "domain": "nodus-compute.ai",
        "domainRegistered": "",
        "endpointOnVendorDomain": true,
        "terms": "https://www.nodus-compute.ai/terms/",
        "privacy": "https://www.nodus-compute.ai/privacy/",
        "statusPage": "",
        "changelog": "https://www.nodus-compute.ai/changelog/",
        "securityTxt": "none",
        "checked": "2026-11-18",
        "notes": [
          "The terms (effective 28 July 2026) name Nodus, Inc. with San Francisco and New York and choose Delaware law. No place of incorporation, registration number or street address was found on any page read.",
          "The privacy policy is effective 8 October 2026.",
          "www.nodus-compute.ai robots.txt allowed every page read on 18 November 2026.",
          "No status page is linked from the site or the docs. The security page gives a disclosure policy with response times. /.well-known/security.txt returned 404.",
          "The domain's registration date wasn't looked up."
        ],
        "score": 65
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/nodus-compute.json",
      "live": {
        "slug": "nodus-compute",
        "probe": {
          "target": "https://api-next.nodus-compute.ai/mcp",
          "method": "get",
          "lastAt": "2026-11-18T23:01:43.19041236Z",
          "lastOk": true,
          "lastStatus": 401,
          "lastMs": 314,
          "lastNote": "asks for credentials",
          "authRequired": true,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 362,
          "p95ms24h": 1308,
          "samples24h": 14,
          "samples30d": 14,
          "days": [
            {
              "date": "2026-11-18",
              "probes": 14,
              "ok": 14
            }
          ],
          "since": "2026-11-18T21:38:16.078618535Z"
        },
        "updatedAt": "2026-11-18T23:01:43.19041236Z"
      },
      "streak": {
        "days": 0,
        "from": "2026-11-18",
        "sinceWatching": true,
        "best": 0
      }
    },
    "edges": [
      {
        "by": 31,
        "category": "schema",
        "leads": "nodus-compute",
        "name": "Schema \u0026 documentation",
        "reasons": {
          "a": "Two Swagger files generated from protobuf (gateway and pods) still sit under the API reference and in llms.txt, with typed bodies and a shared error schema but almost no operation summaries; the workspace REST API at app.beam.cloud/api/v1 is a route table with no spec (15 of 25). llms.txt with .md pages (10). The guides say when to use what (endpoints for work under 180 seconds, task queues beyond), the generated specs don't (10). Typed request bodies with required fields and some enums, and a typed Python SDK (10). Plenty of examples; errors are an `rpcStatus` object, and the gateway can return HTTP 200 with `ok: false`, which the REST page now states (8). Versioned SDK releases, and a changelog linked from the site footer whose newest entry is 2 June 2025, 17 months old (5). 15 + 10 + 10 + 10 + 8 + 5 = 58.",
          "b": "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."
        },
        "scores": {
          "a": 58,
          "b": 89
        }
      },
      {
        "by": 30,
        "category": "reliability",
        "leads": "beam",
        "name": "Reliability",
        "reasons": {
          "a": "Atlassian Statuspage at status.beam.cloud with API, Dashboard and Platform components plus Stripe and AWS dependencies, and history (20). Its feed, read on 4 November 2026, has no incident since 17 June 2025, but four GitHub issues opened between 25 August and 1 September 2026 reported account creation and login failing, and none reached the status page, so the record is scored as minor incidents rather than clean (20, per the 1 October reading of the issues, not re-read). No request rate limits found; the plans publish concurrency caps of 30 vCPUs and 5 GPUs on Developer and 1,000 vCPUs and 50 GPUs on Team, with unlimited API requests (5 of 15). No 429 or backoff guidance found; the retries guide asks for task code safe to run more than once, which is about Beam's own task retries, not client retries (0). No SLA; the terms say any uptime commitment applies only if set out in an Order Form (0). Endpoints, task queues, sandboxes and VMs are GA (10). 20 + 20 + 5 + 0 + 0 + 10 = 55.",
          "b": "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."
        },
        "scores": {
          "a": 55,
          "b": 25
        }
      },
      {
        "by": 24,
        "category": "ergonomics",
        "leads": "nodus-compute",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "List endpoints for deployments and tasks take filters and a limit; objects are small (15). Filtering and limits documented, cursor behaviour isn't ('List responses may be paginated') (15). HTTP statuses on the workspace API, but the gateway's 200-with-`ok: false` means an agent has to read the body to spot a failure (8). No idempotency keys; functions and task queues retry 3 times by default, up to 5, with `retry_for` on task queues (5). Defaults are sensible (`keep_warm_seconds` 180 for endpoints, 10 for queues) and there are Python and TypeScript SDKs plus an official MCP server (15). 15 + 15 + 8 + 5 + 15 = 58.",
          "b": "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."
        },
        "scores": {
          "a": 58,
          "b": 82
        }
      },
      {
        "by": 21,
        "category": "transparency",
        "leads": "beam",
        "name": "Transparency \u0026 trust",
        "reasons": {
          "a": "beta9, the engine the hosted Beam runs on, is AGPL-3.0 and self-hostable; the hosted extras and terms are closed (25). Privacy policy dated 14 September 2026 gives retention per category (account data 90 days after deletion, application logs 30 days or 1 year on Growth, platform logs 90 days, analytics 14 months, PostHog recordings 30 days) and the security page agrees (30 days to retrieve data after termination), with a DPA (26). No deprecation policy or dated notices found; the terms promise 30 days' notice of material changes to the terms, not to the API, and the changelog stops in June 2025 (0). Subprocessor list published (AWS, Google Cloud, Stripe, Sentry, PostHog and others) and data stays in the US unless a region or pool is chosen; PostHog session replay is disclosed (20). 25 + 26 + 0 + 20 = 71.",
          "b": "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."
        },
        "scores": {
          "a": 80,
          "b": 59
        }
      },
      {
        "by": 15,
        "category": "maintenance",
        "leads": "beam",
        "name": "Maintenance \u0026 community",
        "reasons": {
          "a": "Newest dated release is the TypeScript SDK tag js/v1.1.6 on 16 October 2026, with beam-client's Python version bumped to 0.2.233 the same day in beam-cloud/beam-client (30). Tags in the 90 days from 6 August are js/v1.0.20 (15 September), cli-0.2.212 (29 September), js/v1.1.5 and js/v1.1.6 (16 October), four (20). Python versions aren't tagged and PyPI couldn't be read, so they aren't counted on their own. Responsiveness per the 1 October check, not re-read, where the sign-up reports got a staff reply but the token-in-logs issue had sat open for two months (15). Python and TypeScript SDKs are current (15). Both repositories run CI with tests on every push, results unread, and the client still declares Python 3.8, which is past end of life (5). 30 + 20 + 15 + 15 + 5 = 85.",
          "b": "`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."
        },
        "scores": {
          "a": 85,
          "b": 70
        }
      },
      {
        "by": 8,
        "category": "security",
        "leads": "nodus-compute",
        "name": "Security \u0026 auth",
        "reasons": {
          "a": "Credential model 25 of 30. Workspace API tokens can be created, rotated and revoked but carry no scopes (20), while the remote MCP server now signs in by OAuth with named scopes (`beam:read`, `beam:credentials`), refreshes tokens and lists connected clients for disconnection (30); between the two. Least privilege 10 of 20. The MCP server takes `?readonly=true` and says deletions and other destructive operations require confirmation, but REST tokens and the SDK have no read-only mode, and all workspace members have the same permissions. Runs your own code and returns its output, no third-party content (10). Task, log and event history per deployment in the dashboard and API; Beam's own staff access logs are internal (10 of 15). Programme 10. A disclosure policy on the security overview and in beta9's SECURITY.md (acknowledgement within 3 business days, safe harbour) and SOC 2 Type II by Advantage Partners with the report under NDA; no bug bounty and no security.txt (404). OSV lists one advisory for beta9, CVE-2025-69820 (Moderate 6.0, path traversal in joinCleanPath, a researcher's record published 22 January 2026). beta9 replaced joinCleanPath on 16 October 2026 in d76ba79 (gateway-0.1.820), a commit that names the CVE, so it is a fixed third-party Moderate and costs nothing. The token-in-logs report of 4 August 2026 is per the 1 October check, not re-read (GitHub pages answer 403). 25 + 10 + 10 + 10 + 10 = 65.",
          "b": "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."
        },
        "scores": {
          "a": 65,
          "b": 73
        }
      }
    ],
    "facts": [
      {
        "a": "Platform",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Beam",
        "b": "Nodus, Inc.",
        "name": "Vendor"
      },
      {
        "a": "https://app.beam.cloud/api/v1",
        "b": "https://api-next.nodus-compute.ai/mcp",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP",
        "b": "HTTP, Streamable HTTP, stdio",
        "name": "Transports"
      },
      {
        "a": "API key",
        "b": "OAuth or key",
        "name": "Auth"
      },
      {
        "a": "Paid",
        "b": "Pay per use",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "AGPL-3.0",
        "b": "Proprietary hosted service under the Nodus Terms of Service. The Python SDK repository is Apache-2.0",
        "name": "Licence"
      },
      {
        "a": "none",
        "b": "17",
        "name": "Tools exposed"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "no",
        "name": "llms.txt"
      },
      {
        "a": "2026-10-16",
        "b": "2026-11-16",
        "name": "Last release"
      },
      {
        "a": "2026-09-14",
        "b": "2026-07-28",
        "name": "Terms last updated"
      },
      {
        "a": "2026-09-14",
        "b": "2026-10-08",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not found in the text",
        "b": "yes, with an opt-out",
        "name": "Customer content may train models"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "1.8k stars, 8.5k PyPI/wk",
        "b": "2 stars",
        "name": "Popularity"
      },
      {
        "a": "3/5 (2)",
        "b": "none",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "Nodus Compute scores 60.6 (C) on agent readiness against Beam's 57.4 (C), and leads in 3 of 7 scored categories. Beam leads on reliability, maintenance \u0026 community and transparency \u0026 trust.",
        "question": "Which is better for AI agents, Beam or Nodus Compute?"
      },
      {
        "answer": "Yes. Beam has a hosted endpoint at https://app.beam.cloud/api/v1 and Nodus Compute at https://api-next.nodus-compute.ai/mcp.",
        "question": "Can an agent call Beam and Nodus Compute without installing anything?"
      },
      {
        "answer": "Beam is open source (AGPL-3.0). No open-source release is listed for Nodus Compute.",
        "question": "Are Beam and Nodus Compute open source?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 55 against 25",
          "Maintenance \u0026 community, 85 against 70",
          "Transparency \u0026 trust, 80 against 59"
        ],
        "also": [
          "Open source"
        ],
        "goodFor": "Python teams and agents running bursty GPU functions, sandboxes or persistent dev VMs on consumer or PCIe cards, with the option to self-host the same runtime.",
        "slug": "beam",
        "watchFor": "No free plan; the Developer plan costs $20 a month, with $20 of credits"
      },
      {
        "aheadOn": [
          "Schema \u0026 documentation, 89 against 58",
          "Agent ergonomics, 82 against 58",
          "Security \u0026 auth, 73 against 65"
        ],
        "also": [
          "Runs on your own machine"
        ],
        "goodFor": "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.",
        "slug": "nodus-compute",
        "watchFor": "The security page describes a pilot with no SOC 2, ISO certification or penetration test, and no private networking"
      }
    ],
    "history": {
      "beam": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 1.2,
          "from": 56.2,
          "fromGrade": "C",
          "to": 57.4,
          "toGrade": "C"
        },
        {
          "causes": [
            "pricing",
            "product",
            "evidence"
          ],
          "date": "2026-11-04",
          "delta": 0.6,
          "from": 55.6,
          "fromGrade": "C",
          "to": 56.2,
          "toGrade": "C"
        },
        {
          "causes": [
            "method"
          ],
          "date": "2026-10-27",
          "delta": 0.1,
          "from": 55.5,
          "fromGrade": "C",
          "to": 55.6,
          "toGrade": "C"
        }
      ],
      "nodus-compute": null
    },
    "job": {
      "capability": "compute.gpu",
      "name": "GPU compute"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/baseten-vs-beam.json",
        "title": "Baseten vs Beam",
        "url": "https://www.anchorterminal.com/compare/baseten-vs-beam"
      },
      {
        "json": "https://www.anchorterminal.com/compare/baseten-vs-nodus-compute.json",
        "title": "Baseten vs Nodus Compute",
        "url": "https://www.anchorterminal.com/compare/baseten-vs-nodus-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beam-vs-cerebrium.json",
        "title": "Beam vs Cerebrium",
        "url": "https://www.anchorterminal.com/compare/beam-vs-cerebrium"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beam-vs-cloud-run-gpus.json",
        "title": "Beam vs Cloud Run GPUs",
        "url": "https://www.anchorterminal.com/compare/beam-vs-cloud-run-gpus"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beam-vs-coreweave.json",
        "title": "Beam vs CoreWeave",
        "url": "https://www.anchorterminal.com/compare/beam-vs-coreweave"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beam-vs-crusoe-cloud.json",
        "title": "Beam vs Crusoe Cloud",
        "url": "https://www.anchorterminal.com/compare/beam-vs-crusoe-cloud"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beam-vs-gpusmarket.json",
        "title": "Beam vs GPUsMarket",
        "url": "https://www.anchorterminal.com/compare/beam-vs-gpusmarket"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beam-vs-hugging-face-inference-endpoints.json",
        "title": "Beam vs Hugging Face Inference Endpoints",
        "url": "https://www.anchorterminal.com/compare/beam-vs-hugging-face-inference-endpoints"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beam-vs-hyperbolic.json",
        "title": "Beam vs Hyperbolic",
        "url": "https://www.anchorterminal.com/compare/beam-vs-hyperbolic"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beam-vs-koyeb.json",
        "title": "Beam vs Koyeb",
        "url": "https://www.anchorterminal.com/compare/beam-vs-koyeb"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beam-vs-lambda.json",
        "title": "Beam vs Lambda Cloud",
        "url": "https://www.anchorterminal.com/compare/beam-vs-lambda"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beam-vs-massed-compute.json",
        "title": "Beam vs Massed Compute",
        "url": "https://www.anchorterminal.com/compare/beam-vs-massed-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beam-vs-modal.json",
        "title": "Beam vs Modal",
        "url": "https://www.anchorterminal.com/compare/beam-vs-modal"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beam-vs-nebius-ai-cloud.json",
        "title": "Beam vs Nebius AI Cloud",
        "url": "https://www.anchorterminal.com/compare/beam-vs-nebius-ai-cloud"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beam-vs-northflank.json",
        "title": "Beam vs Northflank",
        "url": "https://www.anchorterminal.com/compare/beam-vs-northflank"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beam-vs-replicate-deploy.json",
        "title": "Beam vs Replicate Deployments",
        "url": "https://www.anchorterminal.com/compare/beam-vs-replicate-deploy"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beam-vs-runpod.json",
        "title": "Beam vs Runpod",
        "url": "https://www.anchorterminal.com/compare/beam-vs-runpod"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beam-vs-thunder-compute.json",
        "title": "Beam vs Thunder Compute",
        "url": "https://www.anchorterminal.com/compare/beam-vs-thunder-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beam-vs-together-gpu-clusters.json",
        "title": "Beam vs Together GPU Clusters",
        "url": "https://www.anchorterminal.com/compare/beam-vs-together-gpu-clusters"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beam-vs-vast-ai.json",
        "title": "Beam vs Vast.ai",
        "url": "https://www.anchorterminal.com/compare/beam-vs-vast-ai"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beam-vs-verda.json",
        "title": "Beam vs Verda",
        "url": "https://www.anchorterminal.com/compare/beam-vs-verda"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cerebrium-vs-nodus-compute.json",
        "title": "Cerebrium vs Nodus Compute",
        "url": "https://www.anchorterminal.com/compare/cerebrium-vs-nodus-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-nodus-compute.json",
        "title": "Cloud Run GPUs vs Nodus Compute",
        "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-nodus-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/coreweave-vs-nodus-compute.json",
        "title": "CoreWeave vs Nodus Compute",
        "url": "https://www.anchorterminal.com/compare/coreweave-vs-nodus-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-nodus-compute.json",
        "title": "Crusoe Cloud vs Nodus Compute",
        "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-nodus-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/gpusmarket-vs-nodus-compute.json",
        "title": "GPUsMarket vs Nodus Compute",
        "url": "https://www.anchorterminal.com/compare/gpusmarket-vs-nodus-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-nodus-compute.json",
        "title": "Hugging Face Inference Endpoints vs Nodus Compute",
        "url": "https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-nodus-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperbolic-vs-nodus-compute.json",
        "title": "Hyperbolic vs Nodus Compute",
        "url": "https://www.anchorterminal.com/compare/hyperbolic-vs-nodus-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/koyeb-vs-nodus-compute.json",
        "title": "Koyeb vs Nodus Compute",
        "url": "https://www.anchorterminal.com/compare/koyeb-vs-nodus-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/lambda-vs-nodus-compute.json",
        "title": "Lambda Cloud vs Nodus Compute",
        "url": "https://www.anchorterminal.com/compare/lambda-vs-nodus-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/massed-compute-vs-nodus-compute.json",
        "title": "Massed Compute vs Nodus Compute",
        "url": "https://www.anchorterminal.com/compare/massed-compute-vs-nodus-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/modal-vs-nodus-compute.json",
        "title": "Modal vs Nodus Compute",
        "url": "https://www.anchorterminal.com/compare/modal-vs-nodus-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-nodus-compute.json",
        "title": "Nebius AI Cloud vs Nodus Compute",
        "url": "https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-nodus-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/nodus-compute-vs-northflank.json",
        "title": "Nodus Compute vs Northflank",
        "url": "https://www.anchorterminal.com/compare/nodus-compute-vs-northflank"
      },
      {
        "json": "https://www.anchorterminal.com/compare/nodus-compute-vs-replicate-deploy.json",
        "title": "Nodus Compute vs Replicate Deployments",
        "url": "https://www.anchorterminal.com/compare/nodus-compute-vs-replicate-deploy"
      },
      {
        "json": "https://www.anchorterminal.com/compare/nodus-compute-vs-runpod.json",
        "title": "Nodus Compute vs Runpod",
        "url": "https://www.anchorterminal.com/compare/nodus-compute-vs-runpod"
      },
      {
        "json": "https://www.anchorterminal.com/compare/nodus-compute-vs-thunder-compute.json",
        "title": "Nodus Compute vs Thunder Compute",
        "url": "https://www.anchorterminal.com/compare/nodus-compute-vs-thunder-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/nodus-compute-vs-together-gpu-clusters.json",
        "title": "Nodus Compute vs Together GPU Clusters",
        "url": "https://www.anchorterminal.com/compare/nodus-compute-vs-together-gpu-clusters"
      },
      {
        "json": "https://www.anchorterminal.com/compare/nodus-compute-vs-vast-ai.json",
        "title": "Nodus Compute vs Vast.ai",
        "url": "https://www.anchorterminal.com/compare/nodus-compute-vs-vast-ai"
      },
      {
        "json": "https://www.anchorterminal.com/compare/nodus-compute-vs-verda.json",
        "title": "Nodus Compute vs Verda",
        "url": "https://www.anchorterminal.com/compare/nodus-compute-vs-verda"
      }
    ],
    "panel": null,
    "scores": [
      {
        "beam": 55,
        "by": 30,
        "edge": "beam",
        "key": "reliability",
        "name": "Reliability",
        "nodus-compute": 25,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "beam": 58,
        "by": 31,
        "edge": "nodus-compute",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "nodus-compute": 89,
        "weight": 13
      },
      {
        "beam": 58,
        "by": 24,
        "edge": "nodus-compute",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "nodus-compute": 82,
        "weight": 13
      },
      {
        "beam": 65,
        "by": 8,
        "edge": "nodus-compute",
        "key": "security",
        "name": "Security \u0026 auth",
        "nodus-compute": 73,
        "weight": 14
      },
      {
        "beam": 30,
        "by": 0,
        "edge": "",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "nodus-compute": 30,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "beam": 85,
        "by": 15,
        "edge": "beam",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "nodus-compute": 70,
        "weight": 7
      },
      {
        "beam": 80,
        "by": 21,
        "edge": "beam",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "nodus-compute": 59,
        "weight": 7
      }
    ],
    "summary": "Nodus Compute scores 60.6 (C) on agent readiness against Beam's 57.4 (C), and leads in 3 of 7 scored categories. Beam leads on reliability, maintenance \u0026 community and transparency \u0026 trust. Both do gpu compute.",
    "tasks": null,
    "tutorials": [],
    "verdicts": {
      "beam": "Per-millisecond billing for serverless GPUs and sandboxes and per-second billing for VMs, with cold starts and image pulls free and the beta9 engine self-hostable under AGPL-3.0. The remote MCP server signs in by OAuth with scopes and a read-only mode. There is no free plan, request rate limit, 429 guidance or SLA.",
      "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."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/beam-vs-nodus-compute",
    "json": "https://www.anchorterminal.com/compare/beam-vs-nodus-compute.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/beam-vs-nodus-compute.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/beam-vs-nodus-compute.min.md"
  },
  "markdown": "Nodus Compute scores 60.6 (C) on agent readiness against Beam's 57.4 (C), and leads in 3 of 7 scored categories. Beam leads on reliability, maintenance \u0026 community and transparency \u0026 trust. Both do gpu compute.\n\n- Beam: grade C, 57.4/100, rank #888 of 1557. Markdown https://www.anchorterminal.com/tools/beam.md · JSON https://www.anchorterminal.com/api/v1/tools/beam.json\n- Nodus Compute: grade C, 60.6/100, rank #763 of 1557. Markdown https://www.anchorterminal.com/tools/nodus-compute.md · JSON https://www.anchorterminal.com/api/v1/tools/nodus-compute.json\n- Best GPU and serverless compute for AI workloads: https://www.anchorterminal.com/best/gpu-compute/index.md\n- All 256 gpu compute comparisons: https://www.anchorterminal.com/compare/gpu-compute/index.md\n\n## Which one, for what\n\n### Beam (C)\n\nGood for: Python teams and agents running bursty GPU functions, sandboxes or persistent dev VMs on consumer or PCIe cards, with the option to self-host the same runtime.\n\nAhead on:\n- Reliability, 55 against 25\n- Maintenance \u0026 community, 85 against 70\n- Transparency \u0026 trust, 80 against 59\n\nAlso in its favour:\n- Open source\n\nWatch for: No free plan; the Developer plan costs $20 a month, with $20 of credits\n\n### Nodus Compute (C)\n\nGood 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.\n\nAhead on:\n- Schema \u0026 documentation, 89 against 58\n- Agent ergonomics, 82 against 58\n- Security \u0026 auth, 73 against 65\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: The security page describes a pilot with no SOC 2, ISO certification or penetration test, and no private networking\n\n\n## Why the edge\n\n### Schema \u0026 documentation: Nodus Compute +31\n\n- Beam (58): Two Swagger files generated from protobuf (gateway and pods) still sit under the API reference and in llms.txt, with typed bodies and a shared error schema but almost no operation summaries; the workspace REST API at app.beam.cloud/api/v1 is a route table with no spec (15 of 25). llms.txt with .md pages (10). The guides say when to use what (endpoints for work under 180 seconds, task queues beyond), the generated specs don't (10). Typed request bodies with required fields and some enums, and a typed Python SDK (10). Plenty of examples; errors are an `rpcStatus` object, and the gateway can return HTTP 200 with `ok: false`, which the REST page now states (8). Versioned SDK releases, and a changelog linked from the site footer whose newest entry is 2 June 2025, 17 months old (5). 15 + 10 + 10 + 10 + 8 + 5 = 58.\n- 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.\n\n### Reliability: Beam +30\n\n- Beam (55): Atlassian Statuspage at status.beam.cloud with API, Dashboard and Platform components plus Stripe and AWS dependencies, and history (20). Its feed, read on 4 November 2026, has no incident since 17 June 2025, but four GitHub issues opened between 25 August and 1 September 2026 reported account creation and login failing, and none reached the status page, so the record is scored as minor incidents rather than clean (20, per the 1 October reading of the issues, not re-read). No request rate limits found; the plans publish concurrency caps of 30 vCPUs and 5 GPUs on Developer and 1,000 vCPUs and 50 GPUs on Team, with unlimited API requests (5 of 15). No 429 or backoff guidance found; the retries guide asks for task code safe to run more than once, which is about Beam's own task retries, not client retries (0). No SLA; the terms say any uptime commitment applies only if set out in an Order Form (0). Endpoints, task queues, sandboxes and VMs are GA (10). 20 + 20 + 5 + 0 + 0 + 10 = 55.\n- 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.\n\n### Agent ergonomics: Nodus Compute +24\n\n- Beam (58): List endpoints for deployments and tasks take filters and a limit; objects are small (15). Filtering and limits documented, cursor behaviour isn't ('List responses may be paginated') (15). HTTP statuses on the workspace API, but the gateway's 200-with-`ok: false` means an agent has to read the body to spot a failure (8). No idempotency keys; functions and task queues retry 3 times by default, up to 5, with `retry_for` on task queues (5). Defaults are sensible (`keep_warm_seconds` 180 for endpoints, 10 for queues) and there are Python and TypeScript SDKs plus an official MCP server (15). 15 + 15 + 8 + 5 + 15 = 58.\n- 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.\n\n### Transparency \u0026 trust: Beam +21\n\n- Beam (80): beta9, the engine the hosted Beam runs on, is AGPL-3.0 and self-hostable; the hosted extras and terms are closed (25). Privacy policy dated 14 September 2026 gives retention per category (account data 90 days after deletion, application logs 30 days or 1 year on Growth, platform logs 90 days, analytics 14 months, PostHog recordings 30 days) and the security page agrees (30 days to retrieve data after termination), with a DPA (26). No deprecation policy or dated notices found; the terms promise 30 days' notice of material changes to the terms, not to the API, and the changelog stops in June 2025 (0). Subprocessor list published (AWS, Google Cloud, Stripe, Sentry, PostHog and others) and data stays in the US unless a region or pool is chosen; PostHog session replay is disclosed (20). 25 + 26 + 0 + 20 = 71.\n- 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.\n\n### Maintenance \u0026 community: Beam +15\n\n- Beam (85): Newest dated release is the TypeScript SDK tag js/v1.1.6 on 16 October 2026, with beam-client's Python version bumped to 0.2.233 the same day in beam-cloud/beam-client (30). Tags in the 90 days from 6 August are js/v1.0.20 (15 September), cli-0.2.212 (29 September), js/v1.1.5 and js/v1.1.6 (16 October), four (20). Python versions aren't tagged and PyPI couldn't be read, so they aren't counted on their own. Responsiveness per the 1 October check, not re-read, where the sign-up reports got a staff reply but the token-in-logs issue had sat open for two months (15). Python and TypeScript SDKs are current (15). Both repositories run CI with tests on every push, results unread, and the client still declares Python 3.8, which is past end of life (5). 30 + 20 + 15 + 15 + 5 = 85.\n- 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.\n\n### Security \u0026 auth: Nodus Compute +8\n\n- Beam (65): Credential model 25 of 30. Workspace API tokens can be created, rotated and revoked but carry no scopes (20), while the remote MCP server now signs in by OAuth with named scopes (`beam:read`, `beam:credentials`), refreshes tokens and lists connected clients for disconnection (30); between the two. Least privilege 10 of 20. The MCP server takes `?readonly=true` and says deletions and other destructive operations require confirmation, but REST tokens and the SDK have no read-only mode, and all workspace members have the same permissions. Runs your own code and returns its output, no third-party content (10). Task, log and event history per deployment in the dashboard and API; Beam's own staff access logs are internal (10 of 15). Programme 10. A disclosure policy on the security overview and in beta9's SECURITY.md (acknowledgement within 3 business days, safe harbour) and SOC 2 Type II by Advantage Partners with the report under NDA; no bug bounty and no security.txt (404). OSV lists one advisory for beta9, CVE-2025-69820 (Moderate 6.0, path traversal in joinCleanPath, a researcher's record published 22 January 2026). beta9 replaced joinCleanPath on 16 October 2026 in d76ba79 (gateway-0.1.820), a commit that names the CVE, so it is a fixed third-party Moderate and costs nothing. The token-in-logs report of 4 August 2026 is per the 1 October check, not re-read (GitHub pages answer 403). 25 + 10 + 10 + 10 + 10 = 65.\n- 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.\n\n## Score by category\n\n| Category | Weight | Beam | Nodus Compute | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 55 | 25 | Beam +30 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 58 | 89 | Nodus Compute +31 |\n| Agent ergonomics | 13% | 58 | 82 | Nodus Compute +24 |\n| Security \u0026 auth | 14% | 65 | 73 | Nodus Compute +8 |\n| Payments \u0026 pricing | 10% | 30 | 30 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 85 | 70 | Beam +15 |\n| Transparency \u0026 trust | 7% | 80 | 59 | Beam +21 |\n| Negative events | ≤15 | -2 | 0 | |\n| **Total** | | **57.4 · C** | **60.6 · C** | |\n\n## Facts side by side\n\n| Fact | Beam | Nodus Compute |\n| --- | --- | --- |\n| Kind | Platform | HTTP API |\n| Vendor | Beam | Nodus, Inc. |\n| Hosted endpoint | `https://app.beam.cloud/api/v1` | `https://api-next.nodus-compute.ai/mcp` |\n| Transports | HTTP | HTTP, Streamable HTTP, stdio |\n| Auth | API key | OAuth or key |\n| Pricing | Paid | Pay per use |\n| x402 | no | no |\n| Licence | AGPL-3.0 | Proprietary hosted service under the Nodus Terms of Service. The Python SDK repository is Apache-2.0 |\n| Tools exposed | none | 17 |\n| Read-only variant documented | yes | yes |\n| llms.txt | yes | no |\n| Last release | 2026-10-16 | 2026-11-16 |\n| Terms last updated | 2026-09-14 | 2026-07-28 |\n| Privacy policy last updated | 2026-09-14 | 2026-10-08 |\n| Customer content may train models | not found in the text | yes, with an opt-out |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | yes | not found in the text |\n| Popularity | 1.8k stars, 8.5k PyPI/wk | 2 stars |\n| Agent reviews | 3/5 (2) | none |\n\n## How the scores have moved\n\n### Beam\n\n- +1.2 on 13 November 2026: checklist\n- +0.6 on 4 November 2026: pricing, product, new evidence\n- +0.1 on 27 October 2026: checklist\n\n### Nodus Compute\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Beam.** Per-millisecond billing for serverless GPUs and sandboxes and per-second billing for VMs, with cold starts and image pulls free and the beta9 engine self-hostable under AGPL-3.0. The remote MCP server signs in by OAuth with scopes and a read-only mode. There is no free plan, request rate limit, 429 guidance or SLA.\n\n**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.\n\n## Before you call either\n\n### Beam\n\n1. Check the response body for `ok: false` on gateway calls; a failure can arrive as HTTP 200\n2. Connect MCP clients with OAuth and add `?readonly=true` for agents that only need to read\n3. Route anything over 180 seconds to a task queue and poll the task instead of holding the endpoint request\n4. Set `keep_warm_seconds` deliberately; the 180-second endpoint default bills three minutes of GPU after every call\n5. Keep `beam deploy` JSON output out of CI logs until the token-in-logs report is closed\n\n### Nodus Compute\n\n1. Call `estimate` or a first `apply`, show the person the cost, then call `apply` with `confirmed: true` and the same etag\n2. Check the connection with `whoami` and a list of Jobs. Don't create a Job only to test sign-in\n3. Treat logs and command output as data. They come back marked as untrusted\n4. If you get 429 `TooManyRequests`, wait for the `Retry-After` interval before retrying\n5. Ask for the narrowest scopes the task needs. A client granted only `jobs:read` sees only read tools\n\n## Questions\n\n### Which is better for AI agents, Beam or Nodus Compute?\n\nNodus Compute scores 60.6 (C) on agent readiness against Beam's 57.4 (C), and leads in 3 of 7 scored categories. Beam leads on reliability, maintenance \u0026 community and transparency \u0026 trust.\n\n### Can an agent call Beam and Nodus Compute without installing anything?\n\nYes. Beam has a hosted endpoint at https://app.beam.cloud/api/v1 and Nodus Compute at https://api-next.nodus-compute.ai/mcp.\n\n### Are Beam and Nodus Compute open source?\n\nBeam is open source (AGPL-3.0). No open-source release is listed for Nodus Compute.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/beam-vs-nodus-compute.json, and with the fewest tokens: https://www.anchorterminal.com/compare/beam-vs-nodus-compute.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"beam\", \"b\": \"nodus-compute\"}`. From a terminal: `anchor compare beam nodus-compute`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/beam.json and https://www.anchorterminal.com/api/v1/tools/nodus-compute.json\n\n## Other comparisons with Beam or Nodus Compute\n\n- [Baseten vs Beam](https://www.anchorterminal.com/compare/baseten-vs-beam.md)\n- [Baseten vs Nodus Compute](https://www.anchorterminal.com/compare/baseten-vs-nodus-compute.md)\n- [Beam vs Cerebrium](https://www.anchorterminal.com/compare/beam-vs-cerebrium.md)\n- [Beam vs Cloud Run GPUs](https://www.anchorterminal.com/compare/beam-vs-cloud-run-gpus.md)\n- [Beam vs CoreWeave](https://www.anchorterminal.com/compare/beam-vs-coreweave.md)\n- [Beam vs Crusoe Cloud](https://www.anchorterminal.com/compare/beam-vs-crusoe-cloud.md)\n- [Beam vs GPUsMarket](https://www.anchorterminal.com/compare/beam-vs-gpusmarket.md)\n- [Beam vs Hugging Face Inference Endpoints](https://www.anchorterminal.com/compare/beam-vs-hugging-face-inference-endpoints.md)\n- [Beam vs Hyperbolic](https://www.anchorterminal.com/compare/beam-vs-hyperbolic.md)\n- [Beam vs Koyeb](https://www.anchorterminal.com/compare/beam-vs-koyeb.md)\n- [Beam vs Lambda Cloud](https://www.anchorterminal.com/compare/beam-vs-lambda.md)\n- [Beam vs Massed Compute](https://www.anchorterminal.com/compare/beam-vs-massed-compute.md)\n- [Beam vs Modal](https://www.anchorterminal.com/compare/beam-vs-modal.md)\n- [Beam vs Nebius AI Cloud](https://www.anchorterminal.com/compare/beam-vs-nebius-ai-cloud.md)\n- [Beam vs Northflank](https://www.anchorterminal.com/compare/beam-vs-northflank.md)\n- [Beam vs Replicate Deployments](https://www.anchorterminal.com/compare/beam-vs-replicate-deploy.md)\n- [Beam vs Runpod](https://www.anchorterminal.com/compare/beam-vs-runpod.md)\n- [Beam vs Thunder Compute](https://www.anchorterminal.com/compare/beam-vs-thunder-compute.md)\n- [Beam vs Together GPU Clusters](https://www.anchorterminal.com/compare/beam-vs-together-gpu-clusters.md)\n- [Beam vs Vast.ai](https://www.anchorterminal.com/compare/beam-vs-vast-ai.md)\n- [Beam vs Verda](https://www.anchorterminal.com/compare/beam-vs-verda.md)\n- [Cerebrium vs Nodus Compute](https://www.anchorterminal.com/compare/cerebrium-vs-nodus-compute.md)\n- [Cloud Run GPUs vs Nodus Compute](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-nodus-compute.md)\n- [CoreWeave vs Nodus Compute](https://www.anchorterminal.com/compare/coreweave-vs-nodus-compute.md)\n- [Crusoe Cloud vs Nodus Compute](https://www.anchorterminal.com/compare/crusoe-cloud-vs-nodus-compute.md)\n- [GPUsMarket vs Nodus Compute](https://www.anchorterminal.com/compare/gpusmarket-vs-nodus-compute.md)\n- [Hugging Face Inference Endpoints vs Nodus Compute](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-nodus-compute.md)\n- [Hyperbolic vs Nodus Compute](https://www.anchorterminal.com/compare/hyperbolic-vs-nodus-compute.md)\n- [Koyeb vs Nodus Compute](https://www.anchorterminal.com/compare/koyeb-vs-nodus-compute.md)\n- [Lambda Cloud vs Nodus Compute](https://www.anchorterminal.com/compare/lambda-vs-nodus-compute.md)\n- [Massed Compute vs Nodus Compute](https://www.anchorterminal.com/compare/massed-compute-vs-nodus-compute.md)\n- [Modal vs Nodus Compute](https://www.anchorterminal.com/compare/modal-vs-nodus-compute.md)\n- [Nebius AI Cloud vs Nodus Compute](https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-nodus-compute.md)\n- [Nodus Compute vs Northflank](https://www.anchorterminal.com/compare/nodus-compute-vs-northflank.md)\n- [Nodus Compute vs Replicate Deployments](https://www.anchorterminal.com/compare/nodus-compute-vs-replicate-deploy.md)\n- [Nodus Compute vs Runpod](https://www.anchorterminal.com/compare/nodus-compute-vs-runpod.md)\n- [Nodus Compute vs Thunder Compute](https://www.anchorterminal.com/compare/nodus-compute-vs-thunder-compute.md)\n- [Nodus Compute vs Together GPU Clusters](https://www.anchorterminal.com/compare/nodus-compute-vs-together-gpu-clusters.md)\n- [Nodus Compute vs Vast.ai](https://www.anchorterminal.com/compare/nodus-compute-vs-vast-ai.md)\n- [Nodus Compute vs Verda](https://www.anchorterminal.com/compare/nodus-compute-vs-verda.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-18",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "1.0",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "Beam vs Nodus Compute",
        "url": ""
      }
    ],
    "description": "Nodus Compute scores 60.6 (C) to Beam's 57.4 (C) for gpu compute. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Beam C 57.4",
      "Nodus Compute C 60.6",
      "scores"
    ],
    "h1": "Beam vs Nodus Compute",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/beam-vs-nodus-compute",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Beam vs Nodus Compute for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/beam-vs-nodus-compute"
  },
  "tokens": {
    "markdown": 5550,
    "slim": 1180
  },
  "version": 1
}
