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. And every week the reaction is the same. Someone forwards the quote with a one-line email: “Is this right?”

It's right. Here's what changed, what it actually costs now, and the escape hatch we built for exactly 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 actually bought are gone: the Essentials Plus kit was retired, and vSphere Standard hit end-of-sale on July 31, 2025. If you're a three-host shop, the product you're being quoted today is vSphere Foundation (VVF), a bundle priced per core, with a 16-core minimum per CPU, packed with features you may never touch.

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%. Miss your renewal anniversary and there's a 20% late penalty waiting.

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.

Here's the thing: it almost doesn't matter. Even at the 16-core floor, per-core subscription pricing punishes small clusters. Do the math on yours.

Take the standard build: three hosts, dual socket, 16 cores per socket. That's 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.

What did the same cluster cost on the old vSphere Standard model? On the order of $3,600 a year. Same three servers. Same workloads. Four to five times the licensing bill, before you've bought a single piece of hardware.

The usual answer is “fine, we'll refresh the hardware and ride it out.” That plan got expensive too, because AI demand is eating 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 “keep vSphere, buy new hosts” plan means: pricier boxes, a much pricier license attached to every core in them, and a wait measured in quarters.

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 is licensed per socket, not 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.

That's the old vSphere Standard number. The one Broadcom took away.

Here's the honest catch: a two- or three-person IT team doesn't want to become a Proxmox operations team. Migrating a hypervisor is real work, and running one well (patching, clustering, storage tuning, backup verification, capacity planning) is a permanent job, not a project.

That's the gap we built for. ModernOps runs Proxmox at scale in our own infrastructure, behind a custom front end that gives your team the cloud experience (a self-service portal, fast provisioning, monitoring, predictable monthly billing) without you owning a single host. Compute lands on our IaaS. Recovery is covered by DRaaS with defined RTO and RPO. Backup is delivered as BaaS on enterprise storage with immutability built in.

Because it's one platform serving many clients, you get economies of scale a three-host shop can't reach alone. And when something breaks at 2 a.m., you call a phone number and an engineer answers. Not a chatbot. Not a ticket queue in another hemisphere.

People assume hosted means marked up. It's the opposite, and the reasons are structural.

Start with redundancy math. 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're paying 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 iron per VM is a real, recurring saving.

Then there's the boring part, which is the point. Every host in our fleet runs one extremely by-the-book 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, and when something does misbehave, troubleshooting a known configuration takes minutes instead of a weekend of archaeology. Operations hours are one of the biggest hidden costs of self-hosting, and standardization removes most of them.

And nothing sits stranded. We fill racks properly and share what was built to be shared: a switch port that would sit dark in your closet serves another workload here, so nobody is buying 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 are simply our problem, not yours.

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

There's precedent at much larger scale for the underlying idea: that predictable workloads on the right platform beat sticker assumptions. 37signals famously 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 direction of the math holds at three hosts too; it just points toward a shared platform instead of your own racks.