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 use a separate prepaid invoice and can’t be paid with VESSL Cloud credits. See Pricing and 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.
4 to 52 weeks. For longer terms, talk to sales.
No. Place a new order for a different configuration, or talk to sales if you need help with a custom setup.
No. To switch payment methods, cancel the current order and place a new one.
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.
These configurations go through a separate process — talk to sales for a consultation to scope and provision the cluster. Once it’s enabled in your VM clusters dashboard, you manage it the same way as any self-service cluster.
No. The node count is fixed for the contract term — if you need more capacity mid-contract, place a new order or talk to sales.