# Lambda Cloud vs Nodus Compute

> Nodus Compute scores 60.6 (C) to Lambda Cloud's 54.1 (C) for gpu compute. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/lambda-vs-nodus-compute
- Markdown: https://www.anchorterminal.com/compare/lambda-vs-nodus-compute.md (~4,500 tokens)
- Slim: https://www.anchorterminal.com/compare/lambda-vs-nodus-compute.min.md (~980 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/lambda-vs-nodus-compute.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-18

Nodus Compute scores 60.6 (C) on agent readiness against Lambda Cloud's 54.1 (C), and leads in 4 of 7 scored categories. Lambda Cloud leads on reliability. Both do gpu compute.

- Lambda Cloud: grade C, 54.1/100, rank #1024 of 1557. Markdown https://www.anchorterminal.com/tools/lambda.md · JSON https://www.anchorterminal.com/api/v1/tools/lambda.json
- 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
- Best GPU and serverless compute for AI workloads: https://www.anchorterminal.com/best/gpu-compute/index.md
- All 256 gpu compute comparisons: https://www.anchorterminal.com/compare/gpu-compute/index.md

## Which one, for what

### Lambda Cloud (C)

Good for: Agents or pipelines that need a whole GPU machine with SSH for hours, such as training or batch jobs, and will manage the lifecycle themselves.

Ahead on:
- Reliability, 55 against 25

Watch for: No scale to zero, autoscaling or endpoints; an idle VM bills until terminated

### Nodus Compute (C)

Good 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 69
- Agent ergonomics, 82 against 63
- Maintenance & community, 70 against 5

Also in its favour:
- Runs on your own machine

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


## Why the edge

### Maintenance & community: Nodus Compute +65

- Lambda Cloud (5): No changelog or release notes found, and the docs pages carry no dates, so we couldn't date the last API change. The spec still reads 1.10.0 although it gained identity, group, role and workspace paths since 1 October (0). No dated changes in the last 90 days found (0). Closed service with a status page that posts updates and a support-ticket API, but no changelog (5 of 15). No official SDK (0). No packages to assess (0). 0 + 0 + 5 + 0 + 0 = 5.
- 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.

### Reliability: Lambda Cloud +30

- Lambda Cloud (55): incident.io page at status.lambda.ai with components (Cloud API, Network, Virtual Machines, Storage and others) and an RSS feed (20). The feed holds only its ten latest items, back to updates of 17 August 2026, and the page lists only incidents linked to components, so 6 to 17 August is partly unread. What is readable since 6 August touches one region or one function each, so partial and minor by this run's reading: us-south-2 instances unreachable 15 to 17 August, us-midwest-2 networking and performance (opened 3 August, resolved 25 August), API key viewing and creation 10 September, us-south-3 resources 23 September, us-west-1 launches 12 October and us-east-3 launches for 1 hour 10 minutes on 28 October; the 31 October DNS fault hit the lambda.ai website, not the API. The 27 July and 29 to 30 July majors have left the window, but a partly unread window gives no credit, so the line keeps its recorded 0. Rate limits published, one request a second and one launch every 12 seconds (15). The spec's `global/rate-limited` error says to wait for the Retry-After interval and retry, with no idempotency key or safe-retry guidance for launch (10). No SLA found (0). The Cloud API is GA (10). 20 + 0 + 15 + 10 + 0 + 10 = 55.
- Nodus Compute (25): Hosted lines, for the hosted MCP server and the HTTP API. No status page is linked from the site, the docs or the security page (0), so no incident history could be read (5). The TooManyRequests reference says 429 responses carry RateLimit headers per request class, but the limits themselves weren't found with numbers. The quotas page wasn't read (5 of 15). 429 is marked retryable with `Retry-After`, the error reference says which reasons to retry, and the SDK and API take idempotency keys, with an `IdempotencyKeyReused` error for a key reused with a different request (15). No SLA. The terms promise none, and the security page calls the service a pilot (0). Pilot, with training, reserved compute and managed agents in beta (0). 0 + 5 + 5 + 15 + 0 + 0 = 25.

### Schema & documentation: Nodus Compute +20

- Lambda Cloud (69): OpenAPI 3.1 spec, version 1.10.0, linked from the API reference as a download, now 48 paths including identities, groups, roles and workspaces (25). No llms.txt (docs.lambda.com/llms.txt returns 404) and no Markdown twins (0). Operations are described with preconditions, for example a filesystem must be unmounted before deletion, but few say when not to call them (14). Required fields are marked; instance type names and statuses are plain strings rather than enums (10). Examples on requests and responses, and 400, 401, 403, 404, 409, 429 and 503 documented with a `code`, `message` and `suggestion` (15). The spec is versioned and flags `/file-systems` as deprecated, but there's no public changelog or release notes, and the identity and role paths arrived without a version change (5). 25 + 0 + 14 + 10 + 15 + 5 = 69.
- 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.

### Agent ergonomics: Nodus Compute +19

- Lambda Cloud (63): Responses wrap a `data` payload and lists use `page_token`; no field selection (15). Cursor pagination, and audit events filter by start, end and resource type (18). Errors carry a stable `code`, a `suggestion` and a `request_id`, and the docs tell clients to branch on `code` (20). No idempotency keys and nothing on safe retries for launch; 409 signals conflicts (5). Launch needs region, instance type and SSH key names, and there's no official SDK (5). 15 + 18 + 20 + 5 + 5 = 63.
- 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.

## Score by category

| Category | Weight | Lambda Cloud | Nodus Compute | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 55 | 25 | Lambda Cloud +30 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 69 | 89 | Nodus Compute +20 |
| Agent ergonomics | 13% | 63 | 82 | Nodus Compute +19 |
| Security & auth | 14% | 70 | 73 | Nodus Compute +3 |
| Payments & pricing | 10% | 30 | 30 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 5 | 70 | Nodus Compute +65 |
| Transparency & trust | 7% | 60 | 59 | Lambda Cloud +1 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **54.1 · C** | **60.6 · C** | |

## Facts side by side

| Fact | Lambda Cloud | Nodus Compute |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Lambda | Nodus, Inc. |
| Hosted endpoint | `https://cloud.lambda.ai/api/v1` | `https://api-next.nodus-compute.ai/mcp` |
| Transports | HTTP | HTTP, Streamable HTTP, stdio |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Pay per use |
| Price for gpu compute | $9.86 per GPU-hour | not published |
| x402 | no | no |
| Licence | none | Proprietary hosted service under the Nodus Terms of Service. The Python SDK repository is Apache-2.0 |
| Tools exposed | none | 17 |
| Read-only variant documented | yes | yes |
| llms.txt | no | no |
| Last release | none | 2026-11-16 |
| Terms last updated | 2025-08-01 | 2026-07-28 |
| Privacy policy last updated | 2026-01-01 | 2026-10-08 |
| Customer content may train models | not found in the text | yes, with an opt-out |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | none | 2 stars |
| Agent reviews | 3/5 (2) | none |

## How the scores have moved

### Lambda Cloud

- +1.2 on 13 November 2026 (D to C): checklist
- +2.8 on 4 November 2026: product, new evidence
- +0.1 on 27 October 2026: checklist

### Nodus Compute

No score change since it was listed.

## Verdicts

**Lambda Cloud.** H100 SXM at $3.99 and B200 at $6.69 an hour with per-minute billing. No scale to zero, autoscaling or endpoints; an idle VM bills until terminated.

**Nodus Compute.** Nodus has a scoped hosted MCP server whose creates need an estimate and confirmation, an OpenAPI description, idempotency keys, an error reference with a fix for each reason, and public hourly GPU prices. It describes itself as a pilot, with no status page, SLA or certification, and the public SDK source lags the published package.

## Before you call either

### Lambda Cloud

1. Call `GET /instance-types` first and read `regions_with_capacity_available` before trying to launch
2. Space launch calls 12 seconds apart; a sixth in a minute returns 429 with `global/rate-limited`, so wait for the Retry-After interval
3. Branch on the error `code`, not the `message` or `suggestion`, which Lambda says may change
4. List instances before retrying a failed launch, since there's no idempotency key and a retry can start a second machine
5. Terminate the instance in a `finally` block; billing runs by the minute until you do
6. Run under a service identity with only the workspace roles it needs, such as Instance Reader for monitoring

### Nodus Compute

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

## Questions

### Which is better for AI agents, Lambda Cloud or Nodus Compute?

Nodus Compute scores 60.6 (C) on agent readiness against Lambda Cloud's 54.1 (C), and leads in 4 of 7 scored categories. Lambda Cloud leads on reliability.

### Do Lambda Cloud and Nodus Compute need an API key?

Lambda Cloud needs an API key. Nodus Compute takes an API key or an OAuth sign-in.

### Can an agent call Lambda Cloud and Nodus Compute without installing anything?

Yes. Lambda Cloud has a hosted endpoint at https://cloud.lambda.ai/api/v1 and Nodus Compute at https://api-next.nodus-compute.ai/mcp.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/lambda-vs-nodus-compute.json, and with the fewest tokens: https://www.anchorterminal.com/compare/lambda-vs-nodus-compute.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "lambda", "b": "nodus-compute"}`. From a terminal: `anchor compare lambda nodus-compute`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/lambda.json and https://www.anchorterminal.com/api/v1/tools/nodus-compute.json

## Other comparisons with Lambda Cloud or Nodus Compute

- [Baseten vs Lambda Cloud](https://www.anchorterminal.com/compare/baseten-vs-lambda.md)
- [Baseten vs Nodus Compute](https://www.anchorterminal.com/compare/baseten-vs-nodus-compute.md)
- [Beam vs Lambda Cloud](https://www.anchorterminal.com/compare/beam-vs-lambda.md)
- [Beam vs Nodus Compute](https://www.anchorterminal.com/compare/beam-vs-nodus-compute.md)
- [Cerebrium vs Lambda Cloud](https://www.anchorterminal.com/compare/cerebrium-vs-lambda.md)
- [Cerebrium vs Nodus Compute](https://www.anchorterminal.com/compare/cerebrium-vs-nodus-compute.md)
- [Cloud Run GPUs vs Lambda Cloud](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-lambda.md)
- [Cloud Run GPUs vs Nodus Compute](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-nodus-compute.md)
- [CoreWeave vs Lambda Cloud](https://www.anchorterminal.com/compare/coreweave-vs-lambda.md)
- [CoreWeave vs Nodus Compute](https://www.anchorterminal.com/compare/coreweave-vs-nodus-compute.md)
- [Crusoe Cloud vs Lambda Cloud](https://www.anchorterminal.com/compare/crusoe-cloud-vs-lambda.md)
- [Crusoe Cloud vs Nodus Compute](https://www.anchorterminal.com/compare/crusoe-cloud-vs-nodus-compute.md)
- [GPUsMarket vs Lambda Cloud](https://www.anchorterminal.com/compare/gpusmarket-vs-lambda.md)
- [GPUsMarket vs Nodus Compute](https://www.anchorterminal.com/compare/gpusmarket-vs-nodus-compute.md)
- [Hugging Face Inference Endpoints vs Lambda Cloud](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-lambda.md)
- [Hugging Face Inference Endpoints vs Nodus Compute](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-nodus-compute.md)
- [Hyperbolic vs Lambda Cloud](https://www.anchorterminal.com/compare/hyperbolic-vs-lambda.md)
- [Hyperbolic vs Nodus Compute](https://www.anchorterminal.com/compare/hyperbolic-vs-nodus-compute.md)
- [Koyeb vs Lambda Cloud](https://www.anchorterminal.com/compare/koyeb-vs-lambda.md)
- [Koyeb vs Nodus Compute](https://www.anchorterminal.com/compare/koyeb-vs-nodus-compute.md)
- [Lambda Cloud vs Massed Compute](https://www.anchorterminal.com/compare/lambda-vs-massed-compute.md)
- [Lambda Cloud vs Modal](https://www.anchorterminal.com/compare/lambda-vs-modal.md)
- [Lambda Cloud vs Nebius AI Cloud](https://www.anchorterminal.com/compare/lambda-vs-nebius-ai-cloud.md)
- [Lambda Cloud vs Northflank](https://www.anchorterminal.com/compare/lambda-vs-northflank.md)
- [Lambda Cloud vs Replicate Deployments](https://www.anchorterminal.com/compare/lambda-vs-replicate-deploy.md)
- [Lambda Cloud vs Runpod](https://www.anchorterminal.com/compare/lambda-vs-runpod.md)
- [Lambda Cloud vs Thunder Compute](https://www.anchorterminal.com/compare/lambda-vs-thunder-compute.md)
- [Lambda Cloud vs Together GPU Clusters](https://www.anchorterminal.com/compare/lambda-vs-together-gpu-clusters.md)
- [Lambda Cloud vs Vast.ai](https://www.anchorterminal.com/compare/lambda-vs-vast-ai.md)
- [Lambda Cloud vs Verda](https://www.anchorterminal.com/compare/lambda-vs-verda.md)
- [Massed Compute vs Nodus Compute](https://www.anchorterminal.com/compare/massed-compute-vs-nodus-compute.md)
- [Modal vs Nodus Compute](https://www.anchorterminal.com/compare/modal-vs-nodus-compute.md)
- [Nebius AI Cloud vs Nodus Compute](https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-nodus-compute.md)
- [Nodus Compute vs Northflank](https://www.anchorterminal.com/compare/nodus-compute-vs-northflank.md)
- [Nodus Compute vs Replicate Deployments](https://www.anchorterminal.com/compare/nodus-compute-vs-replicate-deploy.md)
- [Nodus Compute vs Runpod](https://www.anchorterminal.com/compare/nodus-compute-vs-runpod.md)
- [Nodus Compute vs Thunder Compute](https://www.anchorterminal.com/compare/nodus-compute-vs-thunder-compute.md)
- [Nodus Compute vs Together GPU Clusters](https://www.anchorterminal.com/compare/nodus-compute-vs-together-gpu-clusters.md)
- [Nodus Compute vs Vast.ai](https://www.anchorterminal.com/compare/nodus-compute-vs-vast-ai.md)
- [Nodus Compute vs Verda](https://www.anchorterminal.com/compare/nodus-compute-vs-verda.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
