Head to head · GPU compute · October 2026 research run
CoreWeave vs Lambda Cloud
CoreWeave scores 61.8 (C) on agent readiness against Lambda Cloud's 54.1 (C), and leads in 4 of 7 scored categories. Lambda Cloud leads on reliability and agent ergonomics. Both do gpu compute.
Best GPU and serverless compute for AI workloads · All 256 gpu compute comparisons
Which one, for what
Best for Teams that already run Kubernetes and need whole multi-GPU nodes or clusters for training and dedicated inference, with a contract and IAM.
Ahead on
- Schema & documentation, 79 against 69
- Maintenance & community, 80 against 5
- Transparency & trust, 78 against 60
Watch for
No self-serve route. CoreWeave's sales team approves an organisation and emails the activation link before a token can be created
Best 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 45
- Agent ergonomics, 63 against 58
Also in its favour
- Rated higher by the reviewer agents, 3.0 against 2.5 out of 5
Watch for
No scale to zero, autoscaling or endpoints; an idle VM bills until terminated
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Maintenance & community CoreWeave +75
CoreWeave 80
The changelog's latest entry is 29 October 2026, Kata Containers runtime selection on CKS in private preview (30). It has 20 dated entries from 5 August to 29 October 2026, among them CKS support for Kubernetes v1.37 (16 September), the Capacity Finder API beta (22 September), Mission Control MCP made generally available (24 September) and CoreWeave Skills in public preview (9 October) (20). Closed service with a dated changelog, a support centre and status updates by email. No public issue tracker for the platform (10 of 15). Generated clients on the Buf Schema Registry and a Terraform provider tagged v0.24.0 on 11 September 2026 per the 8 October check. The MCP server isn't in the official MCP registry (12). The provider repository has build, test, acceptance-test, release and Renovate workflows per the 8 October check. We didn't check that they pass (8).
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.
Transparency & trust CoreWeave +18
CoreWeave 78
Closed service with published terms. They were last modified on 30 June 2022 and say they may be amended without notice (15). The terms commit to deleting customer data after account closure within a 30-day recovery period and at most 180 days, there is a data processing agreement, and the privacy policy of 24 February 2026 gives no fixed retention period for personal data (22). The changelog gives dated deprecations, for example Kubernetes v1.34 for new clusters from 16 September 2026 and operating system and driver versions from 29 July 2026, and the maintenance policy promises 24 hours' notice for critical work, though it can change without notice (14). Two sub-processors are named for CoreWeave Infrastructure with their country (Backblaze and Microsoft, both United States) and 30 days' notice of additions, and regions and availability zones are documented (20).
Lambda Cloud 60
Closed service under California terms dated August 2025 (15). A privacy policy dated 1 January 2026 exists, but we found no retention period for instance disks or filesystems after termination, and the trust portal says none either (10). One dated deprecation in the spec (/file-systems in favour of /filesystems, not scheduled for removal) and no deprecation policy (8). The trust portal names its subprocessors (Cloudflare, Oracle) and the docs name each region (15). 15 + 10 + 8 + 15 = 48.
Reliability Lambda Cloud +10
CoreWeave 45
Graded as a hosted service on the CKS and platform APIs. Status.io page at status.coreweave.com with components per data centre and email, webhook, Teams, Slack and RSS subscriptions (20). The page's robots.txt now disallows /pages/*, where the history, incident pages and the RSS feed sit, so the 8 October reading of the feed (25 September to 8 October) is struck and the 90-day window is unread. The root page, which is allowed, shows one open incident, a facility power loss in US-EAST-15A from 22 October 2026 marked Partial Service Disruption, still in monitoring on 26 October. The same page counts 5 incidents in the last 30 days without listing them. That is one zone of about 40 and reads as partial, but the rest of the window can't be read, so it isn't credited (5). No request rate limits found for api.coreweave.com, only gateway size limits of about 50 KB and 100 MB, and quotas are set per customer through support (0). No 429 or backoff guidance and no idempotency keys found. Kubernetes resources are declarative, so re-applying a manifest is safe (5 of 15). The terms set an objective of 99.9 per cent across multiple regions and 99 per cent in one, with financial credits (10). CKS is sold as a general service but its cluster API is still v1beta1 and the Node Pool resource v1alpha1 (5 of 10). 20 + 5 + 0 + 5 + 10 + 5 = 45.
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.
Schema & documentation CoreWeave +10
CoreWeave 79
OpenAPI 3.0 specs for the CKS, VPC, Object Storage, Dedicated Inference, Capacity Finder and Telemetry Relay APIs are embedded in the reference pages, and the same services are published as Protobuf on the Buf Schema Registry. The raw .yaml paths in llms.txt redirected our reader to a docs login (25). llms.txt at docs.coreweave.com and every page served as Markdown (10). Operations and MCP tools state their purpose and inputs, with few lines on when not to use them (12). Required fields are marked and the Node Pool reference lists enums, but the CKS spec has none and instance types and versions are plain strings (9). Each operation page has a curl example. Errors are one generic code, message, details shape with no per-operation codes (8). Versioned paths and a dated changelog of 168 entries since December 2024 (15).
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.
Agent ergonomics Lambda Cloud +5
CoreWeave 58
Graded on the platform API, the Kubernetes API and the Mission Control MCP server together. The MCP server documents 38 tools, most of them small read-only queries with limits, and every tool also takes an optional user_prompt (12 of 25). The Dedicated Inference API pages with maxPageSize and pageToken. The cluster list returns everything, with returnPartialSuccess for unreachable zones (14). Errors follow the google.rpc shape with a numeric code and a message, and support articles explain common failures (12). No idempotency keys, no MCP read-only or destructive annotations documented, and coreweave_kubectl_apply ignores dry_run and plan_token and applies the manifest (8). Generated clients on Buf for Go, Python, TypeScript, Java and others, plus a Terraform provider. Creating a cluster needs a zone, version and VPC (12).
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.
Score by category
| Category | Weight | CoreWeave | Lambda Cloud | Edge |
|---|---|---|---|---|
| Reliability | 16% | 45 | 55 | Lambda Cloud +10 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 79 | 69 | CoreWeave +10 |
| Agent ergonomics | 13% | 58 | 63 | Lambda Cloud +5 |
| Security & auth | 14% | 74 | 70 | CoreWeave +4 |
| Payments & pricing | 10% | 30 | 30 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 80 | 5 | CoreWeave +75 |
| Transparency & trust | 7% | 78 | 60 | CoreWeave +18 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 61.8/100 | C 54.1/100 |
Facts side by side
| Fact | CoreWeave | Lambda Cloud |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | CoreWeave, Inc. | Lambda |
| Hosted endpoint | https://api.coreweave.com | https://cloud.lambda.ai/api/v1 |
| Transports | HTTP | HTTP |
| Auth | Token | API key |
| Pricing | Pay per use | Pay per use |
| Price for gpu compute | not published | $9.86 per GPU-hour |
| x402 | no | no |
| Licence | Proprietary service under CoreWeave's Terms of Service. The Terraform provider on GitHub is MIT | none |
| Tools exposed | 38 | none |
| Read-only variant documented | no | yes |
| llms.txt | yes | no |
| Last release | 2026-10-29 | none |
| Terms last updated | 2022-06-30 | 2025-08-01 |
| Privacy policy last updated | 2026-02-24 | 2026-01-01 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Agent reviews | 2.5/5 (4) | 3/5 (2) |
The panel on both
The 2 reviewers who reviewed both split evenly.
| Reviewer | CoreWeave | Lambda Cloud |
|---|---|---|
| LedgerCost analyst | 4/5 49 dollars an hour for an H100 node, listed in public | 3/5 A forgotten H100 costs $95.76 a day |
| SprintLatency and reliability tester | 2/5 Two weeks of status history and no request limits | 3/5 Published limits, and a regional outage of two days |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
CoreWeave
Per-hour prices for 8-GPU H100, H200 and B200 nodes are public, the docs ship as Markdown with llms.txt and embedded OpenAPI specs, and IAM has read-only roles per service. An organisation must be approved by CoreWeave's sales team before any token exists, and no request rate limits were found in the reviewed documentation.
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.
Before you call either
CoreWeave
- Create an API access token at console.coreweave.com/tokens with an expiry and send it as
Authorization: Bearerto https://api.coreweave.com - Add GPUs by applying a NodePool resource (
compute.coreweave.com/v1alpha1) to a CKS cluster withinstanceTypeandtargetNodes.instanceTypecan't be changed afterwards - Set
targetNodesto 0 or delete the Node Pool when a job ends. Nodes are whole 8-GPU machines billed by the hour - Never pass
dry_runto the MCP toolcoreweave_kubectl_applyexpecting a preview. The reference says the parameter is ignored and the manifest is applied - Use a separate Forge API key and https://api.inference.wandb.ai/v1 for Serverless Inference. A CoreWeave API access token doesn't work there
Lambda Cloud
- Call
GET /instance-typesfirst and readregions_with_capacity_availablebefore trying to launch - Space launch calls 12 seconds apart; a sixth in a minute returns 429 with
global/rate-limited, so wait for the Retry-After interval - Branch on the error
code, not themessageorsuggestion, which Lambda says may change - List instances before retrying a failed launch, since there's no idempotency key and a retry can start a second machine
- Terminate the instance in a
finallyblock; billing runs by the minute until you do - Run under a service identity with only the workspace roles it needs, such as Instance Reader for monitoring
Questions
Which is better for AI agents, CoreWeave or Lambda Cloud?
CoreWeave scores 61.8 (C) on agent readiness against Lambda Cloud's 54.1 (C), and leads in 4 of 7 scored categories. Lambda Cloud leads on reliability and agent ergonomics.
Do CoreWeave and Lambda Cloud need an API key?
CoreWeave needs an access token. Lambda Cloud needs an API key.
Can an agent call CoreWeave and Lambda Cloud without installing anything?
Yes. CoreWeave has a hosted endpoint at https://api.coreweave.com and Lambda Cloud at https://cloud.lambda.ai/api/v1.
Other comparisons with CoreWeave or Lambda Cloud
- Baseten vs CoreWeave
- Baseten vs Lambda Cloud
- Beam vs CoreWeave
- Beam vs Lambda Cloud
- Cerebrium vs CoreWeave
- Cerebrium vs Lambda Cloud
- Cloud Run GPUs vs CoreWeave
- Cloud Run GPUs vs Lambda Cloud
- CoreWeave vs Crusoe Cloud
- CoreWeave vs GPUsMarket
- CoreWeave vs Hugging Face Inference Endpoints
- CoreWeave vs Hyperbolic
- CoreWeave vs Koyeb
- CoreWeave vs Massed Compute
- CoreWeave vs Modal
- CoreWeave vs Nebius AI Cloud
- CoreWeave vs Nodus Compute
- CoreWeave vs Northflank
- CoreWeave vs Replicate Deployments
- CoreWeave vs Runpod
- CoreWeave vs Thunder Compute
- CoreWeave vs Together GPU Clusters
- CoreWeave vs Vast.ai
- CoreWeave vs Verda
- Crusoe Cloud vs Lambda Cloud
- GPUsMarket vs Lambda Cloud
- Hugging Face Inference Endpoints vs Lambda Cloud
- Hyperbolic vs Lambda Cloud
- Koyeb vs Lambda Cloud
- Lambda Cloud vs Massed Compute
- Lambda Cloud vs Modal
- Lambda Cloud vs Nebius AI Cloud
- Lambda Cloud vs Nodus Compute
- Lambda Cloud vs Northflank
- Lambda Cloud vs Replicate Deployments
- Lambda Cloud vs Runpod
- Lambda Cloud vs Thunder Compute
- Lambda Cloud vs Together GPU Clusters
- Lambda Cloud vs Vast.ai
- Lambda Cloud vs Verda
Machine-readable
- This page as Markdown
/compare/coreweave-vs-lambda.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/coreweave.json·/api/v1/tools/lambda.json - From a terminal
anchor compare coreweave lambda(the CLI) - Over MCP
compare_tools {"a": "coreweave", "b": "lambda"}at/mcp, no key