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.
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
- Nutanix Hardware Platform Spec Sheets - all NX and OEM platform data
- Nutanix Cloud Infrastructure (NCI) datasheet - editions, metrics, limits
- Nutanix licensing & software options - NCI, NCM, NUS, NDB, NKP metrics
- Nutanix best-practice guides for SQL Server (BP-2015), Oracle (BP-2000) and the Hybrid Cloud Reference Architecture
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
| Workload | Use case | Source | VMs | vCPU/VM | RAM GB/VM | Disk GB/VM | Used % | IOPS/VM | vCPU:core | Total vCPU | Cores | Total RAM | Data 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.
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.
Resiliency
Oversubscription & headroom
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.
Storage policy
Growth & hypervisor
Features in scope
These drive the NCI edition recommendation on the Licensing tab.
Hardware platform
Platform catalogue
Node configuration
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
VLAN plan
| VLAN ID | Purpose | Subnet | MTU | Notes |
|---|
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
NCI edition comparison
How the node count was derived
Storage capacity model
Design policy & assumptions
Growth projection
Physical connectivity
Logical architecture
Rack elevation
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.