GPU marketplace
RunPod
Rent individual GPUs or pods by the hour, with community and secure cloud options for training and inference workloads.
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
Teams that want to pick a specific GPU SKU and control the container stack
Watch out
You still own ops: images, scaling, and idle spend. Stopping a pod is not the same as terminating it — stopped storage can keep billing until you tear the volume down.
| Billing | Per-second / per-hour GPU rental |
|---|---|
| GPU choice | Broad consumer and datacenter SKUs |
| Cold start | Depends on pod spin-up and image cache |
| Model access | Bring your own weights or pull from registries |
Fit detail
When RunPod is the right shortlist — and when it is not
Use these lists to kill bad comparisons early, before you compare logos.
Ideal for
- Picking a specific consumer or datacenter GPU SKU
- Self-hosted vLLM / TGI / Comfy stacks you already trust
- Burst experiments that still need SSH-level control
Usually not ideal for
- Shipping a chat API tomorrow with no container skills
- Teams that cannot monitor idle pods overnight
- Strict multi-region SLAs without your own ops layer
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
You pay for hardware time whether tokens are flowing or not. Great when utilization is high; expensive when pods sit warm “just in case.”
Ops notes
- Stop ≠ terminate — tear down volumes when the experiment ends or storage keeps billing
- Stop or autoscale pods — idle rental is the common bill shock
- Cache images in the region you actually serve from
- Separate community vs secure cloud for anything customer-facing
Fit scores
RunPod on the decision axes
Same editorial scale as the hub chart — useful for shortlists, not as a price quote.
- GPU choice9/10
- Time-to-serving (editorial)6/10
- Price clarity8/10
- Production ops6/10
- Open-model breadth8/10
Among all 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
RunPod 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.