Proxmox VE didn’t start as a bid to dethrone VMware, and for most of its first fifteen years nobody outside a fairly niche crowd of sysadmins had strong opinions about it either way. It started because two brothers in Vienna needed a backup button that didn’t exist. This is how a self-funded Austrian startup ended up as the platform enterprises pointed to when they wanted an alternative to Broadcom’s price list.
A backup tool that grew into a hypervisor (2005)
Martin Maurer and Dietmar Maurer founded Proxmox Server Solutions GmbH in Vienna, Austria, in February 2005. There was no outside funding involved; the company was bootstrapped from day one and has stayed that way, still 100% owned by its founders two decades later. The first product out the door wasn’t a hypervisor at all, it was Proxmox Mail Gateway, a spam-filtering appliance that shipped its 1.0 release that same April. That mattered more than it sounds: a working, revenue-generating product gave the Maurers room to spend years building a hypervisor nobody had asked for yet, without chasing venture capital or a launch deadline set by an investor.
The idea for Proxmox VE came out of a specific frustration. The Maurers were using OpenVZ, an early Linux container technology, and found it had no backup tool and no management GUI worth using. Rather than work around the gap, they decided to build both, and to bolt on full virtualization while they were at it, since KVM was landing in the mainline Linux kernel around the same time. Combining container-based virtualization and a hardware-level hypervisor under one web console was an unusual pitch in 2005; most of the industry treated the two as separate product categories.
Debian, OpenVZ, and the first public release (2008)
It took three years of development before Proxmox VE was ready for the public. The first release landed on April 15, 2008, tagged version 0.9, built on top of Debian and managing both OpenVZ containers and KVM virtual machines from a single browser-based interface. That combination, Debian’s stability underneath, containers and VMs side by side on top, is still the same basic shape Proxmox VE has today. The first stable 1.0 release followed that October. By 2013, tech press coverage marking the project’s fifth birthday was already treating it as a fixture of the Linux virtualization world rather than a curiosity, a reasonable sign the original bet had paid off.
For more on how that architecture holds up as a homelab hypervisor in 2026, our full Proxmox VE guide covers installation, IOMMU passthrough, and the free-versus-Enterprise repository question in detail.
Clustering, high availability, and a business model (2010-2013)
The next few years were about turning a single-node tool into something a small business could run a cluster on. Proxmox VE 2.0 introduced high availability built on the Corosync communication stack, letting a VM restart automatically on another node if its host went down, a feature that mattered a lot more once people started running more than one Proxmox box.
2013 brought the piece of the story that shapes how homelabers still install it today: a subscription-based support model, with a paid Enterprise repository sitting next to a free “no-subscription” one carrying the exact same packages. It was a way to fund a growing engineering team without touching the AGPLv3 license on the code itself, and it’s the same split still in place now.
Retiring OpenVZ for LXC (2014-2015)
OpenVZ had been Proxmox VE’s container engine since the beginning, but it was never a comfortable fit for the long term. It lived as a large out-of-tree kernel patch that had to be maintained separately from mainline Linux, and it didn’t track newer kernel versions well, a real problem once security patches and hardware support started depending on kernel currency.
Proxmox VE 4.0, released on December 11, 2015, replaced OpenVZ with LXC, the Linux Containers project baked into the mainline kernel, and shipped a rebuilt HA manager alongside it. Existing OpenVZ containers could be converted to LXC during the upgrade, but from that release forward, container technology in Proxmox VE stopped being a custom patch and became infrastructure the rest of the Linux world was maintaining too. Not every user welcomed the change; old Proxmox forum threads from that period carry titles like “Moving to LXC is a mistake!”, since some OpenVZ-specific workflows didn’t map over cleanly. A decade later, LXC’s tighter integration with mainline kernel development looks like the correct long-term bet.
A decade of unglamorous maturity (2016-2022)
Most of the next several years weren’t dramatic. Proxmox VE added ZFS as a first-class storage option, then Ceph integration for distributed storage across a cluster, then a software-defined networking stack. In 2020 the company shipped Proxmox Backup Server, a separate product for incremental, deduplicated backups, written in Rust rather than Perl, the first sign of a language shift that would show up more across the codebase in later years. None of this made headlines outside the self-hosting and sysadmin communities that had already adopted it, but it built the feature set that made Proxmox VE a credible ESXi replacement rather than a hobbyist toy, once people started actually looking for one.
A stranger deployment than most homelabs: Proxmox VE reportedly runs aboard the Columbus module, the European Space Agency’s science lab on the International Space Station, according to a 2025 Proxmox community conference talk. Proof that its mainline-Linux approach scales in genuinely unusual environments, not just spare closets and rack shelves.
Broadcom buys VMware, and Proxmox VE stops being a niche pick (2023-2025)
The event that changed Proxmox VE’s trajectory wasn’t anything the company did. Broadcom closed its $69 billion acquisition of VMware in November 2023 and immediately began restructuring how VMware was sold: thousands of SKUs collapsed into a handful of bundles, the free ESXi tier disappeared, and renewal quotes for existing customers reportedly jumped by 800%, in some reported cases over 1,000%. AT&T became one of the more widely cited examples, quoted a 1,050% increase on its renewal. A Gartner Peer Community survey found roughly three-quarters of IT leaders actively exploring VMware alternatives, and Gartner has projected that as much as 35% of VMware workloads could migrate to other platforms by 2028.
The reaction was immediate, and Proxmox was one of the names that kept coming up as displaced customers went shopping. Independent market research put Proxmox VE’s share of server-virtualization mindshare at roughly 16% by 2025, up from around 10% just two years earlier, a jump largely credited to displaced VMware customers rather than organic homelab growth. By its 20th anniversary in April 2025, Proxmox reported more than 1.5 million hosts running its software worldwide and over 1,000 reseller partners across 142 countries, numbers that would have sounded implausible for a bootstrapped Austrian company a decade earlier.
For anyone actually weighing that migration, our comparison of Proxmox VE against TrueNAS covers where a general-purpose hypervisor fits against a storage-first platform, which is usually the more useful question than picking a single “ESXi replacement.”
Where that leaves Proxmox VE now
Twenty years on, Proxmox Server Solutions is still privately held by the two brothers who founded it, still headquartered in Vienna, and still running the same basic free-core-plus-paid-support model it settled on in 2013. What changed is the audience: a project built to fix one team’s backup annoyance is now the default answer enterprise IT departments reach for when a much larger vendor decides to make virtualization expensive. The company’s newest product, Proxmox Datacenter Manager, is built to manage many PVE clusters from one place, which points at exactly the scale problem VMware customers are now trying to escape.