Proxmox dedicated servers, delivered running.

Preinstalled. Select Proxmox VE 9 as the operating system on the order form and the machine is built unattended with Proxmox's own installer, image 9.2-1, with the hostname you typed and the root password you chose. The email that closes the build carries the addresses, the username root and the password; the web console is at https://your-address:8006. On the blade lines the HPE iLO console is there too, so an installation from an ISO of your own is possible, but nobody needs it to get started.

Image 9.2-1, which is Proxmox VE 9.2 on Debian 13, released by Proxmox on 21 May 2026. It updates through apt like any Debian system; which repository it updates from is the subscription question below. Older releases are not offered.

No. Proxmox VE is free software under the AGPL v3, and we charge nothing for installing it. A subscription buys access to the enterprise package repository and, from the Basic tier up, support from Proxmox. Proxmox lists the Community tier at 120 euros per CPU socket per year, Basic at 370, Standard at 550 and Premium at 1,100, net of VAT, and says the no-subscription repository is fine for testing but not recommended for production. It is per socket, so a single-socket blade needs one, a four-socket machine needs four. We do not resell subscriptions; buy the key from Proxmox and enter it in the web console.

One IPv4 comes with the server. On the Scalable and four-socket lines you can add two more for $6 a month, four for $18, six for $30 or eight for $42; the entry blade and the cartridges take two more for $6. Additional addresses are allocated from the same /24 as your primary and delivered to the same port, so you can bridge them, one address and one MAC per guest on vmbr0, or route them through the host with the host as the guests' gateway. There is no MAC registration form on our side. For more guests than addresses, route: any number of machines can sit behind one address with NAT on the host. One or two IPv6 addresses are included on most lines; they are individual addresses, not a /64, and you add them on the host yourself.

Depends on the line, and both are set up before you log in. The ProLiant blade lines carry a Smart Array controller with a battery-backed write cache, so the installer puts ext4 on a RAID 1 logical drive and Proxmox's LVM-thin holds the guests; Proxmox's own documentation says not to put ZFS on top of a RAID controller, and we do not. The NVMe cartridge lines, m510, m710x and m750, have no RAID card, so a two-disk order arrives as a ZFS mirror built by the installer, and any extra software-RAID set is created as a ZFS pool already registered as Proxmox storage. Want snapshots and replication at the filesystem: take a cartridge. Want hot-swap bays and the write cache: take a blade.

Yes, with three or more nodes: Proxmox needs three votes for a reliable quorum, or two nodes and a QDevice, and under 5 milliseconds between them. Put the nodes in the same room and they meet that. Corosync, migration and Ceph traffic crosses each server's public port, because we do not sell a private VLAN, so use the built-in firewall and Proxmox's encrypted migration. Ceph wants three nodes and a fast link; a 10 Gbps port is $529 a month on the lines that offer it. High availability additionally needs storage every node can reach.

Wherever you point them. The simplest layout is a second machine running Proxmox Backup Server: the $72.35 cartridge with two NVMe disks is enough for a small estate, and backups then leave the host that could fail. vzdump to the local disks works from day one and is what a single-host lab usually does. Inbound traffic to any of our servers is not billed, so restoring is free at any size.

You will not need it. This is bare metal: KVM runs straight on Intel VT-x with EPT, so Windows guests, Docker in a guest and Kubernetes nodes all run as first-level virtual machines. Nesting is only for running a hypervisor inside a guest; it works on these processors if you enable it, and Proxmox notes that a guest with nesting switched on cannot be live-migrated.

Proxmox VE has had an ESXi import wizard since release 8.2 in April 2024. It connects to an ESXi host or vCenter, lists the guests and imports them with their settings, and can start a guest while its disks are still copying. Proxmox has tested it against ESXi 6.5 through 8.0; disks on vSAN and encrypted disks cannot be imported that way. If you need vSphere for a transition, VMware vSphere Hypervisor 7 and 8 are on the same order form; the licence for those is yours to arrange with Broadcom. The four-socket page works out what per-core hypervisor licensing does to a large machine, which is usually the reason people are here.

The hardware and the network are ours to keep running; the machine is yours to run. Root is yours, the console is yours, and reinstalling is a button in the control panel. If a disk, a memory module or a power supply fails, on-site staff replace it within four hours of the report under the service agreement, and network unavailability of 15 consecutive minutes or more earns a credit. Support by phone and live chat is staffed 24 hours a day and costs nothing. Engineer time inside Proxmox itself, such as designing your storage or migrating your guests, is a separate service; ask before you order and we will say what it costs.

A machine already racked is live about 30 minutes after the order is approved; the Proxmox build itself takes around a quarter of an hour of that. A configuration built to order is assembled and handed over within 4 to 24 hours. Service is month to month with no contract and no minimum term; you stop it from the control panel and it ends at the close of the billing month. Paying 3, 6 or 12 months ahead takes 5%, 10% or 15% off. Where a machine or an optional add-on carries a one-off charge it is itemised on the order page before you pay; Proxmox itself carries none.

Yes. It is your hardware and your hypervisor; how many tenants share it is your decision, not ours. Up to eight public IPv4 addresses per server are on the order form, and guests beyond that are routed. Reseller panels that drive Proxmox through its API exist and are yours to run. Windows guests run under KVM; a Windows licence for a guest is the customer's own, as it is on any hypervisor.