A licensing or renewal decision under time pressure
Broadcom's changes to VMware licensing have pushed some organisations into a decision they didn't plan for this year.
Enterprise engineering
Kritical plans and delivers VMware Cloud Foundation work around the workloads, infrastructure and operating responsibilities that depend on it. Start with the problem to resolve, from a platform assessment to a scoped migration or upgrade, and get a written scope and price before anything changes.
On this page
Jump to the part that matches the problem or decision in front of you.
Broadcom builds VMware Cloud Foundation as a full-stack private-cloud platform: integrated compute, storage, networking, security and management delivered through vSphere, vSAN and NSX, with self-service automation on top so a team can provision VMs and containers without waiting on a ticket queue. VMware Cloud Foundation supports NVIDIA GPUs for private AI workloads. Support for other accelerators varies by release, so we check the current Broadcom compatibility guide for the hardware you plan to buy. You shouldn't have to guess what that means for your own estate — we translate the platform's actual capability into what your workloads, your recovery requirements and your operating team can support.
You don't need a finished target design to start this conversation.
Broadcom's changes to VMware licensing have pushed some organisations into a decision they didn't plan for this year.
Hosts, storage or networking components are approaching end of support and nobody has mapped what depends on them.
Private AI or GPU workloads are being considered on the existing virtualisation platform, but nobody has sized the whole stack yet.
A useful assessment starts with the installed versions, topology, workload requirements and operational condition — not an assumed target design.
Compute, storage, networking, management services and every system that depends on them, mapped before we recommend anything.
Management domain, workload domains, connectivity, identity, certificates, backup integration and monitoring, alongside hardware and software compatibility.
Not inferred from technical capability — checked against the commercial arrangement you hold.
Prerequisites, maintenance windows, workload sequencing and the conditions that stop a change, agreed before we touch production.
The proposal applies the same engineering disciplines—scope, evidence, testing, rollback and handover—to a platform where a mistake may be expensive to unwind.
Identify prerequisites before implementation.
Use a window agreed for the environment.
Sequence workloads around the planned change.
Define stopping conditions and evidence before proceeding.
A scoped assessment, migration, upgrade or remediation is quoted in writing before work starts — the licence and support entitlements you already hold are identified separately and never assumed included. Handover can include the implemented design, configuration records, runbooks and a list of unresolved constraints. Ongoing platform management and vendor support stay explicit responsibilities, including who handles an incident after the project closes.
Bring the current vCenter and host versions, the workloads involved and the change you're considering.
We confirm whether this is an assessment, a migration or a remediation, and what evidence we need to scope it.
A scoped assessment covering the dependency map, the compatibility position and a recommended path, priced in writing.
Send the systems and constraints involved and we quote the work.
No. Tell us about an existing environment, planned upgrade, migration or technical issue. We can scope an assessment before recommending an implementation path.
Yes. We compare options against workload dependencies, operating effort, migration risk and commercial inputs. The result should support your decision rather than assume a replacement.
Not automatically. Required entitlements, support arrangements and any procurement work are identified in the scope and confirmed separately.
We factor the current commercial terms into the assessment and flag where a licensing change affects the technical design, rather than treating licensing as someone else's problem.
Yes. We size the model, accelerator, storage, network and facility requirements alongside the virtualisation platform so the AI decision doesn't get made in isolation.
Tell us what you want to achieve, what you have today and when it matters.