Project

Identify the engagement and the document metadata

Sign in

Sign in to save sizing projects to the portal and pick them up on any machine.

Create an account

Accounts are stored in the portal's own database. Passwords are hashed with PBKDF2-HMAC-SHA256 and never stored in plain text.

At least 10 characters, mixing at least three of: lower case, upper case, digits, symbols.

Configuration file (XML)

Export the whole sizing - project details, use cases, workloads, cluster policy, hardware, network and licensing - as a portable XML file, and import it again here or on another machine. Works with or without the portal.

Preview the XML for the current sizing

          

Project details

These fields populate the cover page and headers of the Word, Excel and PowerPoint deliverables.

How this sizer works

Every hardware specification, licensing rule and design rule used by this tool is taken from official Nutanix sources. Nothing is invented.

Sizing method

  • CPU, memory and storage are sized independently; the cluster takes the largest node count.
  • Every dimension is sized N+<failure tolerance> so a failed node's VMs restart and its data re-protects.
  • Storage runs workload data through data-efficiency assumptions, snapshot reserve, replication factor and the utilisation ceiling.
  • The result is validated against Nutanix minimums (RF2/RF3 node counts, EC-X node counts, CVM NUMA fit, edition limits).

Official sources used

Select the use cases in scope

Each use case carries its own Nutanix sizing profile - oversubscription ratios, CVM allocation, headroom, data-efficiency assumptions and best practices. Selecting more than one blends the profiles conservatively.

Workloads

Add one row per workload profile. Growth is applied on the Cluster policy tab.
WorkloadUse caseSource VMsvCPU/VMRAM GB/VM Disk GB/VMUsed %IOPS/VM vCPU:coreTotal vCPUCores Total RAMData TiB

Import an RVTools export

Drop an RVTools .xlsx (or a vInfo CSV) here. The vInfo sheet is read for CPUs, Memory, Provisioned and In Use capacity, then classified into Nutanix use cases and turned into workload rows.

Drop RVTools file here, or click to browse .xlsx / .xls / .csv - the vInfo sheet is used

Raw capacity requirement

Use this when you have been given headline numbers rather than a VM inventory: total physical cores, total memory and total usable storage. It is added as an extra workload row.

Physical cores, not vCPU. Enter 0 if compute is covered by the workload table.
Usable capacity as the customer sees it, before replication.

Resiliency

RF3 requires NCI Pro or higher.

Oversubscription & headroom

Use-case default. 1-2:1 for tier-1 databases, 4:1 general server, 6:1 VDI knowledge workers.
AHV does not overcommit memory by default - keep at 1.0 for production.

Controller VM

Nutanix default is 12 vCPU / 32 GB, rising to 16 vCPU / 64 GB for storage-heavy database nodes. All CVM vCPUs must fit inside one physical socket.

1.0 charges every CVM vCPU against the physical core pool (the conservative default).

Storage policy

Nutanix flags Data Resiliency critical when free space falls below rebuild capacity.
AOS metadata, oplog, Curator working space, drive formatting.
Assumed ratio
VDI / backup only
NCI Pro+, 4 nodes min
Data-efficiency ratios are planning assumptions, not guarantees. Validate against a real sample or a Nutanix Collector run before ordering.

Growth & hypervisor

Features in scope

These drive the NCI edition recommendation on the Licensing tab.

Hardware platform

Choose Nutanix NX appliances or an OEM platform. Every model, its CPU options, maximum memory, storage type, form factor and maximum raw capacity come from the official Nutanix Hardware Platform Spec Sheets.

Platform catalogue

Node configuration

0 = size automatically.

Top-of-rack switching

Nutanix is switch agnostic - any standards-based switch meeting the Nutanix networking requirements is supported. Pick the model you intend to quote so the cabling plan and BoQ are accurate.

Node connectivity

Split evenly across the two ToR switches.
10 GbE is the practical minimum; 25 GbE+ for all-flash / NVMe.

VLAN plan

Edit to match the customer's addressing. Included in the logical diagram and every export.
VLAN IDPurposeSubnetMTUNotes

Licence selection

Add-ons

Add-ons extend NCI Pro with capabilities that are otherwise native to NCI Ultimate, or add a separate Nutanix product.

Licence line items

Nutanix does not publish list pricing. This tool produces quantities and metrics only - your Nutanix account team or partner adds commercials.

NCI edition comparison

How the node count was derived

Storage capacity model

Design policy & assumptions

Growth projection

Physical connectivity

Node-to-ToR cabling, switch redundancy, uplinks to the core and the out-of-band network.

Logical architecture

CVMs, hypervisor, distributed storage fabric, containers, virtual switch and VLANs.

Rack elevation

Chassis, switches and rack units consumed.

Generic bill of quantities

Placeholder SKUs with real quantities. Confirm exact part numbers with the vendor or distributor. No pricing is included - Nutanix does not publish list prices.

Export the deliverables

All three documents are generated in the browser from the same report model, so they always tell the same story. Charts and diagrams are embedded as images.

Word

Full design document - cover page, contents, executive summary, sizing derivation, capacity model, platform, network design, both diagrams, licensing, growth, best practices, BoQ and sources.

Excel

Workbook with one sheet per section - summary, workloads, sizing logic, design policy, capacity, platform, growth, licensing, network, BoQ, best practices, validation and sources.

PowerPoint

Executive deck - cover, summary KPIs, requirements, node-count rationale, capacity, platform, physical and logical diagrams, network, licensing, growth, best practices and BoQ.

Project file

Save the whole sizing as JSON to reopen or share later.

Sources