Vultr VX1™

Vultr VX1™ delivers industry-leading price-performance and boasts up to 77% better performance per dollar when compared to leading hyperscaler performance-per-dollar focused compute plans. This makes VX1 an exceptionally good fit for cloud-native workloads where total cost efficiency takes priority.

VX1 instances also support booting from Vultr Block Storage. This offers data durability, encryption at rest (AES-256), and infinite scale-up with support for live resizing of volumes. Boot volumes are backed by Vultr's highest performing NVMe Block Storage tier, and come with provisioned IOPS (10k) and throughput (400 MB/s) allowing up to 60-second bursts of 15k IOPS and 600 MB/s throughput. VX1 instances can also be paired with local NVMe for high performance local scratch.

Key Features

Boot from High Performance Vultr Block Storage with locally attached NVMe
Fastest cloud compute networking yet with up to 15 Gbps for the smallest VX1 plans and scaling up to 50 Gbps, fully dedicated
Instant provisioning and ready for use in seconds
Dedicated CPU resources ensuring predictable performance over time even under the heaviest workloads
Supports additional CPU features including support for virtualization

VX1 Cloud Compute Plan Types

General Purpose (vx1-g-) - General purpose compute and memory resources for a variety of workloads
Memory Optimized (vx1-m-) - Increased memory capacity for memory-intensive applications

Note

All VX1 plans ending with -###s, for example vx1-g-4c-16g-240s, come with local NVMe where the ### represents the size of the provisioned local NVMe volume. You can opt for plans without local storage and boot from Vultr Block Storage by finding plans without the ###s suffix, for example vx1-g-4c-16g.

VX1 Cloud Compute Deployment Options

Local NVMe - Ideal for workloads that require low-latency access to data and can tolerate data loss in the event of a disk failure.
Block Storage - Suitable for applications that require persistent storage and can benefit from the flexibility of block storage volumes including data durability, encryption at rest (AES-256), and live resizing.
Local NVMe and Block Storage - Provides the best of both worlds with durable block storage and fast local NVMe scratch.

Customer Portal Deployment

To deploy VX1 from the Vultr Customer Portal, select Deploy > Dedicated CPU > VX1 and select New York (NY) for the location. You can select either Block Storage or Local NVMe option and configure storage on the second step before deploying.

API Deployment with Local NVMe

VX1 Cloud Compute plans support using local NVMe as the bootable disk. Please note that deleting an instance with local disk will result in permanent data loss. This requires you to back up any important data before deleting the instance.

Create a new VX1 instance with local disk storage.

Option A - Basic local boot (bootable parameter not required):

                            console
                            
                        
$ curl --location 'https://api.vultr.com/v2/instances' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer VULTR_API_KEY' \
--data '{
   "region": "ewr",
   "plan": "vx1-g-4c-16g-240s",
   "label": "VX1 Local Disk Only",
   "hostname": "vx1-localonly-1",
   "os_id": 2284
}'

Option B - Explicit local boot configuration:

                            console
                            
                        
$ curl --location 'https://api.vultr.com/v2/instances' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer VULTR_API_KEY' \
--data '{
   "region": "ewr",
   "plan": "vx1-g-4c-16g-240s",
   "label": "VX1 Local Disk Only - Bootable",
   "hostname": "vx1-localonly-2",
   "os_id": 2284,
   "block_devices": [
      {
         "block_id": "local",
         "bootable": true
      }
   ]
}'

Note: Ensure you select a plan with the -###s suffix (e.g., vx1-g-4c-16g-240s) to include local storage.

Deploy VX1 Cloud Compute with Block Storage

VX1 Cloud Compute plans without local disk support must use block storage for the bootable disk. This configuration provides persistent storage and data durability. This would ensure that your data remains intact even if the VM is stopped or deleted.

Create a new bootable block storage volume.

Send a POST request to create the bootable block:

                            console
                            
                        
$ curl --location 'https://api.vultr.com/v2/blocks' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer VULTR_API_KEY' \
--data '{
   "region": "ewr",
   "size_gb": 50,
   "label": "Bootable Block",
   "block_type": "high_perf",
   "os_id": 2284,
   "bootable": true
}'

Important: The block_type must be set to high_perf for bootable block devices.

Create a new VX1 instance using the bootable block storage volume.

Option A - Using a newly created bootable block:

                            console
                            
                        
$ curl --location 'https://api.vultr.com/v2/instances' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer VULTR_API_KEY' \
--data '{
   "region": "ewr",
   "plan": "vx1-g-4c-16g",
   "label": "vx1-blockonly-new-boot-block-1",
   "hostname": "vx1-blockonly-new-boot-block-1",
   "os_id": 2284,
   "block_devices": [
      {
         "disk_size": 50,
         "label": "New Bootable Block",
         "bootable": true
      }
   ]
}'

Option B - Using an existing bootable block:

                            console
                            
                        
$ curl --location 'https://api.vultr.com/v2/instances' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer VULTR_API_KEY' \
--data '{
   "region": "ewr",
   "plan": "vx1-g-4c-16g",
   "label": "vx1-blockonly-existing-boot-block-1",
   "hostname": "vx1-blockonly-existing-boot-block-1",
   "os_id": 2284,
   "block_devices": [
      {
         "block_id": "BLOCK_UUID",
         "bootable": true
      }
   ]
}'

Replace BLOCK_UUID with the UUID of your existing bootable block device.

Deploy VX1 Cloud Compute with Local Disk and Block Storage

VX1 Cloud Compute plans that support both local and block storage can take advantage of the benefits of each storage type. We recommend using a bootable block storage volume for the operating system and local disk storage for temporary data. This would allow for faster access to frequently used files while still providing the durability of block storage for your operating system and any application files.

Create a new bootable block storage volume.

Send a POST request to create the bootable block:

                            console
                            
                        
$ curl --location 'https://api.vultr.com/v2/blocks' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer YOUR_API_KEY' \
--data '{
   "region": "ewr",
   "size_gb": 50,
   "label": "Bootable Block",
   "block_type": "high_perf",
   "os_id": 2284,
   "bootable": true
}'

Create a new VX1 instance with both bootable block storage and local disk.

Option A - Using a newly created bootable block with local storage:

                            console
                            
                        
$ curl --location 'https://api.vultr.com/v2/instances' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer YOUR_API_KEY' \
--data '{
   "region": "ewr",
   "plan": "vx1-g-4c-16g-240s",
   "label": "vx1-new-boot-block-plus-local-1",
   "hostname": "vx1-new-boot-block-plus-local-1",
   "os_id": 2284,
   "block_devices": [
      {
         "disk_size": 50,
         "label": "New Bootable Block",
         "bootable": true
      },
      {
         "block_id": "local"
      }
   ]
}'

Option B - Using an existing bootable block with local storage:

                            console
                            
                        
$ curl --location 'https://api.vultr.com/v2/instances' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer YOUR_API_KEY' \
--data '{
   "region": "ewr",
   "plan": "vx1-g-4c-16g-240s",
   "label": "vx1-existing-boot-block-plus-local-1",
   "hostname": "vx1-existing-boot-block-plus-local-1",
   "os_id": 2284,
   "block_devices": [
      {
         "block_id": "local"
      },
      {
         "block_id": "BLOCK_UUID",
         "bootable": true
      }
   ]
}'

Replace BLOCK_UUID with the UUID of your existing bootable block device.

Note: The local storage disk must be formatted and mounted manually within your operating system after instance creation.

Additional Notes

Automated Backups are currently disabled for VX1 instances
Windows OS is currently not available for VX1 instances
Block Type must be high_perf for bootable block devices
Currently available in New Jersey (ewr) with expansion regions coming soon. Please contact us if you'd like us to consider a specific region.

Tags:

Vultr Compute

Vultr VX1™ - Cloud Compute

Vultr VX1™

Key Features

VX1 Cloud Compute Plan Types

VX1 Cloud Compute Deployment Options

Customer Portal Deployment

API Deployment with Local NVMe

Deploy VX1 Cloud Compute with Block Storage

Deploy VX1 Cloud Compute with Local Disk and Block Storage

Additional Notes

Comments

Products

Features

Solutions

Marketplace

Resources

Company

Tech Talks

Vultr Blogs