Virtualization
Order a Proxmox dedicated server with Proxmox VE 9 installed in one click, typically online in about 10 minutes, then run KVM virtual machines and LXC containers on EPYC cores.
Choose Proxmox VE 9 when you order and the host comes up ready for its web interface on port 8006, or install any hypervisor from ISO.
Up to 32 EPYC cores and 384 GB of ECC RAM in stock, with no other hypervisor beneath yours and no steal time from other tenants.
Add IPv4 addresses routed to the host for your VMs, and give every guest native IPv6 from the included /64, or a /56 on request.
A wrong vmbr0 edit can cut SSH; the browser-based KVM console still reaches the host, and virtual media mounts any ISO.
Recommended servers
From a first deployment to a busy production setup. Live stock and prices; in-stock picks are online in minutes.
Homelab or small cluster node
12C / 24T · 3.7–5.4 GHz
12 cores up to 5.4 GHz and 128 GB DDR5 ECC: a dozen or two mid-size VMs on mirrored NVMe, with high clocks for Windows and desktop guests.
Our pickProduction VM host
24C / 48T · 2.85–4.0 GHz
24 cores, 256 GB ECC and 2 × 3.84 TB NVMe on a 10 Gbps port: room for dozens of VMs, with fast backup and migration traffic.
Dense host or private cloud
32C / 64T · 3.25–3.8 GHz
32 Zen 4 cores and 384 GB of 12-channel DDR5 ECC to consolidate many workloads, with 10 Gbps for storage, backups and live migration.
Sizing
VM counts and overcommit ratios are planning rules of thumb, not measurements; give databases and CPU-bound guests 1:1 vCPUs, and avoid overcommitting RAM on a ZFS host.
| Workload | Typical need | Suggested plan |
|---|---|---|
| Homelab or dev lab, 10–20 small VMs | 2–4 GB RAM each; vCPUs overcommitted 3–4:1 | AMD EPYC 4464P |
| LXC containers for web apps | Shared kernel, little overhead; RAM is the limit | AMD EPYC 4464P |
| Production VMs for 20–30 services | 4–8 GB each; vCPU ratio near 2:1 for steady loads | AMD EPYC 7443P |
| Kubernetes on VMs (k3s, Talos) | Fixed-RAM worker VMs; fast local NVMe for etcd | AMD EPYC 7443P |
| Private cloud, 50+ mixed VMs | Many cores, 384 GB of RAM, 10 Gbps for migrations | AMD EPYC 9354P |
| Proxmox Backup Server datastore | Capacity and dedup, ideally in another location | 64 TB Storage Server |
Expert notes
Short, practical advice from our engineers for this workload.
Additional IPv4 addresses are routed to your server’s main IP, so the Proxmox host acts as the router for its guests instead of bridging them straight onto the uplink:
vmbr0, bridged to the physical NIC.vmbr1 with no physical port, give it the host’s main IP as a /32, and enable net.ipv4.ip_forward=1.up lines, for example ip route add 203.0.113.50/32 dev vmbr1.For IPv6, put an address from your /64 on vmbr1, enable net.ipv6.conf.all.forwarding=1 and keep the host’s IPv6 gateway static (fe80::1; check the value in your dashboard). Ask for the free /56 if you want one /64 per bridge or tenant. The Proxmox network documentation covers each mode in detail.
Two NVMe drives can back your guests in two common ways:
zfs_arc_max so guests keep theirs.For a ZFS mirror, install Proxmox VE from the official ISO through IPMI virtual media and choose ZFS RAID1 in the installer; our Proxmox guide walks through it. Give guests VirtIO SCSI disks with discard enabled, so thin volumes reclaim space when guests trim.
Back up guests to Proxmox Backup Server 4, itself a one-click OS, ideally on a 64 TB Storage Server in another location. PBS deduplicates across all guests, reads only the changed blocks of running VMs thanks to dirty bitmaps, and supports client-side encryption, leaving the datastore with ciphertext only.
Root access means you install exactly what you need. These are proven choices for this workload.
FAQ
Either way works. Pick Proxmox VE 9 as the operating system when you order and the host typically comes online in about 10 minutes, ready for the web interface on port 8006. For a custom disk layout such as a ZFS mirror, mount the official ISO through the IPMI console and run the installer yourself. Proxmox subscriptions are optional and bought from Proxmox.
Order additional IPv4 addresses for the server: up to four without justification, and /29 or /28 blocks with one. They are routed to your main IP, so you configure the Proxmox host as a router and point guests at it. For IPv6, every server includes a routed /64, and a /56 is free on request if you want a separate /64 per bridge or tenant.
Yes, from a custom ISO mounted through IPMI virtual media, with your own license. ESXi only supports specific network and storage controllers, so ask us which servers match before you order; desktop-class platforms are the most likely to lack drivers. Proxmox VE and Windows Server with Hyper-V install in one click instead, and any one-click Linux distribution can run plain KVM.
Yes, within one location. Order the nodes in the same city, request the free private VLAN for Corosync and migration traffic, and plan three nodes, or two plus a QDevice, so the cluster keeps quorum. Stretching one cluster across cities is not a good idea: to keep copies elsewhere, use Proxmox Backup Server and its sync jobs to another location.
Yes. The Windows Server license we offer covers Windows installed directly on the server, billed per physical core. Windows guests inside Proxmox or KVM need their own licensing, arranged with Microsoft or a reseller. Linux guests such as Ubuntu, Debian, AlmaLinux and Rocky Linux carry no license cost, and a cloud-init template makes them quick to clone.
Pick one of the recommended in-stock servers and it can be online in minutes. Need something bigger or different? Our engineers quote custom builds within one business day.