Cloud GPU cluster
Lambda
Cloud GPUs and clusters aimed at ML teams that want familiar instance-style access with strong NVIDIA inventory.
Product facts checked October 2, 2026Editorial scores last reviewed September 3, 2026
Some outbound links use a first-party redirect hop for click counting. Commission is only claimed when a partner programme is active for that specific link — most vendor hops here are not paid placements. Affiliate disclosure.
Marketplace referrals (for example RunPod or Vast) may return credits or kickbacks when a programme is active — that is a material connection even when it is not a cash CPA.
Best for
Training and sustained inference on reserved or on-demand GPU instances
Watch out
Capacity and lead times depend on the selected cluster and contract. Lambda announced the closing of a $926M term loan B on August 27, 2026 for a committed customer deployment. That financing does not establish that a particular GPU SKU is currently available to other customers.
| Billing | On-demand instances priced hourly, billed in one-minute increments; 1-Click Clusters reserved and billed weekly; filesystems billed separately. |
|---|---|
| GPU choice | Datacenter NVIDIA focus |
| Cold start | Instance boot + your serving stack |
| Model access | Self-hosted models on Lambda GPUs |
Sources for the dated product and announcement claims
- Current product modes, billing and deployment documentation — source checked October 2, 2026
- Current product modes, billing and deployment documentation — source checked October 2, 2026
- Lambda August 27 loan closing — source checked October 2, 2026
Fit detail
When Lambda is the right shortlist — and when it is not
Use these lists to kill bad comparisons early, before you compare logos.
Ideal for
- Sustained training and inference on NVIDIA instances
- Teams that want cloud GPUs with familiar instance semantics
- Multi-GPU jobs that outgrow a single consumer rental
Usually not ideal for
- One-click managed chat APIs with no ops staff
- Tiny burst jobs that never keep a machine busy
- Spot-price hunting across random hosts
Spend & ops
How cost behaves — and what breaks first
No invented $/hour quotes. These notes explain the failure modes that show up on the first real invoice.
Cost mental model
On-demand billing begins after launch health checks and ends on termination, including idle allocated time. Cluster reservations have their own term. Filesystem charges track used GiB with hourly granularity and continue independently; the docs' $0.20/GiB-month example is illustrative, so use the creation screen's current rate.
Ops notes
- Terminate an on-demand instance through Lambda to end compute billing; shutting down its guest OS is not a termination.
- Back up instance data and retain only needed filesystems; filesystems keep billing while they exist, even when unmounted.
- Create and attach filesystems in the same region/workspace at instance launch; they cannot currently be attached to an already running instance.
Fit scores
Lambda on the decision axes
Same editorial scale as the hub chart — useful for shortlists, not as a price quote.
Lambda
- GPU choice8/10
- Time-to-serving (editorial)6/10
- Price clarity7/10
- Production ops7/10
- Open-model breadth7/10
Among all 16 providers
GPU choice
Pick exact GPUs
Time-to-serving (editorial)
Warm-path fit
Price clarity
Easy to forecast
Production ops
Less DIY ops
Open-model breadth
Catalog depth
Scores are editorial planning ratings (1–10) for product shape — not published $/hour quotes or vendor SLAs. Verify current pricing on each provider site.
Compare
Lambda vs alternatives
Open a head-to-head when you are deciding between product shapes.
Related
Keep the decision attached to the rest of the stack
Cloud rental is one path. Local VRAM and open-weight fit still matter.