Nutanix cost vs self-hosted XCP-ng: where the money actually goes
If you are facing a Nutanix renewal or a per-core quote, XCP-ng and Xen Orchestra carry no license fee, so the comparison is not about software price. It turns on your Nutanix subscription terms, whether you buy optional Vates support per host, which storage you choose (XOSTOR or another option), and the one-time migration and staff effort. Nutanix Cloud Infrastructure is sold as term subscriptions of 1 to 5 years, licensed on physical CPU cores and portable across supported hardware, in Starter, Pro and Ultimate editions. Your actual Nutanix figure must come from your own quote, because it depends on core count, edition, term and any separately licensed storage or security add-ons. Ask the vendor to itemize each of these lines so you can compare them component by component.
On the XCP-ng side, the recurring cost is whatever support you choose. Vates describes the hypervisor and Xen Orchestra as open-source projects with no limits and no license fees, with commercial support subscriptions adding SLAs. Its published VMS plans are Essential at $2,000 per year and Essential+ at $4,000 per year 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. XOSTOR hyperconverged storage is an add-on priced at $800 to $1,200 per host per year. Confirm with Vates which plan and host count apply to your estate, and whether XOSTOR is needed at all if you already have shared storage. Support is optional, so an internally staffed team may choose a lower recurring spend and accept more operational responsibility.
The one-time costs are where estimates often go wrong. Plan for the effort to export VMs from Prism Central, import them with Xen Orchestra's V2V tool (which warm-migrates from ESXi 7 and later, not ESXi 6.x), validate guest tools removal and boot settings, and rebuild backup jobs. Also budget staff time to learn XAPI and Xen Orchestra operations and to test failover before cutover. Ask any partner for a written scope with deliverables and timelines before work starts, and ask Vates to confirm the XCP-ng 8.3 LTS support window, which runs until November 30, 2028, against your planned hardware refresh. Those dates, not the license line, usually decide whether the move pays back.
Which cost components differ between Nutanix and XCP-ng
This table compares the cost components of Nutanix NCI with XCP-ng and Xen Orchestra, row by row, so you can see who is paid for what and which costs are one-time or recurring. Read each row against your own renewal quote, because the commercial side depends on core counts, edition and storage terms that only your quote confirms. The main takeaway is that XCP-ng removes the hypervisor license fee, but support, storage and staff effort remain costs you must budget for.
| Cost component | Nutanix (NCI and add-ons) | XCP-ng (self-hosted) |
|---|---|---|
| Software license or subscription | NCI term subscriptions of 1 to 5 years, licensed per physical CPU core and sold in Starter, Pro and Ultimate editions. Recurring. | No license fee for XCP-ng or Xen Orchestra. Commercial support is optional and sold separately by Vates. Recurring only if you buy support. |
| Storage licensing | Nutanix storage is bundled in NCI, but other storage features such as Nutanix Files and Objects are licensed separately. Recurring. | XOSTOR hyperconverged storage is a Vates add-on priced per host per year. Otherwise you choose and pay for storage hardware and software, often at no license cost. |
| Hardware | Nodes must be Nutanix-supported hardware in most setups. One-time purchase or lease, plus refresh cycles. | Runs on a wide range of standard x86 servers, so existing nodes may be reusable. Confirm hardware compatibility with the XCP-ng hardware list before reuse. |
| Migration | Move is free for Nutanix customers and migrates VMs to AHV, but it is the destination side that carries your effort. One-time. | Xen Orchestra V2V migrates VMs from ESXi 7 and later with warm migration. Earlier ESXi 6.x hosts are not supported. Effort is one-time and driven by VM count and data size. |
| Vendor support | Included in NCI subscription terms. Recurring with the subscription. | Vates VMS plans: Essential at 2,000 USD per year and Essential+ at 4,000 USD per year (up to 3 hosts), Pro at 1,000 USD per host per year, Enterprise at 1,800 USD per host per year with 24/7 support (Vates pricing page). Recurring. |
| Upgrades and patches | Covered by the subscription. Recurring within the term. | XCP-ng 8.3 LTS is supported until November 30, 2028. Upgrade effort is your team's time unless you buy a retainer or Vates support. One-time per cycle. |
| Internal skills and operations | Prism-based operations are familiar to many teams, with less Linux or Xen work. Recurring staff time. | Staff need Xen, XAPI and Xen Orchestra skills. Training and cross-training are one-time costs, and ongoing operations are recurring staff time. |
| Backup tooling | Backup is priced and delivered through Nutanix tooling or third-party products, depending on your contract. Confirm the terms in your quote. Recurring. | Xen Orchestra includes backup features, and you choose any other tools. Ask Vates which backup features need a paid plan before you assume they are included. |
What moves the Nutanix versus XCP-ng comparison
Nutanix and XCP-ng price the same workload on different units, so the comparison turns on how many cores, hosts and years you actually need. The cards below are the inputs to check before you request a quote from either side.
Core count versus host count
Nutanix NCI terms are licensed on physical CPU cores, so total cores across every node drive the subscription. Vates Pro is priced per host with a 3-host minimum, and Enterprise is per host with a 4-host minimum, so a few large hosts and many small hosts produce very different bills. Count nodes and cores for the target cluster, then ask Vates which tier and host minimum apply to that count.
Term length and renewal timing
Nutanix sells NCI as term subscriptions of 1 to 5 years, so the length you pick sets the annual cost and the point at which you must decide again. Vates support is also an annual commitment per host. Model both terms over the same planning horizon and align renewal dates with your hardware refresh.
Nutanix edition selection
NCI is offered in Starter, Pro and Ultimate editions, and each edition bundles a different feature set. Choose the edition that matches the features you use today, such as microsegmentation or advanced data services, and price any add-on you would otherwise need. Ask Nutanix to list which features each edition includes for your exact hardware, so the comparison does not rely on feature assumptions.
Availability and 24/7 support
Vates Enterprise includes 24/7 support, while lower tiers differ in response commitments. Decide whether your production estate needs around-the-clock cover and a contractual SLA, or whether an internal on-call team can absorb incidents. Put the support hours and response targets into the written quote, because they are the largest recurring line after hardware.
Storage capacity and XOSTOR need
Nutanix storage is bundled into the hyperconverged platform, while XCP-ng needs a storage choice. XOSTOR is a Vates add-on priced per host per year, and it is not required if you already run a SAN or NFS backend. Measure usable capacity, replication factor and growth, then decide whether XOSTOR, existing storage or another option fits.
In-house Xen and XAPI skills
XCP-ng runs the Xen hypervisor, dom0, the XAPI toolstack and QEMU, so operators need to understand that stack when they troubleshoot. Nutanix teams already work in Prism, so the retraining effort is a real staffing cost. Ask who will run upgrades, backups and incident response, and whether Vates support or an implementation partner will cover the gap during the first year.
How to build the comparison with your own numbers
This sequence turns a vague renewal question into a side-by-side total for Nutanix and XCP-ng over the same 3 to 5 year horizon, so every line has a source and every assumption is visible.
Pull the current Nutanix quote per core and term
Ask your Nutanix partner or reseller for a written quote that lists the NCI edition (Starter, Pro or Ultimate), the number of physical cores covered, the term length in years from 1 to 5, and any separately licensed add-ons such as storage or security features. Confirm whether the quote covers Prism Central, Nutanix Move and support, and whether a renewal discount applies to the second and later years. The output is a single line per cost item with its annual and term totals, so you can compare it year by year.
List hosts and cores for a 3 to 5 year horizon
Build an inventory of every node you expect to run in each year of the horizon, including the current cluster, planned expansion and any hosts you expect to retire. For each host, record the physical core count, memory, storage capacity and the year it enters or leaves service. Check the core count you will license against the Nutanix quote so both models use the same hardware base. The output is a host table by year that drives every later line.
Price Vates support tiers for the host count
Take the host counts from your table and apply the Vates VMS pricing from its pricing page. Essential is listed at $2,000 per year and Essential+ at $4,000 per year 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. Calculate each tier for your host count at each year, then note that the XCP-ng hypervisor and Xen Orchestra carry no license fee, so support is an optional line you can drop. Confirm current figures with Vates before you rely on them.
Choose the storage option and price it
Decide how the VM disks will be stored. If you want hyperconverged storage on the same nodes, price XOSTOR, which Vates lists at $800 to $1,200 per host per year, and multiply by the host count for each year. If you prefer shared storage such as an existing SAN or NFS array, or a separate storage platform, record its hardware, support and staff lines instead. The output is one storage line per year, labeled with the option you chose, so the Nutanix storage cost can be compared against it on equal terms.
Add hardware refresh, migration and staff time
Add one-time lines for hardware you must buy, the migration effort, and any training. Include the OVA export from Prism Central, the import into XCP-ng with Xen Orchestra, guest tool removal and backup setup. Add recurring lines for the staff hours that run the platform each month, and for backup software or storage if they are not already in your estate. Mark every line as one-time or recurring and state who is paid for it, whether your own team, a vendor or an implementation partner. Ask for written scope and timing from any partner before you enter a figure.
Compare totals and test sensitivity to host count
Sum the one-time and recurring lines for each option across the same horizon, then show the cumulative cost by year. Rerun the comparison with one more host and one fewer host to see how the gap moves, since per-core Nutanix terms and per-host Vates tiers scale differently. Also run a case with and without Vates support, because support is optional. The output is a short table of totals and a sensitivity range that shows where the decision changes.
What a migration into XCP-ng costs in effort
The one-time cost of moving into XCP-ng is mostly staff time for planning, testing and cutover, and the size of that work depends on how your VMs leave Nutanix. Xen Orchestra's V2V tool warm-migrates VMs from ESXi 7 and later by reading the source over HTTP access to the ESXi API, which is a useful path only if you first place Nutanix workloads on a VMware host. For AHV estates the more typical route is OVA export from Prism Central, so the effort drivers are the per-VM steps that follow: removing Nutanix guest tools, checking whether each guest boots with BIOS or UEFI firmware, and confirming the disk and network devices the guest expects. Ask your migration partner to inventory these items per VM before any cutover date is set.
Storage repository planning is the decision that most shapes the schedule. XCP-ng hosts consume storage through repositories, and XOSTOR, which Vates sells as an add-on, is a separate purchase from the hypervisor itself. Decide early whether imported disks land on local storage, NFS, iSCSI or XOSTOR, because that choice determines how much data must be copied twice and how backups are scheduled in Xen Orchestra. Verify the source hypervisor you are importing from as well, since XCP-ng also documents imports from Hyper-V, KVM and VirtualBox and upgrades from XenServer and Citrix Hypervisor, but these paths do not apply to Nutanix AHV directly. Confirm the current V2V and OVA import behavior for your Xen Orchestra version in the XCP-ng migration documentation before you commit to a method.
Effort rises with the number of VMs that need custom drivers, licensed software tied to hardware identifiers, or application-level validation after import. It falls when you pilot a small group of representative guests, write a rollback plan for each wave, and keep Nutanix in place until backups in the new environment have been restored and tested. Ask any quote to itemize the inventory, pilot, per-wave cutover, validation and documentation as separate line items, state which tasks are assumed to be done by your own team, and name the Xen Orchestra and XCP-ng versions the work is scoped against. Note that ESXi 6.x hosts are not supported by current Xen Orchestra versions for V2V, so any VMware-sourced workloads in the estate need a separate check.
How the cost picture differs by estate size
A small estate with a few hosts is usually dominated by the one-time migration effort and staff time, not by license lines. On the Nutanix side, the recurring cost is the term subscription on physical cores plus any separately licensed storage or add-on features, and those figures scale with core count even when the cluster is small. On the XCP-ng side, the hypervisor and Xen Orchestra carry no license fee, so the recurring question is whether to buy Vates support per host, and whether the team will run it without a vendor contract.
- Subscription floor: Ask whether the Nutanix quote has a minimum term, minimum core count or minimum edition that applies even to a two- or three-node cluster.
- Support choice: Compare Vates support tiers against the cost of an internal on-call rota, since a few hosts rarely justify a dedicated support function.
- Migration labor: Estimate the hours to export from Prism Central, import, reinstall guest tools and validate backups, and ask who carries that effort.
- Hardware reuse: Confirm whether existing nodes meet the hardware and firmware requirements for XCP-ng before pricing new servers.
- Backup tooling: Ask whether Xen Orchestra backup features in your plan cover your retention needs, or whether a separate tool is needed.
Before accepting any quote, confirm the total cost over the planned term, including the migration scope, the support tier and the number of hosts that the quote assumes.
A mid-sized cluster that needs high availability and a support SLA moves the recurring cost lines toward subscriptions and storage. Nutanix bundles hyperconverged storage with the hypervisor, but the terms are priced per physical core and the storage capacity or feature tier may be licensed separately, so the bill grows with both compute and data. With XCP-ng, the recurring cost is the Vates support subscription per host, and the storage choice (for example, XOSTOR at the add-on price listed by Vates) becomes a separate line that must be sized with the cluster.
- Per-host support: Ask Vates to price each support tier against your actual host count and minimum host requirements, and confirm the SLA response times in writing.
- Storage line: Compare the Nutanix storage cost with XOSTOR per host and with a separately designed Ceph or NFS backend, including replica counts.
- Core count growth: Ask how the Nutanix quote changes if you add cores in year two, since core-based terms recur at renewal.
- Renewal timing: Align the decision with the Nutanix term end so that you are not paying for overlapping subscriptions during migration.
- Operations staff: Estimate the recurring hours for patching, upgrades and HA testing, and ask who owns them after handover.
Confirm whether the quote covers HA testing, upgrade assistance and backup integration, because those services drive the effort more than the license line in this profile.
Multi-site and regulated estates usually see the largest share of cost in evidence, documentation, testing and support coverage rather than license fees. Replication across sites, separated management networks and retention rules for logs and backups add recurring infrastructure cost on both platforms. A regulated organization also needs to show that the chosen platform is supported, patched and recoverable, which can make a vendor support contract a control requirement rather than a convenience. Nutanix offers its own multi-site features under its subscription terms, while XCP-ng sites need the replication, backup and monitoring design to be built and documented.
- Compliance evidence: Ask for the cost of producing change records, backup test reports and access reviews, and whether the quote includes them.
- Replication design: Price the inter-site links, replica storage and the failover testing schedule for each platform separately.
- Support obligations: Confirm whether your control framework requires a supported version, and check the XCP-ng 8.3 LTS support window against your planned go-live and refresh dates.
- Independent review: Budget for an independent auditor's review, since DeployOpen prepares evidence but auditors and certification bodies issue the reports.
- Exit and data portability: Ask how much it would cost to export data if you later leave either platform.
For regulated estates, request a quote that lists each control area, the evidence owner and the recurring test cycle, so the comparison reflects the work your assessors will actually review.
Nutanix cost and XCP-ng effort: common questions
Is XCP-ng really free to run?
The software itself carries no license fee. Vates describes the XCP-ng hypervisor and Xen Orchestra as open-source projects with no limits and no license fees, and XCP-ng is licensed GPL-2.0. What you still pay for is the hardware, network and storage, the staff who operate the platform, and any support subscription you choose to buy. Those costs recur through hardware refresh, staff time and optional support, so compare them line by line against your current Nutanix term renewal rather than against zero. Ask Vates or your reseller to confirm exactly which features each tier includes before you assume you can run without a support contract.
What does Vates support cost per host?
Vates lists its VMS plans on its pricing page. Pro is priced 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. Essential is $2,000 per year and Essential+ is $4,000 per year, each covering up to 3 hosts. The Pro and Enterprise figures scale with host count, so a larger cluster raises the recurring cost in a straight line. Confirm current pricing, what each tier covers and whether the minimums apply to your layout directly with Vates, since published figures can change.
Can our team migrate ourselves?
A team with Linux, Xen or KVM experience and a clear migration plan can often run the moves in-house, especially for a small set of non-critical VMs. Xen Orchestra's V2V feature warm-migrates VMs from ESXi 7 and later and needs only HTTP access to the ESXi API, and XCP-ng also documents imports from Hyper-V, KVM and VirtualBox. The harder work is usually the surrounding design: storage repositories, network mapping, backup targets, guest tools removal and cutover testing. If your staff have not run a hypervisor in production before, or the workloads are regulated, a fixed-scope implementation with a written deliverables list can cover that gap. DeployOpen plans, implements, integrates and documents self-hosted platforms in your environment under such scopes.
How long does a migration take and what drives it?
No supplied source gives a standard duration for a Nutanix to XCP-ng move, so treat any single number with caution and ask for an estimate based on your own inventory. The main drivers are the number of VMs, their disk sizes, how much data must sync during warm migration, whether guest tools need removing, the network and storage design you choose, and how many cutover windows your change process allows. Migrating from Nutanix usually means exporting VMs as OVA from Prism Central first, then importing them, and the BIOS or UEFI settings must be checked after import. Ask for a phased plan with pilot workloads, a rollback step and a list of the items you must approve before work starts.
Do we need XOSTOR?
Not necessarily. XOSTOR is the hyperconverged storage add-on Vates sells, priced at $800 to $1,200 per host per year according to Vates. It is one option among several, and you can run XCP-ng with other storage such as shared NFS or iSCSI arrays you already own. Choose XOSTOR when you want storage on the same nodes as compute, the vendor's support path for it, and a single subscription, and weigh that recurring per-host cost against the storage you would otherwise buy. Confirm with Vates the replication behavior, minimum node count and support boundaries before you size the cluster.
What does the work need from our staff?
Plan for people who can manage Linux hosts, networking, storage and backups, and who can work through the XCP-ng and Xen Orchestra documentation during a migration. Day-to-day operation covers patching hosts, watching backup jobs, managing storage repositories and handling upgrades, including the move between XCP-ng release lines. Ask who on your team will own patch approvals, on-call response and change records after handover. Where skills are thin, a retainer for ongoing support, upgrades and testing can cover the recurring work while your staff build experience.
When should we start relative to the Nutanix renewal?
Start planning before the renewal notice so you have options when the term ends. Nutanix sells NCI as term subscriptions of 1 to 5 years, so the length of your current term sets the date you must weigh against. A realistic plan begins with an inventory and a pilot well before renewal, so a decision is based on tested migration results rather than a deadline. Ask Nutanix for your term end date and renewal terms in writing, and check whether any service level or support you depend on lapses if you run a shorter parallel period. Keep in mind that Nutanix Move can move VMs to AHV, so compare that option during the same review.
When Nutanix still makes sense on cost
A Nutanix estate can cost less overall than a rebuild when the comparison is made on a full ledger rather than on license lines alone. Nutanix Cloud Infrastructure is sold as term subscriptions of 1 to 5 years, licensed on physical CPU cores, and the hyperconverged storage that many buyers would otherwise assemble separately sits inside that platform. Replacing it means paying for a new storage design, a Xen-side storage repository plan or a Vates XOSTOR add-on, validation of the new stack, and a period in which the old and new environments run side by side. If the current cluster is recent, adequately sized and already covered by a term that runs past the planned migration window, the recurring cost of staying may be lower in the near term than the one-time cost of moving. Confirm the remaining term, renewal date and any true-up or expansion terms in writing before comparing numbers. The skills side of the ledger matters as much. A team that already runs Prism, manages AHV upgrades and has documented runbooks for node failure and cluster expansion carries that knowledge at no line-item cost, but a move to XCP-ng with Xen Orchestra asks the same people to learn XAPI, the Xen Orchestra backup jobs, Vates support tiers and a new upgrade cadence tied to the 8.3 LTS support window. Ask who would carry the operational load during the first two quarters after cutover, and whether that work would be backfilled. Hardware is the other variable: nodes that are still inside their warranty and meet the workload profile can be reused for a new platform, which lowers migration cost, but nodes nearing end of life shift the balance toward a rebuild regardless of software cost. Before any decision, ask the Nutanix account team for a quote that lists each component separately: core count and edition, storage capacity, support level, and any add-ons such as Flow or Files. Then ask Vates for the matching per-host support tier and XOSTOR pricing. Have the internal team estimate its own hours for migration, testing and training, and record which assumptions depend on the renewal date. A rebuild decision holds up only when those numbers still favor it after the staff time is counted.
How DeployOpen scopes a fixed-price XCP-ng implementation
DeployOpen plans, implements, hardens, backs up and documents self-hosted platforms inside your own infrastructure, including XCP-ng with Xen Orchestra for teams weighing Nutanix cost against open-source options. Most engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts. Quotes follow from that written scope.
How we scope
- Inventory the Nutanix clusters, per-core subscription terms and separately licensed storage that the cost model must cover.
- Confirm which VMs are in the migration wave, including any VMs that depend on Nutanix guest tools or BIOS or UEFI settings.
- Agree in writing whether XOSTOR, Vates support per host or an external storage design is in scope for each cluster.
- Record the hardware, networking and backup assumptions behind every cost line so the quote can be compared like for like.
How we build
- Deploy XCP-ng 8.3 LTS hosts and Xen Orchestra in your cloud accounts, data centers or air-gapped networks as the written scope defines.
- Run warm V2V or OVA-based test migrations of representative VMs and record disk, boot and network results before cutover.
- Configure storage repositories, network mappings and Xen Orchestra backup jobs to match the recovery targets you agree in scope.
- Run security testing on management interfaces and API access, and document findings and remediation before production use.
How we hand over
- Deliver runbooks for host patching, storage repository management, backup restores and Xen Orchestra administration.
- Provide a migration register listing each VM, its source, target, cutover date and rollback path for your change records.
- Document the controls and evidence your compliance assessors will ask for, without issuing audit reports or certifications.
- Walk your operations staff through the handover so they can run the platform, and confirm the handover criteria in writing.
How we support
- Offer ongoing support, upgrades and continuous testing as a retainer after handover, scoped separately from the implementation.
- Plan upgrades around the XCP-ng 8.3 LTS support window, which runs until November 30, 2028, and confirm the next upgrade path in your retainer.
- Ask Vates which support plan and host count apply to your estate, since its per-host and SLA terms are separate from DeployOpen's work.
- Review backup restores and security test results on an agreed schedule so the platform stays documented as it changes.
