Virtualization From Pro
Install systems, allocate IPs, open consoles, take snapshots, power VMs on and off, back up and restore — next to the websites, storage and networking they serve. Nodekeeper connects to your hypervisors; it does not pretend they are all the same, so this page lists what has been verified for each one.
On this page: Per-backend matrix · VM lifecycle · Where Nodekeeper runs · Storage and HA · Plans
KVM / ESXi / PVE management from one panel. The rows below are the workflows we have tested per backend.
| Workflow | KVM | Proxmox VE | VMware ESXi |
|---|---|---|---|
| Automatic OS install | Windows (18 versions on x86_64, 6 on aarch64), Linux (23 distributions on x86_64, 13 on aarch64), custom ISO | Reinstall verified (LXC containers) | One-click provisioning, unattended Windows install, EFI network boot |
| Automatic IP allocation | — | IP pool | IP guard |
| Web console | ✓ | ✓ | ✓ |
| Snapshots | ✓ | ✓ (multi-disk group snapshots for HA VMs on distributed storage) | ✓ |
| Rescue system | ✓ | ✓ | ✓ |
| Port forwarding, traffic limits | ✓ | — | — |
| USB / GPU / disk passthrough | GPU, whole-disk passthrough | GPU, USB, disk | GPU, disk (RDM), USB auto-connect |
| System disk on distributed storage From Business | ✓ | ✓ | ✓ (NVMe/TCP) |
| High-availability failover From Business | ✓ | ✓ (VMs) | not supported |
— = not in the verified list for that backend yet. Ask us before relying on it. The rescue system boots into memory and never wipes the customer disk; passthrough needs IOMMU / VT-d on the host and is assigned by administrators only. Rescue system
Pick an image or your own ISO, size and network; Nodekeeper installs the system and assigns the address where the backend supports it.
VM power, backup and restore, web console, snapshots, port forwarding and traffic limits — with the same permission checks and operation log as the rest of the panel.
Assign a VM to a member account; the member manages only their own machines. Selling VMs through WHMCS is described on the hosting providers page.
DD in-place reinstall rewrites a whole server from a disk image — available on every plan, Free included.
The panel talks to KVM hosts, Proxmox VE or ESXi and drives the workflows above.
Nodekeeper itself can run inside a VM on ESXi or Proxmox VE, and it also runs natively on ESXi 7, 8 and 9 as a VIB package. That native ESXi build is a dedicated port; it does not mean any Linux program runs on ESXi.
How licences are counted when Nodekeeper runs both on a host and inside its guests: ask us before you plan it.
With Business, KVM and Proxmox VE VM disks can live on distributed storage managed by the same panel, and a VM on a failed host is restarted on another host with the same IP and MAC. It is a cold restart, not live migration.
High availability: prerequisites and measured times · Distributed storage
| From plan | Virtualization |
|---|---|
| Free | DD-image reinstall of a server |
| Pro | KVM, Proxmox VE and ESXi management: install, IP allocation, console, snapshots, power, backup and restore |
| Business | VM disks on distributed storage, restart on another host after a failure |
The trial is a monthly subscription whose first month is $0: card required, once per account; cancel before day 30 and you are not charged.