DigitalOcean

GPU types

GPU type	VRAM	Architecture	GPUs available	Regions
`H100-80GB`	80 GB	NVIDIA Hopper	1 or 8	tor1, nyc2
`H200-141GB`	141 GB	NVIDIA Hopper	1	atl1, nyc2

DigitalOcean sells fixed droplet shapes only: a gpu_count of 2 or 4 is rejected at submit, and the H200 is single-GPU. The H200’s 141 GB fits a full-parameter fine-tune of a 7B to 8B model, or LoRA on 30B-class models, on one GPU.

Submitting a job

job = client.training_jobs.create(
    base_model="Qwen/Qwen2.5-0.5B-Instruct",
    dataset_id=dataset.id,
    method="sft_text",
    output_name="qwen-do-sft",
    gpu_type="H200-141GB",
    gpu_count=1,
    provider="digitalocean",
)

veri jobs create train.toml --gpu-type H200-141GB --gpu-count 1 --set provider.name=digitalocean

Notes

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. AMD MI300X training is not yet available on any provider.

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.

veri gpu list --provider digitalocean shows 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.

Get started

Training

Deployments

Evaluations

Agents

CLI

Volumes

Webhooks

Secrets

Billing

GPU types

Submitting a job

Notes

Where to go next

All providers

SFT (text)

​GPU types

​Submitting a job

​Notes

​Where to go next

All providers

SFT (text)

GPU types

Submitting a job

Notes

Where to go next