Skip to main content
Veri runs training jobs on four GPU providers. You pick one at job submit time with the provider field. Each provider offers different GPU types at different price points — AWS is the default, Hot Aisle is the AMD beachhead, Vast.ai is the NVIDIA marketplace spillover, and DigitalOcean offers single-GPU H100 droplets with per-second billing.

Providers at a glance

All providers except AWS are gated behind feature flags that may be off in your environment. If a provider is disabled, submit returns a “coming soon” 400. Run veri gpu list to see which providers are live.

Choosing a provider

Pass provider when creating a training job:
From the CLI:
Or in a TOML config:
Omit provider to use the default (AWS).

Checking live availability

Capacity is per-provider and per-region. Check what’s available right now before submitting:
The available column shows live capacity: a real-time count of GPUs that can be launched immediately. 0 means the shape is offered but currently out of stock — retry later.
DigitalOcean rows show one AVAILABLE entry per region with current capacity, or a single UNAVAILABLE row when a shape has no capacity anywhere. This signal comes from DigitalOcean’s size catalog, which can lag real launch acceptance in both directions — a submit may still succeed after the launcher retries across regions, or miss capacity the catalog listed moments earlier.

AWS (default)

AWS is the default provider and the most reliable for NVIDIA training. It offers four GPU types: L4 and A10G are single-GPU instances — you rent one card. A100 and H100 are whole 8-GPU nodes: you get (and pay for) all 8 cards regardless of gpu_count, which controls how many are used for training, not how many are rented.

Hot Aisle (AMD MI300X)

Hot Aisle is a neocloud offering single- and multi-GPU AMD MI300X VMs. The MI300X has 192 GB of HBM3 memory — more than any NVIDIA single-GPU offering — making it well-suited for large-model finetuning on a single card.
Hot Aisle VMs run ROCm, not CUDA. The training stack (torch, transformers, TRL) is installed from the ROCm wheel index at boot. Unsloth, bitsandbytes, xformers, and vLLM are CUDA-only and are not available on this provider. Vanilla TRL training (GRPO, SFT, DPO) is fully supported.

Cold-start behavior

Hot Aisle VMs boot from a stock image and install the ROCm training stack at boot via cloud-init. The first boot includes:
  1. ROCm driver verification (rocm-smi)
  2. PyTorch ROCm wheel installation (torch 2.9.1 from the ROCm 6.4 index)
  3. Training stack install (transformers, accelerate, peft, TRL)
  4. GPU sanity gate (SA5_ROCM_OK — torch must see the AMD GPU)
Cold-start time depends on Hot Aisle’s VM provisioning and network throughput. If the cloud-init path is slow, a prebuilt ROCm worker container may be used in the future to reduce boot time.

Supported training methods

All managed training methods work on Hot Aisle: grpo, sft_text, dpo, and sft_video_gen. The grpo_agentic method is unavailable on all providers (the agentic engine is being rebuilt).
use_unsloth and load_in_4bit (QLoRA) are not supported on Hot Aisle — both depend on CUDA-only libraries. Set them to false (the default) when using provider="hotaisle".

Vast.ai (NVIDIA marketplace)

Vast.ai is a GPU marketplace that rents per-host NVIDIA chunks (1-8 GPUs within a single machine). It serves as a capacity spillover when AWS is out of A100 or H100 stock.
Vast.ai rents individual GPU cards on shared hosts, so gpu_count=1 rents exactly one GPU (unlike AWS where A100/H100 are whole 8-GPU nodes). Availability and pricing vary by host and fluctuate in real time.

DigitalOcean (H100)

DigitalOcean GPU Droplets are on-demand single- and 8-GPU VMs with per-second billing and fast (about one minute) provisioning. DigitalOcean sells fixed 1x and 8x droplet shapes only — a gpu_count of 2 or 4 is rejected at submit.
DigitalOcean also lists AMD MI300X droplets, but they are not yet enabled on Veri — a provider="digitalocean" submit with gpu_type="MI300X-192GB" returns a 400 listing the offered shapes. For AMD MI300X training today, use provider="hotaisle".
DigitalOcean GPU capacity fluctuates minute-to-minute. A submit that hits CAPACITY_UNAVAILABLE after retrying across regions is not billed — check veri gpu list --provider digitalocean and retry.

Pricing

Each provider has its own rate card. Check current pricing with:
Rates are per-GPU-hour. You are billed from when the GPU is provisioned (provisioning state) until the job terminates and the instance is reaped. A job that never secures a GPU (e.g. CAPACITY_UNAVAILABLE) is not billed.

Where to go next

Managed training

How the training loop works across all providers.

GRPO algorithm

The default RL method — works on all providers.

Check live availability

veri gpu list shows real-time capacity per provider.

Regions

Launch in a specific AWS region for lower latency or capacity.