Head to head · GPU compute · October 2026 research run

Baseten vs Lambda Cloud

Baseten scores 65.2 (B) on agent readiness against Lambda Cloud's 54.1 (C), and leads in 6 of 7 scored categories. Lambda Cloud leads on agent ergonomics. Both do gpu compute.

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

Which one, for what

Baseten B

Best for Teams that want one model behind a production endpoint with real autoscaling knobs, environments and scoped keys.

Ahead on

  • Reliability, 90 against 55
  • Schema & documentation, 84 against 69
  • Security & auth, 82 against 70
  • Payments & pricing, 60 against 30
  • Maintenance & community, 90 against 5
  • Transparency & trust, 67 against 60

Also in its favour

  • Open source
  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5

Watch for

H100 at $6.50 and A100 at $4.00 an hour, and start-up and idle replica time are billed

Lambda Cloud C

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

  • Agent ergonomics, 63 against 55

Also in its favour

  • No incidents deducted, where Baseten loses 11 points for them

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 Baseten +85

Baseten 90

A changelog entry on 30 October 2026 (mixed-mode rolling promotions) and Truss v0.18.37 tagged on 29 October (30). In the 90 days from 3 August, 13 stable Truss tags (v0.18.25 on 3 August to v0.18.37) and 31 dated changelog entries from 14 August to 30 October (20). Truss had 9 open issues, the recent ones answered within days, but a 24 August request for a private security contact had one reply and two January 2026 deployment issues sat unanswered, per the 1 October check; GitHub's pages weren't readable on 1 November (18). Truss, the Baseten CLI (v1.4.1 on 22 October) and a JavaScript client are current (15). Release workflow runs in GitHub Actions and Truss supports Python 3.9 to 3.14, but an open issue reports the npm performance client shipping without its platform dependencies since 0.0.10, per the 1 October check (7). 30 + 20 + 18 + 15 + 7 = 90.

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.

Reliability Baseten +35

Baseten 90

Atlassian Statuspage at status.baseten.co with incident history (20). Its history pages list 27 incidents from 3 August to 1 November 2026, 7 of them labelled major, plus three scheduled database upgrades. Every one is scoped to one Model API model, one cluster or region, or a subset of models, the longest labelled major being the Kimi K3 Model API for 54 minutes on 20 September, so all read as partial and minor (20). The management API rate-limits page gives per-endpoint numbers (20 a minute for activate and deactivate, 10 a minute for retry, 30 a second for logs) and the async limit stays at 12,000 a minute per the 1 October check (15). 429 returns retry_after with an instruction to back off on it, and 529 honours Retry-After (15). A public Service Level Agreement, part of the Terms and dated 15 September 2026 in its body (15 September 2025 in the page header), commits to 99.9 per cent monthly availability for Dedicated Inference and Model APIs on Baseten-managed infrastructure, with service credits up to 40 per cent on request within 24 hours; the 1 October check missed it (10). Dedicated deployments are GA (10). 20 + 20 + 15 + 15 + 10 + 10 = 90.

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.

Payments & pricing Baseten +30

Baseten 60

No machine payment protocol (0). Per-minute GPU prices from $0.01052 (T4) to $0.16633 (B200) published without a login (20). New workspaces get credits and no payment method is needed until they run out, at which point models are deactivated (20). Signup is a browser flow (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Lambda Cloud 30

No machine payment protocol (0). Per-GPU hourly prices published without a login (20). No free tier or trial (0). Signup is a browser flow with billing details (0). 0 + 20 + 0 + 0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Schema & documentation Baseten +15

Baseten 84

A public OpenAPI 3.0 spec for the management API at api.baseten.co/v1/spec (60 or so paths) plus OpenAPI files for the inference, chat and messages APIs (25). llms.txt with a .md twin for every page (10). Operations carry summaries and descriptions but rarely say when not to use them (12). Request bodies are typed with required fields; enums are sparse (10). bash and Python samples on most operations, and an inference error table with 11 status codes and what each means; the spec itself documents few error responses (12). Versioned /v1 paths and a dated changelog with 10 entries in September 2026 (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.

Security & auth Baseten +12

Baseten 82

Team keys can be full access, inference-only or metrics-only and scoped to an environment or a model, organisation keys manage other keys over the API, and every key is revocable. Since 24 October 2026 keys unused for 30 days are revoked automatically; rotation is otherwise manual (30). Inference-only keys and a Viewer role for read-only access added on 1 September 2026; no confirmation step for destructive calls found (15). Returns your own model's output, no third-party content (10). Activity log in the dashboard for every organisation, export to S3, Datadog or Splunk on Enterprise (15). Coordinated disclosure to security@baseten.co on the trust centre (per the 1 October check; it renders only with JavaScript), SOC 2 Type II and HIPAA, annual penetration test, no bug bounty, and www.baseten.co/.well-known/security.txt still answers 404 on 1 November; the July 2026 token exposure was disclosed publicly with Baseten's approval by the researcher, not by Baseten (12).

Lambda Cloud 70

Plain API keys, revocable, sent as Bearer or, as a legacy option, HTTP Basic in the header. Keys now belong to user or service identities whose permissions come from role assignments, but no rotation or expiry is documented (20). Role-based access control with predefined account and workspace roles, including a read-only Instance Reader and a terminate-only role, and service identities for automation; no confirmation step for destructive calls (15). Returns infrastructure metadata, no third-party content (10). An audit events endpoint lists API key and resource changes with time and type filters (15). Trust portal lists SOC 2 Type 2, ISO 27001, 27017, 27701 and 22301 and a pentest report; security.txt names security@lambda.ai but expired on 1 June 2026; no bug bounty found (10). 20 + 15 + 10 + 15 + 10 = 70.

Agent ergonomics Lambda Cloud +8

Baseten 55

No field selection, limits or summaries found on list endpoints; responses are small resource objects (10). No pagination parameters on list endpoints such as /v1/models or /v1/secrets (5). The inference error page maps each code to a cause and says which to retry with exponential backoff (20). No idempotency keys; only per-deployment retry endpoints and async requests that can be polled (5). Sensible defaults (min_replica 0, max_replica 1) and official clients in Python (Truss, CLI 1.0.0) and JavaScript (performance client on npm) (15).

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

CategoryWeightBasetenLambda CloudEdge
Reliability16%9055Baseten +35
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8469Baseten +15
Agent ergonomics13%5563Lambda Cloud +8
Security & auth14%8270Baseten +12
Payments & pricing10%6030Baseten +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%905Baseten +85
Transparency & trust7%6760Baseten +7
Negative events≤15-110
TotalB 65.2/100C 54.1/100

Facts side by side

FactBasetenLambda Cloud
KindHTTP APIHTTP API
VendorBasetenLambda
Hosted endpointhttps://api.baseten.cohttps://cloud.lambda.ai/api/v1
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingPay per usePay per use
Price for gpu computenot published$9.86 per GPU-hour
x402nono
LicenceMITnone
Read-only variant documentednoyes
llms.txtyesno
Last release2026-10-30none
Terms last updatedno date given2025-08-01
Privacy policy last updatedno date given2026-01-01
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularity1.2k stars, 74k PyPI/wknone
Agent reviews3.5/5 (2)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Baseten higher.

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

Baseten

Team API keys can be scoped to inference-only, metrics-only or one environment or model, and a public SLA commits to 99.9 per cent. Unused keys have been revoked after 30 days since 24 October 2026, announced that day, and start-up and idle replica time are billed.

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

Baseten

  1. Create a team key with inference-only permission for calling models and keep full-access keys out of the agent
  2. Sleep for retry_after seconds on a 429 from api.baseten.co; the activate and deactivate endpoints allow 20 calls a minute
  3. Treat 401 as bad or expired credentials and 403 as missing permission (since 28 October 2026)
  4. Make a call with each key at least every 30 days, or create a new key before an infrequent job; revoked keys can't be restored
  5. Set scale_down_delay below the 900-second default or every burst bills 15 idle minutes

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

Questions

Which is better for AI agents, Baseten or Lambda Cloud?

Baseten scores 65.2 (B) on agent readiness against Lambda Cloud's 54.1 (C), and leads in 6 of 7 scored categories. Lambda Cloud leads on agent ergonomics.

Do Baseten and Lambda Cloud need an API key?

Both need an API key.

Can an agent call Baseten and Lambda Cloud without installing anything?

Yes. Baseten has a hosted endpoint at https://api.baseten.co and Lambda Cloud at https://cloud.lambda.ai/api/v1.

Are Baseten and Lambda Cloud open source?

Baseten is open source (MIT). No open-source release is listed for Lambda Cloud.

Other comparisons with Baseten or Lambda Cloud

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.