Standardize on VCF
Adopt the full VCF stack as a private cloud.
Best fit: Large estates already using vSAN and NSX.
Watch: Subscription cost relative to features consumed.
The virtualization incumbent — VMware Cloud Foundation by Broadcom, at a strategic decision point for many estates.
Part of Broadcom · Also known as: VMware Cloud Foundation, VCF, vSphere
The strategic question
For most estates the decision is no longer which VMware product — it is whether VMware Cloud Foundation as a whole fits the next five years.
Acquisition
Broadcom acquires VMware and consolidates the portfolio around VMware Cloud Foundation.
Portfolio reshaping
Licensing moves to subscription bundles centered on VCF.
Now
Enterprises evaluate VCF as a private cloud platform against alternatives.
Private AI capabilities · Kubernetes workloads
NSX
vSphere · vSAN
VMware Cloud Foundation (VCF) · Lifecycle and operations
Adopt the full VCF stack as a private cloud.
Best fit: Large estates already using vSAN and NSX.
Watch: Subscription cost relative to features consumed.
Right-size the footprint and licensing scope.
Best fit: Estates with stable workloads and limited growth.
Watch: Long-term roadmap alignment.
Move selected workloads to other platforms or cloud.
Best fit: Portfolios with modernizable or containerizable apps.
Watch: Migration effort and dual-platform operations.
VMware defined enterprise virtualization, and its technology — vSphere compute, vSAN storage, NSX networking — still runs a large share of the world's workloads. Since Broadcom's acquisition, the portfolio has been consolidated around VMware Cloud Foundation (VCF) as the flagship private cloud platform, with simplified packaging and a subscription model.
For many enterprises this is a genuine decision point: the technology remains deep and widely skilled, while licensing structures, partner changes and portfolio consolidation have pushed organizations to re-evaluate strategy — some consolidating on VCF, others diversifying to alternatives such as Nutanix or cloud-native patterns.
| Scenario | Problem | Approach | Outcome |
|---|---|---|---|
| Virtualization strategy decision | Licensing changes make renewal a strategic question, not an administrative one. | Model the true estate: workloads, dependencies, skills and renewal exposure; compare consolidate-on-VCF against transition options. | A decision made on your numbers, with a defensible rationale. |
| Private cloud consolidation | The estate is sprawling clusters with inconsistent operations. | Consolidate onto VCF with standardized building blocks and operational discipline. | Cloud-like operations on infrastructure you control. |
| Microsegmentation for security | Flat networks let intrusions spread laterally. | Deploy NSX microsegmentation with application-aware policy. | Contained blast radius as a designed property of the network. |
| Private AI on owned infrastructure | AI workloads should run on owned, governed infrastructure. | Build AI-capable clusters on the private cloud platform with GPU resource governance. | AI capacity inside your trust boundary, operated like the rest of the estate. |
Broadcom-era licensing, bundling and partner changes are real strategic factors — evaluate total cost and flexibility against alternatives with current facts, not legacy assumptions. Skills remain abundant, which cuts in VMware's favor; portfolio consolidation reduces à la carte flexibility.
Organizations evaluating VMware's position under Broadcom typically model their own renewal economics before deciding between consolidating on VCF or diversifying to alternatives. Either path — VCF modernization or migration to another platform — demands workload-level rigor, since licensing changes have made this an executive-level decision rather than a routine renewal.
Questions buyers ask
It depends on the estate's specifics: renewal exposure, workload portability, skills and strategy. Consolidating versus diversifying should be modeled on real numbers before either decision is executed.
VCF consolidates compute, storage, networking and management into one lifecycle-managed private cloud platform — deeper integration, different packaging. Current estates should review what the packaging change means for their usage.
Material but manageable with engineering discipline: compatibility mapping, migration tooling, operational runbook transition and wave-based execution. The worst outcome is drifting into renewal without analysis.
Yes — private AI on VCF is a supported direction, particularly where data control is paramount. Comparisons against dedicated AI infrastructure are worthwhile for specific workload plans.
Independent editorial profile. Vendor facts reviewed against official sources, September 24, 2026.
Planning changes across data, AI, cloud or infrastructure? Tell us about your priorities.
Contact us