Most organisations did not choose VMware Cloud Foundation. They were moved to it. When Broadcom retired vSphere Enterprise Plus and collapsed the catalogue into a handful of bundles, VCF became the destination for any estate too large for vSphere Standard’s 512 core cap or in a region where vSphere Foundation has been withdrawn. So the question we are asked most often is not whether VCF is a good platform. It is whether it is worth what is now being charged for it. The honest answer is that it depends entirely on whether you use what you are paying for, and most estates, as licensed today, do not.
What VCF actually is, and what it can be worth
VCF is the full software defined data centre in one bundle: vSphere for compute, vSAN for storage, NSX for networking, and the lifecycle and operations tooling that ties them together. Deployed deliberately, that is a genuinely strong platform. One operational model across the estate, lifecycle management that removes a great deal of manual patching and upgrade work, a consistent foundation for a private cloud, and the option to extend the same stack into hybrid arrangements. For an organisation running enterprise workloads at scale that intends to use the whole stack, VCF can represent good long term value.
The value case breaks in a predictable set of ways, and they are almost always inherited rather than chosen. Over provisioning from years ago carried forward into the new licence count. Growth assumptions nobody has revisited. Components licensed because they come in the bundle and never switched on. And, most often, an architecture designed under a different commercial model that now inflates the core count for no operational reason. None of that is a fault of the platform. It is a fault of renewing without looking.
Right size before you negotiate
A VCF renewal should not start with the price. It should start with the environment, because the price is a function of the core count and the core count is a function of decisions you can still change.
The audit we run before any commercial conversation covers the real utilisation of hosts, clusters and workloads; entitlement against what is actually deployed; which VCF components are genuinely in use or genuinely planned; the architectural decisions that are pushing the billable number up; and where the estate can be consolidated without adding risk. On its own this step routinely identifies a material reduction before anyone has negotiated anything, because under per core pricing with a 16 core minimum per processor, every host you do not need is licensing you are paying for. Our guide to VCF or VVF covers the bundle decision in detail, and the free VMware licensing cost calculator will show you what the core count does to the bill.
Then use the components, or stop paying for them
If you are going to be on VCF, the way to make it worth the money is to adopt the capability you are already licensed for. NSX for micro segmentation and network security that would otherwise be a separate purchase. vSAN data services in place of a storage array refresh. The lifecycle tooling to replace manual upgrade cycles. Each of those has a real cost elsewhere in the budget, and each is one you are already paying for. Building an adoption roadmap for the components that fit, and challenging the bundle where they do not, is how a forced move becomes a deliberate one.
Negotiate from evidence
Renewals under Broadcom are often presented as fixed. They are rarely fixed. The first number reflects the vendor’s assumptions about your estate, your alternatives and your timeline, and every one of those can be changed by evidence. An audited baseline, a model of the renewal across several scenarios, and a realistic assessment of what leaving would cost and how long it would take: with those in hand, the conversation moves from accepting a figure to challenging it on facts. We spent years on the vendor side of these deals, so we know how they are structured under Broadcom ownership, where flexibility still exists when it appears not to, and which assumptions can be challenged constructively. The key is not confrontation. It is clarity. Staying on VMware after Broadcom, done well sets out the method.
The cloud question
Renewal pressure often triggers a conversation about leaving for public cloud. In theory it looks attractive. In practice the economics are frequently misunderstood. Assessed properly, steady state cloud costs for a lifted and shifted estate often exceed a right sized VCF environment; networking, egress and operational overheads are underestimated; the migration effort and business risk are underplayed; and cloud introduces a different form of lock in rather than removing it. Cloud can absolutely be the right answer, but only when it is evaluated on full lifecycle cost and risk, not as a reaction to a quote. For many workloads a right sized VCF platform remains the sensible option. The wider set of alternatives is compared honestly in VMware alternatives compared, and should you leave VMware gives you a way to decide.
Why our independence matters here
We do not resell VMware. On VMware we earn nothing from the licence and nothing from the transaction, which means our role is simple: tell you when VCF makes sense, tell you when it does not, help you right size and negotiate when it does, and stop historic waste being carried into a new licensing model. We do not promote platforms. We promote better decisions, which is the same approach we take across technology acquisition generally.
The short version
VMware Cloud Foundation is not the problem. Unchallenged assumptions are. Organisations that treat a VCF renewal as a reset, technical and commercial, consistently do better than those that accept the inherited position. If your renewal is approaching, the most valuable step is to pause, right size and validate before you sign. That is where the leverage still is, and it only lasts while you have runway.
If you are planning a VMware renewal or a VCF transition, our VMware strategy and renewal support starts with the audit, or email hello@c4cgroup.co.uk.