Rental models at a glance
All four models rent the same underlying marketplace capacity, the difference is how you pay for it and what guarantees come with each.
What you’re billed for
Every rental, regardless of model, has three cost components:- GPU compute, per-second while the instance is in a billable state. Varies by GPU model, count, reliability, and region.
- Storage, continuous while the instance exists, including when it is stopped. Delete the instance to stop storage billing.
- Bandwidth, per byte for both ingress and egress. Rates are host-set; check before picking data-intensive offers.
Choosing a model
I need guaranteed uptime
Use on-demand. Convert to reserved once you know you’ll run it for days or weeks, the discount is automatic from the instance card.
I can handle interruptions
Use interruptible. Checkpoint your work, save outputs to a volume or cloud storage, and set your bid based on how much priority you need.
My traffic is bursty
Use serverless. Define an endpoint with
min_workers: 0 and let the autoscaler recruit capacity only when requests arrive.I want to benchmark first
Spin up a short on-demand rental, record your throughput, then decide between reserved (steady workload) or serverless (variable workload).
Checking live prices
Prices move continuously. Always query current rates rather than relying on a quote:- Web, cloud.vast.ai/create shows real-time marketplace offers with filters for GPU, price, reliability, and location.
- CLI,
vastai search offersreturns matching offers as JSON. See the search-offers reference. - API, the search offers endpoint for programmatic access.
See also
- Instance pricing, full breakdown of on-demand, reserved, and interruptible
- Serverless pricing, worker and endpoint state billing tables
- Billing, credits, auto-billing, and payment methods
- Reserved instances, how to convert on-demand to reserved