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, Vast.ai is the NVIDIA marketplace spillover, DigitalOcean offers single-GPU H100 droplets with per-second billing, and Hot Aisle (AMD MI300X) is coming soon.

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.

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.

Provider guides

AWS (default)

L4, A10G, and whole-node A100/H100 — the reliable NVIDIA default.

Hot Aisle (AMD MI300X)

192 GB HBM3 per card, the ROCm stack, and MI300X performance tuning.

Vast.ai

Marketplace A100/H100 spillover at fluctuating prices.

DigitalOcean

Fast-provisioning 1x/8x H100 droplets with per-second billing.

Where to go next

Managed training

How the training loop works across all providers.

GRPO algorithm

The default RL method — works on all providers.