Vultr

Authentication

Vultr uses a personal access token from My Vultr Settings. Click Add Personal Access Token, give it a name, and copy the key.

Field	Required	Description
api_key	Yes	Personal access token from Vultr settings

Configuration

providers:
  vultr:
    api_key: "${VULTR_API_KEY}"
    region: ewr
    image: "2284"
    size: vc2-2c-4gb

defaults:
  provider: vultr

Note: Vultr uses numeric OS IDs instead of name slugs for images. See the Images section below.

Regions

Vultr uses short airport-style codes:

Slug	Location
ewr	New Jersey, US
ord	Chicago, US
dfw	Dallas, US
sea	Seattle, US
lax	Los Angeles, US
atl	Atlanta, US
sjc	Silicon Valley, US
mia	Miami, US
ams	Amsterdam, NL
lhr	London, GB
fra	Frankfurt, DE
cdg	Paris, FR
sgp	Singapore, SG
nrt	Tokyo, JP
syd	Sydney, AU
yto	Toronto, CA
sao	Sao Paulo, BR

Run managed providers regions vultr to list all available regions.

Sizes

Vultr plans use the format vc2-{cores}c-{ram}gb:

Slug	Specs	$/mo
vc2-1c-1gb	1 vCPU, 1 GB RAM, 25 GB disk	$5
vc2-1c-2gb	1 vCPU, 2 GB RAM, 55 GB disk	$10
vc2-2c-2gb	2 vCPU, 2 GB RAM, 65 GB disk	$15
vc2-2c-4gb	2 vCPU, 4 GB RAM, 80 GB disk	$20
vc2-4c-8gb	4 vCPU, 8 GB RAM, 160 GB disk	$40
vc2-6c-16gb	6 vCPU, 16 GB RAM, 320 GB disk	$80

Run managed providers sizes vultr --region ewr to list all available plans in a region.

Images

Vultr uses numeric OS IDs. Common Ubuntu images:

ID	OS
2284	Ubuntu 24.04 LTS x64
1743	Ubuntu 22.04 LTS x64
2136	Debian 12 x64

Set the ID as a string in your config: image: "2284".

Auto storage

Vultr does not support auto-provisioned storage. Configure S3-compatible storage manually in managed.yaml if your services need backup storage:

storage:
  endpoint: "s3.us-east-1.amazonaws.com"
  region: "us-east-1"
  bucket: "my-backups"
  access_key: "${S3_ACCESS_KEY}"
  secret_key: "${S3_SECRET_KEY}"

Networking

Vultr assigns a public IPv4 and IPv6 address to each instance by default. For private networking between instances, attach them to a Vultr VPC in the same region.