Proxmox Virtual Environment (Proxmox VE or PVE for short) is an open-source platform for virtualization and containers. It lets companies run virtual machines and containers on their own hardware, managed centrally through a web interface, with no per-core licensing costs. Proxmox is an open-source alternative to VMware vSphere and Microsoft Hyper-V.
Proxmox VE is based on Debian GNU/Linux and combines two virtualization technologies in one product: KVM for full virtual machines and LXC for lightweight Linux containers. It is licensed under the AGPLv3, owned by the Austrian company Proxmox Server Solutions GmbH, and uses open interfaces. Dependencies on tools, data formats and operational knowledge still need consideration.
Versions and lifecycle: Proxmox VE 9.2, PVE 8 end of support, Arm64
The current release is Proxmox VE 9.2, based on Debian 13 (as of October 2026); the previous version 8 reached end of life in August 2026 per the support lifecycle and no longer receives updates. Since August 2026, Proxmox VE has also run officially on Arm64 servers alongside x86-64.
For the transition: upgrade Proxmox VE 8 to 9.
What is Proxmox used for? Business use cases
Proxmox is the foundation for your own private cloud. Typical use cases:
- Server consolidation: Many physical servers are merged onto a few powerful nodes running dozens of VMs and containers.
- Replacing VMware: Companies migrate away from vSphere licensing to a sovereign platform with lower licence cost.
- High availability: Business-critical applications run resilient in a cluster; if a node fails, VMs restart automatically on another.
- Test and development environments: Quickly provisioned, isolated environments with snapshots and clones.
- Hosting open-source applications: Nextcloud, GitLab, databases and more, cleanly separated in their own VMs or containers.
How Proxmox is structured
A Proxmox setup consists of a few clearly defined building blocks:
- KVM (Kernel-based Virtual Machine) is the hypervisor for full virtual machines. Any guest OS, including Windows, runs on it.
- LXC (Linux Containers) provides resource-efficient containers that share the host kernel, ideal for many small Linux services.
- The web interface manages nodes, VMs, containers, storage and networking centrally in the browser. Everything is also controllable via a REST API and the command line.
- Clustering via Corosync joins multiple nodes into a federation with shared management.
- Storage: Proxmox supports ZFS, Ceph, LVM, NFS and more, from a local disk to distributed, highly available storage.
- Proxmox Backup Server (PBS) adds deduplicated, incremental and encrypted backups to the platform.
This manageable architecture is one reason Proxmox runs reliably, from a single server to a multi-node cluster.
The Proxmox product family
Proxmox VE is the best-known product, but not the only one - the four products interlock:
| Product | Purpose |
|---|---|
| Proxmox VE (PVE) | The virtualization platform itself: VMs, containers, clustering, HA, storage |
| Proxmox Backup Server (PBS) | Deduplicated, incremental and encrypted backups for VMs, containers and hosts |
| Proxmox Mail Gateway (PMG) | Email gateway against spam, viruses and phishing in front of your mail server |
| Proxmox Datacenter Manager (PDM) | Central overview and management across multiple clusters and standalone nodes |
What Proxmox actually does
Beyond simply starting VMs, Proxmox handles the tasks that make production operations practical:
- High availability (HA): If a node fails, VMs are automatically restarted on a healthy node (HA manager docs).
- Live migration: Running VMs are moved between nodes without interruption, e.g. for maintenance.
- Snapshots and clones: Freeze states, roll back or create templates for new systems.
- Integrated firewall: Rules at cluster, node and VM level.
- Role and permission management: Fine-grained access control, including LDAP or OpenID integration.
- Backup and restore: Scheduled backups, deduplicated and encrypted with PBS.
Proxmox vs. VMware vs. Hyper-V
| Proxmox VE | VMware vSphere | Microsoft Hyper-V | |
|---|---|---|---|
| Model | Open source (AGPLv3) | Proprietary | Proprietary |
| Licensing cost | None (optional support subscription) | Core-based subscription | Windows Server licence |
| Virtualization | KVM (VMs) + LXC (containers) | ESXi hypervisor | Hyper-V hypervisor |
| Vendor lock-in | Open formats; consider operational dependencies | High | Medium (Microsoft ecosystem) |
| Storage | ZFS, Ceph, LVM, NFS and more | vSAN, VMFS | Storage Spaces |
| Data sovereignty | Full, your own infrastructure | With the infrastructure operator | Microsoft-centric |
| Best for | Sovereign private cloud | Existing VMware estates | Windows-centric environments |
Moving from a deeply integrated VMware environment requires assessing features, integrations and operations. Proxmox is one possible alternative; suitability follows from requirements. Details: Proxmox vs. VMware, Proxmox vs. Hyper-V.
When Proxmox is worth it
Proxmox is the right choice if you:
- want to cut licensing costs, especially after the VMware price changes,
- need data sovereignty and want to control your infrastructure yourself,
- run a private cloud on your own or rented hardware (e.g. at Hetzner),
- need high availability without expensive add-on licences,
- or want to stay independent of a single vendor.
For a single small system a single-node setup is often enough. From production use with several applications onward, a cluster becomes the sensible foundation.
Next steps
- Setup: install Proxmox.
- VMware transition: migration to Proxmox.
- Operations: Managed Proxmox.
- Build knowledge: WZ-IT offers training. Discuss requirements through the Proxmox services page.
