Skip to main content
VMs recover quickly from hardware failures by migrating to a new physical host. You still get GPU passthrough performance and can run root-level operations through sudo. For bare-metal requirements, talk to sales.
No. VM clusters are billed separately from VESSL Cloud and can’t be paid with VESSL Cloud credits. Your account manager handles billing.
Not yet — managed Kubernetes and Slurm are on our roadmap. In the meantime, you can install your own orchestrator (Kubernetes, Slurm, or anything else) on the cluster yourself, since you can run root-level operations through sudo.
Contract length is agreed with sales when you request a cluster. Talk to us for the terms you need.
No. To change your configuration, talk to sales and we’ll scope a new cluster.
No. To change your payment method, talk to your account manager.
No. All data is deleted immediately at expiry, with no grace period. Back up before the expiry date — see Data retention and expiry.
Reboots typically take tens of minutes, and can run past an hour in some cases. See Reboot a node.
You manage authorized keys directly on each node. Because you have root, you can add a new public key to ~/.ssh/authorized_keys. If you’ve lost access to the node entirely, contact support.
Yes. You have root access, so you can change drivers and kernel modules.
Yes. You have root on the VM itself, so any container runtime you install — Docker, containerd, Kubernetes — can run containers with --privileged, custom capabilities, raw device mounts, or anything else that needs host-level access.
Yes — InfiniBand is provided by default on all nodes for multi-node communication.
H100 through the latest Blackwell GPUs (H100, H200, B200, B300), in multi-node clusters sized to your workload. Talk to sales to scope and provision your cluster. Once it’s set up, you can manage it from the VM clusters dashboard.
No. The node count is fixed for the contract term. If you need more capacity, talk to sales.