The comparison is intended to set out, on a single page, the contractual and commercial differences between the legacy perpetual licensing model that buyers signed under VMware prior to the Broadcom acquisition and the subscription model that has replaced it under VCF. The table presents the dimensions that buyers most often need to reconcile inside an internal cost case. Numbers are sourced from the master plan and from comparable signed contracts inside the Desk's verified contract data. No opinion is offered on which model is preferable for any given buyer. That conclusion depends on the buyer's workload mix, term horizon, capital versus operating treatment preference, and contractual flexibility requirements.
The reader should treat the table as a starting point for the internal comparison, not as an ending. Buyer specific economics, including the unamortised perpetual asset position, the support contract status, and the projected hardware refresh schedule, are not captured here and materially shift the calculation in either direction depending on the buyer.
| Dimension | Perpetual licensing (pre acquisition) | VCF subscription (current) |
|---|---|---|
| Licensing unit | Per CPU socket. License entitlement permanent at point of purchase. Support contract separate and renewable annually. | Per CPU core. Annual minimum 16 cores per CPU. Subscription term typically three or five years. Support included in the subscription. |
| Capital treatment | Capitalised asset on the buyer's balance sheet. Amortised across the useful life. Operating expense limited to the annual support fee. | Operating expense in full. No capitalised asset. Subscription fee recognised across the contracted term on a straight line basis. |
| Headline list pricing | $4,200 per socket typical large enterprise list at last legacy refresh cycle. Volume discount band 25 to 45 percent on signed contracts of comparable scale. | $350 per core annual headline rate at retail enterprise list. Negotiated rates observed in signed contracts inside the Desk's verified data range from $145 to $260 per core annual at large enterprise scale. |
| Minimum commitment | No minimum core count per CPU. License paid against actual socket count deployed. | 16 core annual minimum per CPU under VCF subscription terms. Cores deployed below 16 still priced as 16. |
| Bundled scope | Components priced separately. vSphere, vSAN, NSX, Aria each carried distinct SKU lines with distinct entitlement counts. | VCF bundle includes vSphere, vSAN, NSX and Aria operations in a single subscription. Tanzu modules priced as add on. Aria automation tier separated as add on at some contract bands. |
| Renewal economics | Renewal applied to the support contract only. Underlying license entitlement carried forward at no incremental cost. Support uplift typically 8 to 12 percent year over year. | Renewal applied to the full subscription. Trajectory uplift on standing renewal models in 2026 observed at +25 to +51 percent against the prior period on like for like scope, before negotiation. |
| Audit posture | Audit focused on socket count compliance against entitlement records. Deployment drift typically resolved with paid true up at list less standard volume discount. | Audit focused on core count compliance against the subscription entitlement and on bundled component usage compliance. True up priced at subscription rate, not at residual perpetual rate. |
| Exit cost profile | Owned license remains usable in the absence of a support contract. Buyer retains operational continuity at a reduced cost profile if the support contract is dropped, subject to security and patch posture risk. | License entitlement ceases at the end of the subscription term unless renewed. Continued operation requires either renewal, migration to an alternative platform, or transition to a perpetual hold arrangement where one is available. |
| Contractual flexibility | Scope changes mid term typically resolved through purchase of additional perpetual licenses at the prevailing volume rate. Scope reductions not refundable but recoverable through subsequent support contract reduction. | Scope changes mid term resolved through contract amendment. Subscription scope reductions typically not permitted mid term. Scope increases priced at the standing per core rate. |
| Most favoured customer treatment | Rarely contracted in perpetual paper. Volume discount bands published at vendor schedule and applied uniformly. | Available on negotiated subscription contracts at large enterprise scale. Most often scoped to a defined peer band rather than to all customers. |
The table presents the contractual and commercial dimensions that distinguish the two models on a like for like scope basis. It does not capture the buyer specific economics that determine which model produces a lower total cost of ownership for any given enterprise. The unamortised perpetual asset position carried into the renewal conversation, the hardware refresh schedule that determines whether the next refresh cycle creates a natural exit window, and the operational risk profile of running on a perpetual license without support are all material to the comparison and all buyer specific.
Buyers comparing a perpetual hold against a subscription transition should construct the comparison on the buyer's own data, against a defined five year horizon, with the perpetual hold scenario priced including the security and operational risk premium of running without vendor support. The Desk's experience on signed contracts inside the verified data is that the subscription model produces a lower total cost on a five year horizon when the buyer's workload mix supports the bundled scope and when the buyer can negotiate the per core rate inside the lower half of the observed range. Where the buyer's workload mix uses only a subset of the bundled components, the comparison shifts toward the perpetual hold for the components that are not actively used.
The Desk publishes this comparison in its evenhanded form and does not offer a recommendation on either side. Buyers seeking a recommendation for their specific contract should refer to the renewal negotiation service or to the relevant case studies for the workload profile closest to their own.