Skip to main content
Deployments run on AWS by default, or on DigitalOcean for single-GPU H100 and H200. The provider field defaults to aws, so you can leave it out. Capacity errors don’t spill to another cloud: retry later or pick another GPU shape.

Providers at a glance

Each provider sells fixed node shapes. The gpu_count you request must match one of the counts above — asking for a shape a provider doesn’t sell returns a 400 at create, before anything boots.
Other serving providers are not available yet: a create with any other provider returns 400 with Serving provider '<provider>' is not currently enabled.

Choosing a provider

Omit provider to use the default (AWS).

Checking providers from the CLI

The live version of the matrix above (including current prices) is one command:
This renders the GPU catalog: one row per (GPU type, provider) with a training and a serving column: the node counts you can order for each workload (- = not offered, (soon) = not available yet) and the per-GPU $/hr. Any filter switches to the live availability view:
In that view, a status of AVAILABLE is a live signal (DigitalOcean per-region catalog, Vast offers); OFFERED (AWS) is catalog plus a Spot placement-score proxy, not a launch guarantee.

Provider guides

AWS (default)

L4/A10G single GPUs and whole-node A100/H100.

Where to go next

Hosting & GPU sizing

Pick the right GPU for your model size; cold-start expectations.

Billing

Billing states and the idle-stop warning.