VMware Subscription Pricing Calculator
Broadcom does not publish a public pricing calculator that gives you a defensible answer. You can — and should — build your own. This is the input set, the arithmetic, and the effective per-core rates we use with clients to size a credible cost model before the negotiation begins.
Every customer entering a Broadcom VMware renewal asks the same question first: what is this going to cost? The honest answer is that you cannot get a useful number from Broadcom directly until late in the cycle, you cannot trust a quote your incumbent partner produces without checking it, and you cannot use the published list-price tables without a series of adjustments that the documentation does not spell out for you. The customers who arrive at the negotiation with a defensible cost model are the customers who produce defensible outcomes.
This guide explains how to build a VMware subscription pricing calculator from first principles. The arithmetic is not hard; the discipline is in the inputs. We walk through the inputs that drive the model, the per-core arithmetic, the edition logic, the volume and term-discount curves, and the effective per-core rates that are reasonable to plug in for 2026 commercial planning.
Why you need your own calculator
The Broadcom commercial process is structured to produce a single number that the customer is asked to accept, reject, or negotiate. The single number contains many embedded assumptions about edition, commitment level, term, and discount eligibility. Without a calculator of your own, you cannot decompose the number into the components that drive it, and you cannot identify which components are commercially negotiable versus which are list-price-driven.
The calculator's value is not in producing a single competing number. The value is in producing a parameterised model that exposes the cost sensitivity to each input. The customer who knows that swapping VCF Advanced for VVF saves 35-50%, that moving from one-year to three-year term adds 8-15% discount, that committing at the next volume-tier threshold adds 4-8% discount, and that price-protection language is worth roughly 12% over a five-year horizon walks into the negotiation able to construct counter-proposals that Broadcom can evaluate against the customer's stated cost ceiling.
The inputs the calculator needs
A useful calculator needs eight inputs. The accuracy of each input drives the credibility of the model.
Deployed core count
The deployed core count is the licensed core count under the per-core model, adjusted for the 16-core-per-CPU minimum. For each host in the estate, the licensed core count is the maximum of the actual core count per CPU and 16, multiplied by the CPU count per host. A dual-socket host with 12-core CPUs is licensed at 32 cores rather than at 24. A dual-socket host with 32-core CPUs is licensed at 64 cores. Aggregate across the estate to produce the deployed-core figure.
The deployed-core figure is the starting point for the calculator. Customers running a discovery tool or a CMDB query to produce this figure should validate the output against the licensable host count, not against the inventoried host count; powered-off, decommissioning-in-progress, and dev/test isolated hosts are sometimes excluded from operational inventories but remain licensable.
Projected core count across the term
The projected core count is the deployed core count adjusted for known changes across the contract term: hardware refresh, workload growth, dev/test scope changes, decommissioning, workload migration off VMware, and workload migration onto VMware. A three-year term should produce a year-one, year-two, and year-three projected-core figure; the commitment level should be sized against the projection rather than against the current footprint.
Edition target
The edition target is the SKU the customer expects to subscribe to: VCF Enterprise, VCF Advanced, VCF Standard, VVF, vSphere Foundation, or vSphere Standard. The choice is principally driven by the deployed feature set rather than by a default toward the richest available edition; see our VCF licensing explanation for the feature-mapping discussion.
Term length
Term length is one, three, or five years. Longer terms attract additional discount; the trade-off is term risk.
Volume-tier eligibility
Volume-tier eligibility is the discount tier the customer's commitment level qualifies for. The tiers are not published but are observably structured around commitment thresholds (we describe the working bands below).
Strategic-discount category
Strategic-discount category is the customer-specific discount tier Broadcom assigns based on segment, account designation, and competitive context. Customers in target-growth segments or strategic-account designations qualify for discount levels above the volume-driven baseline.
Term discount
Term discount is the additional percentage discount the commercial offer reflects for multi-year commitment. Three-year terms typically carry an 8-12% incremental discount over one-year; five-year terms typically carry an additional 4-6% over three-year.
Effective list-price reference
Effective list-price reference is the per-core annual list price that the calculator applies before discounting. The list prices are not published but are observable through customer benchmarks and partner pricing data; we provide working bands below.
The per-core arithmetic
The basic arithmetic of the calculator is straightforward. Effective annual cost equals committed cores multiplied by per-core list price, multiplied by (1 - volume-tier discount), multiplied by (1 - strategic-discount), multiplied by (1 - term discount). The arithmetic chains the discounts multiplicatively rather than additively; a customer with a 30% volume-tier discount, a 10% strategic discount, and a 10% term discount receives an effective discount of approximately 43.3% off list, not 50%.
The committed cores figure should be the larger of the projected peak deployment and the SKU minimum. VCF subscription carries a 72-core minimum; smaller deployments cannot subscribe at sub-72-core commitment. VVF has a smaller minimum but is also typically not appropriate for very-small deployments; vSphere Foundation and vSphere Standard are the small-deployment SKUs.
Worked example: 800-core mid-market
Consider an 800-core mid-market customer evaluating VVF for a vSphere-and-vSAN-light deployment, three-year term, at the mid-volume-tier with no strategic-discount designation.
Working list price for VVF: approximately $350 per core per year (this is a planning figure, not a quote). 800 cores at $350 produces an undiscounted annual list of $280K. Apply a 25% mid-tier volume discount: $210K. Apply a 10% three-year term discount: $189K. The model produces an effective annual cost of approximately $190K, with a three-year total commitment of $567K.
The same 800-core deployment under VCF Advanced (with a working list of approximately $560 per core per year) at the same discount stack produces an effective annual cost of approximately $302K. The edition selection alone moves the annual cost by approximately $112K; the cumulative three-year decision is approximately $336K. The edition right-sizing analysis is, in practice, the largest single lever on the commercial.
The calculator should use parameterised working figures that the customer can sensitise rather than figures quoted by Broadcom or the partner. The calculator's purpose is to expose the cost sensitivity to inputs; using quoted figures defeats the purpose because the quoted figures already contain Broadcom's preferred discount assumptions.
Reasonable list-price working bands for 2026
List prices are not published. The following working bands are observed across our client benchmark as reasonable planning figures for the 2026 commercial cycle. Use them as inputs to your model; refine them with quoted figures as the negotiation progresses.
VCF Enterprise
Working list price band: $700-850 per core per year. The band reflects the premium for the full bundle including the complete Aria suite. Few customers without strategic Aria usage subscribe at this edition.
VCF Advanced
Working list price band: $520-600 per core per year. This is the principal enterprise SKU and the edition Broadcom typically quotes by default for VCF customers. Many customers' deployed feature set does not justify this edition; the right-sizing analysis is worth running.
VCF Standard
Working list price band: $400-460 per core per year. VCF Standard is a smaller bundle than Advanced and is positioned for deployments not using the full NSX advanced feature set.
VVF
Working list price band: $320-380 per core per year. VVF includes vSphere, limited vSAN (100GB per core), and a curated subset of Aria; it excludes NSX. For vSphere-and-light-vSAN deployments, VVF is the principal alternative to VCF.
vSphere Foundation
Working list price band: $180-230 per core per year. Standalone vSphere without vSAN or NSX bundle, suitable for deployments where storage and networking are handled outside the VMware stack.
vSphere Standard
Working list price band: $90-130 per core per year. The lower-feature standalone edition for smaller deployments without advanced vSphere features.
Volume-tier discount structure
The volume-tier discount curve is observably structured around commitment thresholds. The working bands across our client benchmark sit approximately as follows:
- Under 200 cores: 0-10% discount off list, with the discount frequently in the lower part of the band for customers without strategic-account designation.
- 200-500 cores: 10-20% discount off list.
- 500-1,500 cores: 20-30% discount off list. This is the mid-market band where most enterprise commercial negotiation sits.
- 1,500-5,000 cores: 25-40% discount off list, with the upper end reserved for committed multi-year terms.
- 5,000+ cores: 35-55% discount off list, with substantial dispersion across customers depending on negotiating outcome.
These bands are not contractual and are not published. They are observed across the deals we have seen and are presented as planning figures. Customers benchmarking their specific position should refine these bands with comparable-customer benchmark data.
Term-length and price-protection inputs
Term length and price-protection language carry pricing implications that should be modelled explicitly.
Term-discount delta
One-year subscription is the baseline. Three-year subscription typically attracts an additional 8-12% discount over one-year. Five-year subscription typically attracts an additional 4-6% over three-year. The term-discount delta is in addition to the volume-tier discount; it is not a substitute for it.
Price-protection valuation
The value of negotiated price-protection language is best modelled as a renewal-period cost-uplift scenario. Without protection, the renewal-period cost is whatever Broadcom prices at renewal; a 20% renewal uplift on a three-year deal produces approximately 6-8% additional cost over the next term. Capped-uplift protection at, say, 5% per year is worth approximately the difference between the expected uncapped uplift and the cap. Customers should model the protection value rather than treating it as a soft term.
Building the model in a spreadsheet
The calculator should be a single spreadsheet with five sheets: input parameters, deployment projection, scenario matrix, sensitivity analysis, and summary.
Input parameters sheet
List the eight inputs identified above, with a single editable cell per input. The cells feed into the rest of the model. Document the source for each assumed value so future maintainers can refresh inputs as benchmark data evolves.
Deployment projection sheet
Build a year-by-year deployment projection across the term, with explicit lines for current footprint, hardware refresh, workload growth, decommissioning, and migration impact. The projection feeds the committed-core input. The projection's accuracy is the calculator's principal risk; under-projection produces over-commitment, and over-projection produces over-spending.
Scenario matrix sheet
Build a matrix of edition choices (VCF Enterprise, VCF Advanced, VCF Standard, VVF, vSphere Foundation, vSphere Standard) across term lengths (1-year, 3-year, 5-year), with the per-core arithmetic producing an annual and total cost for each cell. The matrix exposes the cost sensitivity to edition and term and supports the right-sizing conversation.
Sensitivity analysis sheet
Build a sensitivity analysis showing the cost change for each plus/minus 10% on each principal input (list price, volume discount, strategic discount, projected core count). The sensitivity exposes which inputs matter most and supports the discipline around accurate input estimation.
Summary sheet
Build a summary sheet showing the recommended scenario, the alternative scenarios with their cost deltas, and the sensitivity-driven risk range. The summary is the artefact the customer uses in the negotiation; it should be defensible at executive sponsorship.
Using the calculator in the negotiation
The calculator's role in the negotiation is to anchor the customer's position in a defensible model rather than in a reaction to the supplier's quote. Several specific applications:
When Broadcom quotes a price, decompose the quote against the calculator: at the quoted edition, term, and commitment, what discount stack does the quote imply? If the implied discount sits below the customer's modelled band, the gap is the negotiating surface.
When considering an edition downgrade, run the downgraded edition through the calculator: what is the cost delta, and what features are foregone? The customer can then assess whether the foregone features matter against the cost saving.
When evaluating a multi-year commitment, run the multi-year scenario with and without price-protection language: what is the cumulative-cost delta, and what is the protection worth?
When considering walking away or partial migration, the calculator produces the residual-VMware cost figure that supports the migration-versus-renewal economic comparison.
Where independent advisory adds value
The calculator is a tool, not a substitute for the negotiation discipline. Independent advisory adds three specific elements that the calculator cannot reproduce. First, benchmark data: the working bands above are planning figures, but the actual customer-specific benchmarks come from comparable-deal data that advisory firms hold across client portfolios. Second, the negotiation experience: the calculator tells the customer what is possible; the negotiation discipline tells the customer how to achieve it. Third, edition-mapping expertise: the right-sizing analysis requires knowing both the SKU detail and the customer's actual deployment, and the mapping is where independent advisory typically earns its keep.
Pitfalls to avoid in calculator construction
Several pitfalls recur in customer-built calculators. Each is avoidable with the right discipline.
Ignoring the 16-core minimum. Customers projecting deployed cores against actual core counts rather than against the floor-adjusted figures under-count the licensed footprint, sometimes substantially. The deployment projection must apply the floor on a per-CPU basis.
Treating discounts as additive. The discount stack is multiplicative. A 30%+10%+10% stack is 43.3%, not 50%. The arithmetic difference is material at enterprise scale.
Modelling only the headline cost. The headline subscription cost is only part of the total cost. Support, professional services, migration costs (if any), and the operational change cost of edition adoption (e.g., NSX deployment if moving from non-NSX baseline) all sit alongside the subscription cost.
Using a single quote as the calibration point. The first quote is the supplier's opening position. Calibrating the calculator against the quote bakes the supplier's opening assumptions into the customer's model.
Failing to refresh inputs. The benchmark bands shift across the 2026 commercial cycle. A calculator built in early 2026 with the wrong bands will produce defective outputs by mid-2026. Maintain the inputs as the cycle evolves.
Connecting the calculator to the broader renewal strategy
The calculator is the first artefact of the renewal-planning cycle. The downstream artefacts are the alternative-vendor TCO comparison, the negotiating posture document, the executive-summary commercial-case, and the contract-terms checklist. The calculator feeds each: the cost ranges anchor the alternative TCO, the cost sensitivity drives the negotiating posture, the cost case sits at the centre of the executive summary, and the modelled term-length scenarios drive the contract-terms commitments.
Customers who build the calculator early in the planning cycle (six to nine months ahead of renewal) have time to refine inputs, run sensitivities, and develop the downstream artefacts. Customers who build the calculator three months ahead of renewal use the calculator reactively, not strategically, and produce correspondingly weaker commercial outcomes.
Related reading
For deeper detail on adjacent topics, see the Broadcom VMware pricing pillar, VCF pricing analysis, per-core licensing mechanics, VCF licensing explained, Broadcom VMware discount structures, and our negotiating-Broadcom-pricing guide.