The 3-host VMware trap, and the escape hatch that costs about half.

I work for ModernOps, a VAR and MSP outside Philadelphia. Every week I see renewal quotes land on the desks of IT managers running the most common infrastructure footprint in the mid-market: three VMware hosts, shared storage, somewhere between 20 and 80 VMs. The reaction is consistent. Someone forwards the quote with a one-line email: “Is this right?”

It is right. This note covers what changed, what the licensing costs now, and the alternative we built for this situation.

When Broadcom closed the VMware acquisition, it ended perpetual licensing entirely and collapsed roughly 168 products into four subscription bundles. The two SKUs small shops bought are gone: the Essentials Plus kit was retired, and vSphere Standard hit end-of-sale on July 31, 2025. A three-host shop is quoted vSphere Foundation (VVF) today, a bundle priced per core, with a 16-core minimum per CPU, that includes features a small cluster may have no use for.

The renewal increases being reported publicly range from 150% to over 1,000%, and analyses focused on small business specifically put the typical jump at 350–450%. Missing the renewal anniversary adds a 20% late penalty.

In April 2025, Broadcom announced a 72-core minimum per order, meaning a small shop buying licensing for one modest server could be forced to license 72 cores. Reporting since then conflicts: some sources say it took effect and drove 200–350% increases on small and edge deployments; others say it was walked back after backlash, leaving the 16-core-per-CPU floor.

Either way, the outcome for a small cluster is similar. Even at the 16-core floor, per-core subscription pricing weighs heavily on three hosts. The next section works through the figures.

Take the standard build: three hosts, dual socket, 16 cores per socket, which comes to 96 licensable cores.

VVF list pricing has been reported at $150–$190 per core per year depending on term. So your three boxes now cost $14,400 to $18,240 a year in licensing alone.

The same cluster on the old vSphere Standard model cost on the order of $3,600 a year, for the same three servers and the same workloads. That is four to five times the licensing bill before any hardware is purchased.

The usual response is to refresh the hardware and ride it out. That plan has also become expensive, because AI demand is absorbing the component supply chain.

TrendForce reported conventional DRAM contract prices up roughly 93–98% quarter-over-quarter in Q1 2026, the largest quarterly jump on record, with another 58–63% projected for Q2 and NAND up 70–75%. Gartner projects DRAM up around 130% year-over-year for 2026.

Server vendors passed it through fast. Dell raised list prices roughly 17% effective March 30, 2026 across its lines including PowerEdge; Cisco raised compute pricing in early March; Lenovo, HP, and HPE followed with increases in the 10–15% range. Memory now represents as much as a quarter to a third of a server's bill of materials (a 32GB DDR5 server module that sold for about $149 was quoted near $239 roughly two months later), and lead times on popular configs stretched from around 10 weeks to 24 or more.

So the plan to keep vSphere and buy new hosts means pricier boxes, a much pricier license attached to every core in them, and a wait measured in quarters. One manufacturer took a different route and replaced the aging hosts and the array together, then put the displaced gear to work as their DR site.

Proxmox VE is the open-source hypervisor platform that a lot of the VMware exodus is landing on: over 1.5 million hosts under management worldwide, twenty years of development, and a built-in import wizard that pulls VMs straight off ESXi. Its developers estimate the large majority of typical vSphere environments migrate cleanly.

The economics are structurally different: Proxmox VE support is licensed per socket rather than per core, and the software itself is free. Enterprise repository support runs about €550 per socket per year on the Standard tier.

Six sockets across your three hosts is roughly €3,300 (~$3,600) a year, with clustering, live migration, HA, backup integration, and software-defined storage in the box.

The catch is operational. A two- or three-person IT team has little appetite to become a Proxmox VE operations team. Migrating a hypervisor is substantial work, and running one well (patching, clustering, storage tuning, backup verification, capacity planning) is a permanent job rather than a project.

That is what we built for. ModernOps IaaS runs Proxmox VE at scale in our own infrastructure, behind a front end that gives your team a self-service portal, fast provisioning, monitoring and predictable monthly billing, without your owning a single host. Compute lands on our IaaS, recovery is covered by DRaaS with defined RTO and RPO, and backup is delivered as BaaS on enterprise storage with immutability built in.

Veeam’s 13.1 release added a replication safety net for this move, which we cover in a follow-up field note.

Because it is one platform serving many clients, you get economies of scale that a three-host shop lacks on its own. When something breaks at 2 a.m., you call a phone number and an engineer answers.

Hosted is often assumed to carry a markup. In this model it comes in lower, and the reasons are structural.

Start with redundancy. A three-node cluster running N+1 keeps a full third of its hardware in reserve: you bought three hosts to safely use two, and you pay to power, license, patch and warranty all three either way. A ten-host platform cluster running N+2 reserves 20% instead of 33%, and that reserve is shared across every workload on the platform rather than parked for one company's bad Tuesday. Less idle hardware per VM is a recurring saving.

Then there is standardization. Every host in our fleet runs the same configuration: same firmware, same network layout, same storage design. Upgrades follow a defined cadence with documented, repeatable procedures, validated before they touch production. Predictable systems fail less often, and when something misbehaves, troubleshooting a known configuration takes minutes instead of a weekend of archaeology. Operations hours are one of the larger hidden costs of self-hosting, and standardization removes most of them.

Shared infrastructure also stops equipment sitting stranded. We fill racks fully and share what was built to be shared: a switch port that would sit dark in your closet serves another workload here, so nobody buys a 48-port switch to light up 12. Rack space, PDUs, UPS capacity and cooling are bought once, at data-center rates, and spread across the platform instead of one three-host island. Hardware refreshes happen on our schedule at volume pricing, spares are stocked once for the fleet, and patching and host upgrades become our work.

You get VMs and backups in a cloud-like format, and we handle the racks, power, cooling, refreshes and upgrades behind them. Add up the idle redundancy you no longer buy, the operations hours you no longer spend, and the ports and racks you no longer strand, and hosted comes in under buying and self-hosting the gear.

There is precedent at much larger scale for the underlying idea that predictable workloads on the right platform beat sticker assumptions. 37signals moved off the public cloud, bought its own storage for a fraction of its annual S3 bill, and reported cutting its overall cloud spend from over $3 million a year to well under $1 million. The same logic holds at three hosts; at that scale it points toward a shared platform instead of your own racks.