On 22 November 2023, after roughly eighteen months of regulatory review across multiple jurisdictions, Broadcom completed its acquisition of VMware. The deal, valued at around $69 billion when announced, places one of the most widely deployed pieces of enterprise infrastructure software — VMware’s virtualization stack — under the control of a company with a distinct and well-documented approach to managing the software businesses it acquires. For the enormous installed base of organizations running vSphere, vCenter, NSX, and the broader VMware portfolio, the relevant question now is not whether things will change, but how. This piece is necessarily speculative: the deal closed barely two weeks ago, and Broadcom has not yet detailed its plans. What we can do is read the pattern from history.
Why VMware Sits at the Center of So Many Datacenters
VMware’s significance is hard to overstate. Server virtualization — running many isolated virtual machines on a single physical host — is the foundation of the modern datacenter, and VMware’s vSphere has been the dominant platform for it across enterprise IT for well over a decade. A very large share of private-datacenter and private-cloud workloads, particularly in large enterprises and the public sector, runs on VMware. The stack is deeply embedded: in operational tooling, in staff skills and certifications, in backup and disaster-recovery products, and in the architecture of countless applications that were never designed to run anywhere else.
That depth of embedding is precisely what makes the change of ownership consequential. VMware is not a product an organization can swap out over a weekend. It is infrastructure, with all the inertia that implies.
Reading the Broadcom Pattern
Broadcom has acquired large enterprise software businesses before — notably CA Technologies in 2018 and Symantec’s enterprise security business in 2019. Observers of those transactions have described a recognizable playbook, and while past behavior is not a guarantee of future conduct, it is the best available evidence for what customers should anticipate.
The pattern, as commonly characterized, has several elements:
- Focus on the largest customers. Broadcom has tended to concentrate sales and support attention on the biggest accounts — the strategic relationships that generate the most revenue — while smaller customers receive less bespoke attention.
- Portfolio simplification. Acquired product lines are often rationalized, with less strategically central products de-emphasized, repackaged, or discontinued.
- Commercial restructuring. Licensing and packaging models have, in past acquisitions, been revised in ways that altered how customers buy and what they pay.
Broadcom’s leadership has, in public statements around the VMware deal, emphasized investment in VMware’s core platform and a focus on simplifying the portfolio and the way it is sold. Read alongside the historical pattern, that language points toward consolidation and a streamlined commercial model. The specifics, however, have not been announced, and customers are right to wait for detail rather than to assume the worst.
What Customers Should Watch
For organizations running VMware, the prudent posture in the weeks ahead is attentive rather than reactive. Several developments are worth watching closely as Broadcom’s plans become concrete.
Licensing and packaging. The single most consequential question is how VMware’s products will be licensed and packaged going forward. Any move that changes the unit of purchase, bundles products differently, or revises pricing structure will ripple through renewal budgets. Organizations with renewals on the near horizon should engage early and model multiple scenarios.
Product roadmap and portfolio. Which products Broadcom treats as core and which it de-emphasizes will shape long-term planning. Customers depending on peripheral VMware products should seek clarity on their continued investment.
Partner and channel arrangements. Many organizations buy and support VMware through partners. Changes to partner programs would affect the support relationships those customers rely on.
Support experience. The historical pattern of concentrating attention on the largest accounts raises a practical question for mid-sized organizations about the support experience they should expect.
The Strategic Case for Optionality
Whatever Broadcom ultimately decides, the acquisition is a useful prompt for a question that infrastructure teams should periodically ask regardless of any single vendor’s conduct: how reversible is our dependence on this platform?
This is not a recommendation to abandon VMware — for most organizations that would be a costly overreaction to changes that have not yet been announced. It is a recommendation to understand the cost and feasibility of alternatives, so that the organization negotiates and plans from a position of knowledge rather than assumption.
The alternatives exist and have matured considerably. Open-source virtualization and private-cloud platforms — among them OpenStack and the lighter-weight OpenNebula, both with roots in the distributed-systems and grid-computing research tradition — offer paths to virtualization and private-cloud management without a single commercial owner able to set terms unilaterally. KVM, the Linux kernel’s virtualization layer, underpins much of the public cloud and several of these platforms. Proxmox, Nutanix, and the major public clouds’ migration tooling are also part of the landscape. None is a drop-in replacement for a deep VMware estate, and migration is a serious undertaking — but knowing the lay of that land is part of prudent planning.
A Familiar Lesson About Dependency
The deeper point this acquisition surfaces is one the open-infrastructure community has made repeatedly: software an organization depends on operationally is a supply-chain dependency, and the governance of that dependency is a risk worth assessing before circumstances force the issue. A product controlled by a single commercial entity can change ownership, and ownership can change terms. That is not a criticism of any particular acquirer; it is a structural fact about proprietary platforms.
The organizations best positioned to navigate the post-acquisition VMware landscape will be those that understand their dependency in detail — what they run, how deeply it is embedded, and what the realistic alternatives cost. The acquisition has not yet changed anything for most customers. The sensible response is to use the interval before Broadcom’s plans become concrete to build that understanding, so that whatever is announced is met with analysis rather than alarm.
Further Reading
- Open Infrastructure Foundation — governs OpenStack and related open virtualization and private-cloud projects relevant to evaluating alternatives.
- Linux Foundation — neutral-governance home for KVM-adjacent and open infrastructure projects.