Renting a Proxmox Server: Hosting Providers Compared

You rent a Proxmox server from providers of dedicated bare-metal or root servers. In Germany and the EU these are mainly Hetzner, IONOS, OVHcloud and netcup. Proxmox VE is a Debian-based type-1 hypervisor that runs directly on the hardware and requires the CPU virtualization extensions Intel VT-x or AMD-V. That is why Proxmox belongs on a dedicated server and does not run usefully on most shared VPS instances, which are already virtualized themselves. The current release is Proxmox VE 9.2 (May 2026, based on Debian 13 "Trixie"). If you do not want to administer the server yourself, you rent the hardware from a host and have setup, operations and backup handled by a managed Proxmox provider such as WZ-IT. For platform fundamentals, see What is Proxmox.

Where can I rent a Proxmox server?

The Austrian company Proxmox Server Solutions GmbH sells only the software and optional subscriptions, not hosting. You rent the hardware from a server host. Suitable options are dedicated servers (bare metal) or dedicated root servers. The most relevant providers in the DACH region and the EU are:

• Hetzner (data centers in Falkenstein and Nuremberg in Germany, and Helsinki in Finland)
• IONOS (German data centers, part of United Internet)
• OVHcloud (French provider with EU data centers, including Frankfurt)
• netcup (German provider with data centers in Nuremberg and Vienna)

On all four you install Proxmox VE yourself or have it installed. OVHcloud offers Proxmox VE as a preinstallable operating-system image during the order process. On Hetzner you install via the rescue system using the official auto-install ISO, or via Debian. We walk through that step by step in Set up Proxmox on Hetzner.

Why Proxmox needs bare metal and does not run on shared VPS

Proxmox VE is a bare-metal hypervisor: it replaces the operating system on the physical server and divides its CPU, RAM and storage into virtual machines (KVM) and containers (LXC). For that it needs direct access to the CPU's hardware virtualization.

A classic shared VPS is itself already a virtual machine on someone else's hypervisor. In most cases the virtualization extension is not passed through to the guest, so Proxmox cannot start any VMs. Some KVM-based root servers (for example from netcup, or OVHcloud's VPS ranges) enable nested virtualization. Proxmox then runs technically, but with a noticeable performance penalty and without suitability for production load. For labs, training or a test cluster that is fine, for business operations it is not.

The conclusion: for production, Proxmox belongs on a dedicated server. There you have full control over CPU, RAM, NVMe/SSD and networking, and you can use features such as live migration, ZFS or Ceph and build an HA cluster.

Provider comparison

The table below compares the four providers along the criteria that matter for a Proxmox decision. Prices change constantly, so we rate the price level qualitatively rather than with specific figures.

A few practical notes on each:

• Hetzner leads on raw hardware price, especially through the Server Auction with used dedicated servers. The strict IP and MAC binding matters: for VMs with their own public IP you need a routed setup or a vSwitch. Details in Proxmox cluster networking on Hetzner.
• OVHcloud stands out with a preinstalled Proxmox image and the vRack as a private layer-2 network spanning multiple servers, ideal for clusters and storage separation. The network configuration differs from Hetzner, see Cluster networking on OVH.
• IONOS offers a private network with tagged VLANs, so you can cleanly separate cluster, storage and management traffic. More in Cluster networking on IONOS.
• netcup is inexpensive and EU-based. Its low-cost root servers are KVM-based virtual servers; nested virtualization for your own VMs is not enabled by default and must be requested from support (sometimes for a monthly surcharge). For real bare metal, netcup offers separate dedicated servers. For production load we recommend dedicated hardware here as well.

On GDPR, the same applies to all four: as long as the server sits in an EU data center and a data processing agreement (DPA) is in place, the basis is there. Hetzner, IONOS and netcup are companies based in Germany or the EU, OVHcloud is French. Final compliance depends on your configuration, such as encryption, backups and access control.

Setting up Proxmox on a netcup server

netcup is a special case worth a closer look, because the provider runs two very different product lines. Which one you pick decides what is technically possible with Proxmox.

netcup's low-cost (v)Root servers are virtual KVM servers. Nested virtualization for your own KVM VMs is not enabled by default; you have to request it from netcup support, and it sometimes carries a monthly surcharge. Without nesting, Proxmox still runs usefully on these servers, but with fast LXC containers instead of full KVM VMs. For many workloads such as web services, databases or reverse proxies, LXC containers are lightweight and perfectly production-ready.

If you need full KVM VMs with their own kernel, choose netcup's dedicated root servers (bare metal). There hardware virtualization is available directly, and Proxmox runs with its full KVM and LXC feature set. For platform fundamentals, see What is Proxmox.

Practical setup on a netcup (v)Root server

1. Install Debian: In the netcup Server Control Panel (SCP, formerly CCP) select a current Debian image matching your Proxmox version, i.e. Debian 13 "Trixie" for Proxmox VE 9, and install it via the console.
2. Set a clean FQDN: In /etc/hosts add a fully qualified hostname that maps to the public server IP, for example 203.0.113.10 pve.example.com pve. A correctly resolving FQDN is a prerequisite for the installation, otherwise it aborts.
3. Add the Proxmox repository: Add Proxmox's no-subscription or enterprise repository to your APT sources and import the signing key.
4. Install Proxmox: From the SCP console install the proxmox-ve package including the kernel, reboot, and then reach the web interface on port 8006.

On a virtual (v)Root server, before creating VMs check with kvm-ok or the flag in /proc/cpuinfo whether nested virtualization is active. If it is not, plan for LXC from the start. For production load we recommend dedicated hardware at netcup too; what operations cost beyond the rent is covered in How much does Proxmox cost.

Self-managed or managed Proxmox?

The hardware is only half the job. What matters is who operates the platform.

Self-managed makes sense if you have in-house expertise and capacity for virtualization. Managed makes sense when Proxmox runs business-critical workloads but you do not want a team working on it around the clock. In practice the host is replaceable, reliable operations are not. What Proxmox really costs beyond the rent is covered in How much does Proxmox cost.

Who provides support for open-source virtualization?

You buy vendor support through a Proxmox subscription directly from Proxmox Server Solutions. That covers the software, but not your specific environment, your network at the host or your backup strategy. This is where WZ-IT comes in: we are a German managed service provider running Proxmox in production for customers, from selecting the right host through installation, cluster setup and networking to updates, monitoring and encrypted offsite backups with Proxmox Backup Server.

Unlike a pure host, we are vendor-neutral and tied to the open-source platform rather than to specific hardware. You remain the owner of your servers and your data, while we take care of reliable operations with defined response times.

Operations and support

Renting the server is the easy part. Reliable operation of Proxmox - cluster, network, updates and backup - is the real work. We plan, set up and operate Proxmox environments on Hetzner, IONOS, OVHcloud and on hardware of your choice. Our page on Proxmox and private cloud gives an overview, and our Proxmox maintenance and operations page covers ongoing operations. We are happy to discuss your project in a free initial consultation.