VMware Subscription Pricing 2026
The 2026 reference for VMware pricing: per-core list and realized rates for Cloud Foundation and vSphere Foundation, subscription terms, what Broadcom changed, and worked cost examples.
In 2026 VMware Cloud Foundation lists near $350 per core per year and vSphere Foundation near $135 to $190 per core per year, both subscription-only on one, three, or five-year terms, with a 16-core-per-CPU minimum and a 72-core minimum order. Realized VCF pricing commonly lands at $185 to $275 per core after discount, and the cheaper per-VM and per-socket editions are gone. This page is the 2026 reference for what each VMware bundle costs, what the terms are, what Broadcom changed, and where the negotiation room sits. Figures are advisory estimates and should be confirmed against a current quote.
Pricing is the output of the per-core count and the bundle choice, so this reference reads alongside our per-core licensing and Cloud Foundation licensing guides, and the broader VMware Broadcom licensing guide. For the deep VCF pricing breakdown see our VCF pricing 2026 reference.
The 2026 price snapshot
The numbers below reflect 2026 list pricing and typical realized bands. List is per physical core per year; realized reflects negotiated outcomes at enterprise scale.
| Bundle | List per core / year | Realized per core | Includes |
|---|---|---|---|
| VMware Cloud Foundation (VCF) | ~$350 | $185 to $275 | vSphere, vSAN, NSX, Aria |
| VMware vSphere Foundation (VVF) | ~$135 to $190 | $100 to $150 | vSphere, vCenter, limited vSAN, Aria Ops |
| vSphere Standard subscription | Discontinued | No renewal path | Retired by Broadcom |
| Standalone vSAN / NSX SKUs | Folded into bundles | n/a | No longer sold separately at scale |
The headline is the gap between bundles. VCF costs roughly twice VVF per core because it includes the full software-defined data center. Choosing the bundle that matches your deployed features is the largest pricing decision you make, larger than any discount, and it is covered in our vSphere Foundation pricing guide.
Subscription terms
VMware is now term-based only. Commitments run one, three, or five years, and the per-core rate falls as the term lengthens, trading flexibility for a lower rate. At term end, the right to run the software ends unless you renew, which is the structural change explained in our end of perpetual licenses analysis. There is no buy-once option and no maintenance-only mode.
| Term | Rate posture | Best for |
|---|---|---|
| 1 year | Highest per-core rate | Estates planning an exit or major change |
| 3 year | Moderate reduction | Most stable production estates |
| 5 year | Lowest per-core rate | Committed, long-horizon estates |
The term choice is a bargaining decision, not only a discount decision. A one-year term keeps an exit option open at a higher rate; a five-year term locks the lowest rate but removes your flexibility and your renewal position for the duration. Match the term to your exit posture, not just to the headline saving.
What Broadcom changed
The 2026 pricing reflects a deliberate restructuring. Broadcom retired perpetual licenses, consolidated dozens of SKUs into two main bundles, moved to per-core metering, raised the per-CPU and per-order minimums, and discontinued the entry-level vSphere Standard subscription with no renewal path. Each change individually raised cost for some segment; together they produced the renewal quotes that drove the market to evaluate alternatives.
The discontinuation of vSphere Standard subscription is the trap for small estates. Customers whose Standard subscription expires in 2025 or 2026 cannot renew it; their only VMware path forward is VVF or VCF, both more expensive. For those estates, the exit options are often more attractive than the forced upgrade.
Negotiation lever: Multi-year commitments and large core counts open the deepest discounts, but only against competing quotes. Realized VCF pricing below $200 per core generally requires both a multi-year term and a credible alternative on the table. On orders above 200 cores, request quotes from at least three resellers and model the three-year and five-year terms side by side, because the lowest sticker rate is not always the lowest total once flexibility is priced in.
Cost examples
The examples below combine the per-core rate with realistic core counts to show annual subscription cost. They assume billed cores after the minimums are applied.
| Estate | Billed cores | VCF list / year | VVF list / year |
|---|---|---|---|
| Small (2 dense hosts) | 72 | ~$25,200 | ~$9,720 to $13,680 |
| Mid (4 hosts x 2x 24-core) | 192 | ~$67,200 | ~$25,920 to $36,480 |
| Large (8 hosts x 2x 32-core) | 512 | ~$179,200 | ~$69,120 to $97,280 |
These are list figures; apply your negotiated discount to reach the real number. The examples make the bundle gap concrete: at every size, VVF costs less than half of VCF, which is why the bundle-fit check belongs at the front of any renewal negotiation.
Add-on and edition pricing beyond the core bundles
The two headline bundles do not capture the full bill. Several costs sit outside the per-core subscription and are easy to miss when comparing VCF and VVF on rate alone. Additional vSAN capacity beyond the bundled allowance is priced separately and matters for storage-dense estates. Certain advanced NSX and Aria capabilities carry their own entitlements. And support tier upgrades, beyond the standard support included in the subscription, are a quotable add-on that some enterprises require for production-critical estates.
| Add-on | When it applies | Cost posture |
|---|---|---|
| Additional vSAN capacity | Storage beyond the bundled allowance | Per-capacity, on top of per-core |
| Premium support tier | Faster response, dedicated contacts | Uplift on subscription |
| Advanced add-on modules | Features beyond the base bundle | Separately entitled |
| Extended lifecycle support | Older releases past standard support | Premium, time-limited |
Model these against your actual requirements before signing, because an add-on assumed to be included can turn a competitive per-core rate into an uncompetitive total. The discipline is the same one in our Cloud Foundation licensing guide: price the full deployment, including storage and support tiers, not just the core subscription.
How discounting actually works
VMware list pricing is a starting point, and the path from list to realized price runs through the partner channel and the size and shape of your commitment. The largest discounts attach to multi-year terms, high core counts, and competitive situations where Broadcom is defending against an alternative. Smaller estates on one-year terms see the least movement, while large multi-year commitments with a credible alternative on the table see the most.
The channel structure means your reseller matters. Because VMware is sold through partners, different resellers quoting the same Broadcom SKUs can return materially different numbers depending on their margin and their relationship with the account. Requesting quotes from at least three resellers exposes that spread and gives you a defensible benchmark, which is the single most reliable way to test whether a quote is competitive.
Discounts also move with timing. Broadcom, like most vendors, has quarter and year-end pressure that opens room near period close, so aligning your decision window with the vendor's fiscal calendar can capture an additional increment. Combine timing, term, volume, and competition deliberately rather than one at a time, and run the whole approach through a structured renewal negotiation so the levers reinforce each other instead of being spent piecemeal.
Forecasting and budgeting VMware cost
Because VMware is now a recurring subscription rather than a capitalized purchase, it belongs in the operating budget and the multi-year forecast, not in a one-time capital line. The shift changes how finance should treat it: the cost recurs every year, rises with the estate, and resets at each renewal, so a forecast that assumes a flat line will be wrong. Build the forecast from the per-core rate, the billed core count, and the term, then layer in the expected growth and the renewal repricing.
Model the renewal cliff explicitly. A multi-year term locks a rate, but when it ends the estate reprices at then-current rates, which have trended upward, so the forecast should include a step-up at each renewal boundary rather than a smooth extrapolation. Estates that budgeted only the locked term and ignored the reset were the ones most surprised by the post-Broadcom renewals, and the lesson is to carry the reset in the model from the start.
Separate the controllable from the fixed in the forecast. The per-core rate is partly controllable through negotiation, term, and competition; the core count is controllable through host design and bundle fit; the renewal timing is controllable through planning. Forecasting these levers, rather than treating the whole bill as fixed, turns the budget into a plan with intervention points, each tied to the actions in our renewal negotiation and per-core licensing guides.
Revisit the forecast at every hardware refresh and every acquisition. Both events change the core count and therefore the bill, and both are easier to absorb when the forecast anticipates them than when they arrive as a surprise true-up. A maintained forecast is also the document that wins budget for an exit when the recurring cost crosses the threshold where migration pays.
Compare price on total cost of ownership, not the per-core rate alone. Two quotes at the same per-core number can differ sharply once the bundle fit, the add-on storage, the support tier, and the term are accounted for, so the rate is only the first column in the comparison. The buyer who evaluates the all-in annual cost per workload, across the full term, sees the real picture that a rate-only comparison hides.
Watch the direction of travel as well as the current number. Broadcom's pricing has moved in one direction since the acquisition, and a budget or a decision that assumes today's rate will hold is fragile. Treat the current price as a point on a rising line when you forecast, and let that trajectory inform whether a longer locked term or a shorter, more flexible one serves you better, the same judgment our renewal guide applies to term length.
Finally, price the alternative alongside the quote. The clearest way to know whether a VMware price is competitive is to hold it against the cost of a migration to Proxmox or Nutanix over the same horizon. When the subscription cost approaches or exceeds the all-in cost of leaving, the pricing has answered the exit question for you.
Common questions
What does VMware cost per core in 2026?
VMware Cloud Foundation lists near $350 per core per year and realizes $185 to $275 after discount. vSphere Foundation lists near $135 to $190 per core. Both are subscription-only.
Can I still buy perpetual VMware licenses?
No. Broadcom retired perpetual licensing. VMware is sold only as a term subscription on one, three, or five-year commitments.
What happened to vSphere Standard subscription?
Broadcom discontinued it with no renewal path. Estates whose Standard subscription expires must move to vSphere Foundation or Cloud Foundation, both more expensive, or evaluate an exit.
How do I get the lowest VMware price?
Combine a right-sized core count, the correct bundle, a multi-year term, and competing reseller quotes. Realized VCF below $200 per core generally requires both a multi-year commitment and a credible alternative.