Physical core baseline
Capture processor and core counts for every in-scope host, even where cores are disabled or capacity is reserved. Current documentation uses physical-core metrics and minimums; a virtual-machine count alone is insufficient.
VMware by Broadcom licensing
VMware by Broadcom licensing
Build a current VMware licensing baseline from host cores, cluster design, required platform capabilities and the version you intend to operate.
Request a licensing quoteRequirementMetricTermLifecycleVMware by Broadcom
Licensing overview
Map the requirement before comparing offers.
VMware licensing should begin with the target infrastructure, not a historic licence-key inventory. Record every host, processor and physical core; map clusters and management domains; identify storage, networking, operations and automation requirements; and distinguish production, recovery, edge and laboratory environments.
Current VMware by Broadcom commercial discussions commonly centre on VMware Cloud Foundation (VCF) and VMware vSphere Foundation (VVF). Subscription and physical-core metrics apply to current offers, with a 16-core-per-processor minimum referenced in current programme documentation. Version 9 licensing workflows also differ from older 25-character-key processes. Because products, versions and contractual paths can coexist, the exact metric and management method must be validated against the applicable Broadcom documentation and quotation.
Atmic can help collect a defensible estate baseline and translate technical requirements into a quote request. That work does not create entitlement, promise upgrade rights or imply VMware authorisation. The signed order, programme documentation and product-specific terms remain decisive.
Relevant software areas
What teams commonly evaluate.
- VMware Cloud Foundation for an integrated private-cloud platform requirement
- VMware vSphere Foundation for applicable virtual infrastructure requirements
- Compute virtualisation, vCenter management and cluster lifecycle
- Software-defined storage, networking, operations and automation where included in the selected offer
- Subscription capacity and support alignment for production and disaster-recovery estates
Typical business uses
Where the requirement starts.
- Re-baselining a virtual estate before subscription renewal or platform upgrade
- Comparing current cluster requirements with VCF and VVF capabilities
- Planning capacity for new hosts, processor refreshes or data-centre consolidation
- Including recovery-site and edge hosts in a complete licensing model
- Reconciling purchased core capacity with the hosts and versions actually operated
Commercial and technical considerations
Details that can change the right quotation.
Platform composition
Define which compute, storage, networking, operations, automation and management capabilities are required. Components bundled within a platform may have deployment or co-location conditions.
Version and licensing workflow
Record deployed and target versions. Current VCF and VVF version 9 workflows use subscription-based licence files and central management rather than the legacy key process described in many older runbooks.
All environments
Include production, development, disaster recovery, management, edge and temporarily disconnected hosts. Do not assume a passive or powered-off host is automatically outside the relevant terms.
Dependencies and migration
Check hardware compatibility, supported upgrade paths, backup integrations, operational skills and application dependencies alongside licensing. Commercial fit and technical readiness are separate decisions.
Discovery checklist
Information to gather before requesting a quote.
- What VMware products, editions, versions and support identifiers are currently recorded?
- How many hosts, processors and physical cores exist in each cluster and location?
- Which storage, networking, management, operations and automation capabilities are actively required?
- What growth, hardware refresh, consolidation or recovery-site changes are planned?
- Are any workloads tied to version-specific APIs, hardware or third-party integrations?
- What subscription capacity, dates and procurement records already exist?
- Which current Broadcom programme documents will govern the proposed order?
Renewal and lifecycle planning
Treat renewal as a decision point.
- Maintain a host-and-core register that is reconciled with cluster changes and purchase records.
- Review entitlement before adding or replacing processors, hosts, clusters or locations.
- Track subscription dates, support identifiers, product versions and licence-management workflow together.
- Revalidate recovery, test and disconnected environments during each renewal review.
- Confirm current VCF or VVF product-specific documentation before implementation and again before renewal.
Product packaging, availability, metrics and terms can change. Final recommendations and quotations should be checked against the vendor’s current official product terms for the selected region and purchasing channel. No partner, reseller or authorisation status is implied on this website.
Licensing FAQ
Questions worth resolving early.
Is VMware still licensed with perpetual CPU licences?
Do not use that as a planning assumption. Current VCF and VVF offers use subscription and physical-core metrics. Existing contracts and older deployments may require separate analysis, so the applicable agreement and current quote must be reviewed together.
What does the 16-core-per-processor minimum mean?
Current programme documentation states a minimum of 16 licensed cores for each processor for relevant VCF and VVF offers. Actual physical cores and all other product terms still matter; the quote and current specific programme documentation should confirm the calculation.
Are VCF and VVF interchangeable?
No. They are distinct platform offers with different included capabilities and use cases. The technical design should identify required functions before the commercial comparison is made.
Can we estimate licensing from virtual-machine count?
Not reliably for current core-based offers. Host processor and physical-core inventory is fundamental, while virtual machines still matter for capacity planning, migration sequencing and application dependencies.
What should accompany a VMware quote request?
Provide a host-level core inventory, cluster map, deployed and target versions, required platform capabilities, current subscriptions, renewal date, growth plan and recovery-site scope. Atmic can structure this information without making an entitlement determination.
VMware by Broadcom
Prepare a better licensing request.
Share the users, devices, workloads, deployment model, current entitlement and renewal date.