VMware vSphere cost vs self-hosted XCP-ng

Which cost components change when you move from vSphere to XCP-ng

This table sets each vSphere cost component against its XCP-ng equivalent and marks whether it is paid once or recurs. Use it to build a like-for-like quote request, since the commercial side is set by per-core subscription terms and the self-hosted side is set mostly by support choices and staff time. The main takeaway is that the license line moves to zero for XCP-ng, while support, storage and migration effort stay as costs you must price explicitly.

What moves the vSphere versus XCP-ng comparison

Six factors decide whether XCP-ng fits a given estate and what the migration costs in people and time. Several of them interact: host count sets which Vates plan is relevant, and storage choice determines whether XOSTOR is an added line item or unnecessary. Work through them together before requesting quotes.

How the VMware subscription stack adds up per host

How to build the cost model with your own numbers

This sequence turns a vague renewal concern into a three-year cost model built from your own hosts, contract terms and migration waves, so you can compare Broadcom subscriptions with self-hosted XCP-ng on equal terms. The output is a written model and a scope that vendors and partners can quote against.

1. Inventory hosts, sockets and cores

   Your infrastructure or virtualization team lists every ESXi host with its physical CPU socket count, cores per socket, and whether it runs production, test or disaster recovery workloads. Record the cluster each host belongs to, the storage it uses (vSAN, SAN or NFS), and the VM count per host. Broadcom's current subscriptions are licensed per core with a 16-core minimum per CPU, so core counts per socket drive the license quantity more than socket count alone. Done when every host appears in one spreadsheet with its core count and cluster, and someone outside the team has checked the totals against the hypervisor's own inventory.

2. Record the current contract and renewal date

   Procurement or the licensing owner pulls the current VMware agreement, including the product edition, the subscription term, the core count licensed, the renewal date and any add-on modules such as vSAN or Aria. Confirm with your Broadcom reseller which offering (VVF or VCF) your renewal maps to, because Broadcom sells vSphere Enterprise Plus, vSAN and NSX only inside those bundles. Note any support contract dates separately. Under Broadcom's published rules, hosts on perpetual licenses keep running after support expires, but new patches and major upgrades need an active contract. Done when the renewal figure, term and entitlement are recorded in writing and linked to the host inventory.

3. Select the XCP-ng support tier per host or none

   Decide whether each host needs commercial support, and from which tier. XCP-ng and Xen Orchestra are open-source with no license fee, and Vates describes commercial support subscriptions as adding SLAs. Vates lists VMS plans at $2,000 per year for Essential and $4,000 per year for Essential+ for up to 3 hosts, Pro at $1,000 per host per year with a 3-host minimum, and Enterprise at $1,800 per host per year with a 4-host minimum and 24/7 support, per its pricing and support page. Confirm current figures on that page, since they can change. Model one scenario with no support and one with the tier that matches your uptime and staffing needs. Done when each scenario has a dollar line per year, labeled with its source and date checked.

4. Price storage: XOSTOR or existing SAN

   Compare two storage paths. If you keep an existing SAN or NFS array, the cost is mainly the connectivity and support you already pay. If you replace vSAN, the Vates pricing page lists XOSTOR hyperconverged storage at $800 to $1,200 per host per year, so multiply by host count for each scenario. Ask the vendor whether XOSTOR is licensed per host or per capacity, and what hardware minimums apply. Add the replication and failure-domain design work that a hyperconverged layout requires. Done when storage appears as a separate line with two columns, existing array and XOSTOR, and each column shows the recurring cost per year.

5. Estimate migration waves with Xen Orchestra V2V

   Group VMs into waves by business owner, criticality and dependency, then estimate effort per wave. Xen Orchestra's V2V tool performs a warm migration: it replicates disks while the source VM runs, then syncs changed blocks after shutdown, and needs HTTP access to the ESXi API. The XCP-ng migration documentation states that current Xen Orchestra versions do not support V2V from ESXi 6.x, so confirm your ESXi version first. Treat the cutover window, rollback plan and application testing as the main effort drivers, not the copy itself. Done when each wave has a VM list, an owner, a cutover approach and a staff-hour estimate written by the team that will do the work.

6. Add staff time for backup, networking and training

   Add the one-time and recurring labor that a license comparison often omits. Backup jobs in vSphere must be rebuilt for the Xen Orchestra backup model, and virtual switch and VLAN configuration must be recreated on XCP-ng pools. Include training for administrators who know vCenter, plus time for runbooks and monitoring integration. Ask whether the work will be done in-house, by a partner under a fixed-scope written agreement, or through a retainer. DeployOpen plans and implements these components on a fixed-scope basis, and it does not publish prices, so request a written quote against your scope. Done when each labor line has a role, an hour estimate from the owner of that role, and a note on whether it is one-time or recurring.

7. Set a three-year view with one-time and recurring costs

   Build a three-year table with two sections: one-time costs (migration labor, hardware refresh if needed, training, initial configuration) and recurring costs (support plans, XOSTOR or storage fees, staff time for operations, backup storage). Run the current Broadcom renewal path and the XCP-ng path in parallel, and include a row for keeping perpetual hosts running after support expires, with the security patching cost that carries. Mark which costs drive the result most, such as core count, host count and support tier, and test the table with two sensitivity cases. Label any hypothetical figure as illustrative. Done when the finance and infrastructure leads have reviewed the same table and agreed which assumptions are fixed.

8. Request quotes against a written scope

   Send the same written scope to every vendor, partner and reseller you consider, so their quotes are comparable. The scope should list the host inventory, the storage design, the migration waves, the support tier you want, the backup and networking components, the training requirement and the acceptance tests. Ask each provider to quote each component separately, state what is one-time and what recurs, and name the assumptions behind each line. Ask for the renewal terms, the support SLA definitions and the exit terms. Done when you hold at least one quote per component that matches the scope document, and the model's inputs can be traced to a written source.

How migration effort changes by estate type

Costs teams forget on each side

The license line is the number most teams compare first, but it rarely decides the total. Costs on both sides tend to sit in patches, support tiers, tooling and the operator hours that keep a migration moving, and each one changes the comparison.

Questions buyers ask about vSphere and XCP-ng costs