Proxmox VE 9 on a VPS, with nested KVM.
Your own Proxmox VE node on hardware we own and operate in Durham, NC — installed, networked and checked for you, with VMs running hardware-accelerated inside it. For home-labs, cert study and testing.
- From $14.50/mo
- 4 GB RAM minimum, 8 GB recommended
- Ready in about 8–12 minutes
- Month-to-month
A node that works the first time you log in
Real Proxmox VE 9
Installed the supported way — Proxmox VE on Debian 13 — with the web interface on port 8006 and full root access. Not a template; your own node.
Nested KVM that is actually fast
Hardware virtualization is passed through, so your VMs run hardware-accelerated, not in software emulation. We checked a nested VM holding /dev/kvm before we sold this.
Networking ready on day one
vmbr0 carries your server’s address and a vmbr1 NAT bridge (192.168.100.0/24) is already set up, so a new VM reaches the internet straight away.
Checked before you get it
Provisioning only finishes after a 15-point check passes: PVE kernel, cluster services, web UI, bridges, storage, /dev/kvm, DNS and a clean package state. If any check fails, the order is flagged to us instead of being handed to you.
Pay for the CPU, memory and storage you choose
$3.50 per vCPU, $2.50 per GB of RAM and $0.05 per GB of storage, per month. A few starting points:
| Size | vCPU / RAM / Disk | Port speed | Per month | Good for |
|---|---|---|---|---|
| Lab | 2 / 4 GB / 60 GB | 250 Mbps | $20 | Learning Proxmox, one or two small Linux VMs or containers. |
| Recommended | 4 / 8 GB / 120 GB | 400 Mbps | $40 | A handful of small VMs — a home-lab or study environment. |
| Largest | 12 / 12 GB / 200 GB | 500 Mbps | $82 | Our biggest plan: realistically 2–4 small VMs alongside Proxmox itself. |
The limits, plainly
A Proxmox node on a VPS is not a dedicated server. These are the trade-offs.
- VMs inside your node don’t get public IPs. Your VPS has one public IPv4 address. VMs sit behind the vmbr1 NAT bridge and you reach them with port forwards — our guide shows how.
- IPv4 only. The node is set up with IPv4; IPv6 isn’t configured on Proxmox VE nodes.
- No ZFS or LVM-thin. Your node has a single virtual disk, so VM disks live on directory storage on it. No thin provisioning.
- At most 12 GB of RAM. Proxmox itself uses about 1.5 GB, so plan on 2–4 small VMs. 4 GB is the minimum we sell; 8 GB is what we recommend.
- Disks can grow, not shrink. You can add storage later; you can’t take it back.
- Snapshots are a hard stop. A Piedmont snapshot of a running VPS ends with a forced power-off and restart — that hard-stops every VM inside. Shut your VMs down first, or use Proxmox’s own backups.
- No App Marketplace. Our one-click Docker apps are switched off for Proxmox nodes — run them inside a VM or container instead.
- No Proxmox subscription. Your node uses Proxmox’s free no-subscription repository, so the web UI shows Proxmox’s standard “no valid subscription” notice. You can buy a Proxmox subscription yourself if you want enterprise updates.
How we built it — and how to use it
Questions
How long does setup take?
About 8–12 minutes from payment to login. We build a Debian 13 server, convert it to Proxmox VE with two reboots, then run the 15-point check before it is marked ready and you are emailed.
How do I log in?
Open https://your-ip:8006 and sign in as root (realm “Linux PAM”) with the root password you set at checkout — Proxmox orders require one for exactly this reason. The web UI uses Proxmox’s own self-signed certificate, so your browser shows a warning the first time.
Can I run Windows VMs?
Yes — nested KVM runs Windows guests. Our own Proxmox VE VPS runs a Windows Server 2025 VM. You bring the Windows license, and memory is the limit to plan around.
Can I upload my own ISOs and templates?
Yes. The local storage accepts ISO images, container templates, VM disks and backups.
Which firewall ports do I need?
Apply the Proxmox VE Node preset on the Cloud Firewall tab: it opens SSH (22), the web UI (8006), SPICE (3128), the noVNC console range (5900–5999) and ping. Add a rule for every port you forward to a VM.
Is the bandwidth metered?
No. Transfer is unmetered; each plan has a port speed set by its RAM, shown in the table above.
Can I get more public IPv4 addresses?
Not at the moment. VMs reach the internet through the NAT bridge, and inbound traffic arrives through port forwards on your one address.