10 Things You Probably Didn’t Know About Nutanix

10 Things You Probably Didn’t Know About Nutanix

Nutanix is often described with a single word: HCI. That description is not wrong, but it is incomplete.

Over the last decade, Nutanix has evolved from a hyperconverged infrastructure (HCI) pioneer into a mature enterprise cloud platform that now sits at the center of many VMware replacement strategies, sovereign cloud designs, and edge architectures. Yet much of this evolution remains poorly understood, partly because old perceptions persist longer than technical reality.

Here are ten things about Nutanix that people often don’t know or underestimate.

1. Nutanix’s DNA is HCI, but the architecture has evolved beyond it

Nutanix was built on hyperconverged infrastructure. That heritage is important, because it shaped the platform’s operational model, automation mindset, and lifecycle discipline.

Over the last years, Nutanix deliberately opened its architecture. Today, compute-only nodes are a possibility, enabled through partnerships with vendors like Dell (PowerStore support for Nutanix is expected to enter early access in spring 2026, with general availability coming in summer 2026) and Pure Storage (for now). This allows customers to decouple compute and storage where it makes architectural or economic sense, without abandoning the Nutanix control plane.

This is Nutanix acknowledging that real enterprise environments are heterogeneous, and that flexibility matters.

2. A Net Promoter Score above 90

Nutanix has reported an NPS score consistently above 90 for several years. In enterprise infrastructure, that number is almost unheard of.

NPS reflects how customers feel after deployment, during operations, upgrades, incidents, and daily use. In a market where infrastructure vendors are often tolerated rather than liked, this level of advocacy is just unique and tells a story if its own.

It suggests that Nutanix’s real differentiation is not just technology, but operational experience. That tends to show up only once systems are running at scale.

3. Nutanix Kubernetes Platform runs almost everywhere

Nutanix Kubernetes Platform (NKP) is often misunderstood as “Kubernetes on Nutanix”. That is only partially true.

NKP can run on:

  • Bare metal
  • Nutanix AHV
  • VMware
  • Public cloud infrastructure

Nutanix Cloud Native Platform

NKP was designed to abstract infrastructure differences rather than enforce platform lock-in. For organizations that already operate mixed environments, or that want to transition gradually, this matters far more than ideological purity.

In practice, NKP becomes a control layer for Kubernetes. That is especially relevant in regulated or sovereign environments where infrastructure choices are often political as much as technical.

4. Nutanix has matured from “challenger” to enterprise-grade platform

It’s honest to acknowledge that Nutanix wasn’t always considered enterprise-ready. In its early years, the company was widely admired for innovation and simplicity, but many large organizations hesitated because the platform, like all young software, had feature gaps, stability concerns in some use cases, and a smaller track record with mission-critical workloads.

That landscape has changed significantly. Over the past several years, Nutanix has steadily strengthened every axis of its platform. From virtualization and distributed storage to Kubernetes, security, and operations at scale. The company’s most recent financial results show that this maturity isn’t theoretical. Fiscal 2025 delivered 18 % year-over-year revenue growth, strong recurring revenue expansion, and Nutanix added thousands of new customers, including over 50 Global 2000 accounts, arguably its strongest annual new-logo performance in years. 

What this means in practice is that many enterprises that once saw Nutanix as a “challenger” now see it as a credible and proven alternative to VMware, and not just in smaller or departmental deployments, but across core data center and hybrid cloud estates.

The old maturity gap has largely disappeared. What remains is a difference of philosophy. Nutanix prioritizes operational simplicity, flexibility, and choice, without compromising the robustness that large organizations demand. And with increasing adoption among Global 2000 enterprises, that philosophy is proving not only viable but competitive at the highest levels of IT decision-making.

5. The “Nutanix is expensive” perception is outdated and often wrong

The idea that Nutanix is more expensive than competitors is one of the most persistent myths in the market. It was shaped by early licensing models and by superficial price comparisons that ignored operational and architectural differences.

Today, Nutanix offers multiple licensing models, including options that other vendors simply do not have.

For example, NCI-VDI for Citrix or Omnissa environments is licensed based on concurrent users (CCU) rather than physical CPU cores. That aligns cost directly with usage and not hardware density.

Even more interesting is NCI Edge, which is designed for distributed environments with smaller footprints (aka ROBO). It is licensed per virtual machine, with clear boundaries:

  • Maximum of 25 VMs per cluster
  • Maximum 96 GB RAM per VM

Consider a realistic example. An organization runs 250 edge sites. Each site has a 3-node cluster with 32 cores per node and hosts 20 VMs:

  • A core-based model would require licensing 24’000 cores
  • With NCI Edge, the customer licenses 5’000 VMs

It fundamentally changes the cost structure of edge and remote deployments. In a traditional core-based licensing model, effective costs might range from $100 to $140 per core for edge nodes. With NCI Edge, the effective per-core cost can drop to $60-80 (illustrative figures). This is not a marginal optimization, it’s huge.

Note: NCM Edge is a product that provides the same capabilities as NCM for edge use cases. NCM-Edge is also limited to a maximum of 25 VMs in a cluster.

6. Almost 90% of Nutanix customers now use AHV

Nutanix has always been fundamentally about HCI and AOS (Acropolis Operating System). From the beginning, the value was never the hypervisor itself, but the distributed storage, data services, and operational model built on top of it. Over time, Nutanix came to a clear conclusion: The hypervisor should be a commodity, not the value anchor of the platform. Out of this thinking, the perception, and later the expression, emerged that AHV is “free”.

No photo description available.

Today, AHV has become the dominant deployment model in the Nutanix ecosystem, with an adoption rate of 88%. This matters for two important reasons. First, it disproves the assumption that customers need to be pushed or incentivized to move to AHV. Second, it demonstrates that AHV is trusted to run mission-critical workloads at scale, across enterprises and service providers.

7. Nutanix is 100% channel-led

Nutanix does not sell directly to customers (for sure there are some exceptions :)). It is a channel-led vendor, by design, and that decision fundamentally shapes how the company operates in the market. Hence, channel commitment at Nutanix is a structural principle.

Partners are not treated as a fulfillment layer or a transactional necessity. They are core to how Nutanix delivers value – from architecture design and implementation to day-two operations, managed services, and long-term customer success. As a result, Nutanix has built one of the strongest partner and service provider ecosystems in the industry, with clear incentives, predictable rules, and room for partners to build sustainable businesses.

This stands in sharp contrast to the current direction of some other infrastructure vendors, where channel models have become more restrictive, less transparent, and increasingly centered around direct control. In that environment, partners often struggle with margin pressure, reduced influence, and uncertainty about their long-term role.

Nutanix takes a different approach. By staying channel-led, it enables local expertise, regional sovereignty, and trusted delivery models, which are especially critical in public sector, regulated industries, and markets where locality and compliance matter as much as technology.

8. MST and Cloud-Native AOS show how far Nutanix has moved beyond classic HCI

Most people associate Nutanix AOS with hyperconverged infrastructure and VM-centric deployments. What is far less known is how deeply Nutanix has evolved its data platform to address multi-cloud and cloud-native architectures.

One example is MST (Multi-Cloud Snapshot Technology). MST enables application-consistent snapshots to be replicated across heterogeneous environments, including on-premises infrastructure and public clouds. Unlike traditional disaster-recovery approaches that assume identical infrastructure on both sides, MST is designed for asymmetric, real-world scenarios. This makes it possible to use the public cloud as a recovery or failover target without re-architecting workloads or maintaining a second, identical private environment. 

MST diagram

In parallel, Nutanix has introduced Cloud Native AOS, which brings enterprise-grade storage and data services directly into Kubernetes environments. Instead of tying storage to virtual machines or specific infrastructure stacks, Cloud Native AOS runs as a Kubernetes-native service and can operate across diverse platforms. This allows stateful applications to benefit from Nutanix data services, such as snapshots, replication, and resilience, without forcing teams back into VM-centric models.

Together, MST and Cloud-Native AOS illustrate an important point. Nutanix is not simply extending HCI into new form factors. It is re-architecting core data services to work across clouds, infrastructures, and application models. These capabilities are often overlooked, but they are strong indicators of where the platform is heading — toward data mobility, resilience, and consistency across increasingly fragmented environments.

EKS Cluster

9. Nutanix SaaS without forcing SaaS

Nutanix offers SaaS-based services such as Data Lens and Nutanix Central. These services are also available on-premises, including for air-gapped environments.

This dual-delivery model recognizes that not all customers can or should consume control planes as public SaaS. 

10. Nutanix has more than a decade of real-world experience replacing VMware

Nutanix has operated alongside VMware for more than ten years, in many cases within the same environments. As a result, replacing vSphere is not a new ambition or a reactive strategy for Nutanix. It is just a long-standing and proven reality.

Equally important is the migration experience. Nutanix Move was built specifically to address one of the most critical challenges in any platform transition. It’s about getting workloads across safely, predictably, and at scale. Move supports migrations from vSphere, Hyper-V, AWS, and other environments, enabling phased and low-risk transitions rather than disruptive “big bang” projects. Beyond workload migration, Move can also translate NSX network and security policies into Nutanix Flow, addressing one of the most commonly cited blockers in VMware exit strategies.

Nutanix has spent more than a decade refining these aspects across thousands of customer environments, which is why many organizations today view it as a credible, de-risked alternative for the long term.

Conclusion

For organizations reassessing their infrastructure strategy, whether driven by VMware uncertainty, edge expansion, regulatory pressure, or cloud cost realities, Nutanix should be on the top of your list. It is a proven platform with a clear philosophy, a growing enterprise footprint, and more than a decade of hard-earned experience. If Nutanix is still on your shortlist as “HCI”, it may be time to look again, and this time at the full picture! 🙂 

Nutanix’s EUC Stack Reduces TCO and Improves ROI

Nutanix’s EUC Stack Reduces TCO and Improves ROI

Virtual Desktop Infrastructure (VDI) has always been a conservative technology. It sits close to users, productivity, and operational risk. For years, the dominant conversation revolved around brokers, protocols, and user experience. Today, that conversation is shifting more towards licensing, platform dependency, roadmap uncertainty and support models. Even product availability is becoming the real driver behind VDI decisions.

The recent announcements from Omnissa clearly reflect this shift. Horizon 8 is now generally available on Nutanix AHV, opening a long-awaited alternative virtualization path for enterprise-grade VDI.

VMware vSphere Foundation for VDI (VVF for VDI)

The combined Omnissa Horizon and VMware vSphere Foundation for VDI offering responds to a very real customer desire for simplification. For organizations already standardized on VMware technologies, fewer contracts and a predefined bundle feel familiar and operationally convenient.

Broadcom has announced the discontinuation of VMware vSphere Foundation in specific countries and regions, most notably in parts of EMEA. The decision does not apply globally (yet), but it is explicit, regional, and commercially binding for affected markets. Availability is no longer uniform, and customers must now verify on a country-by-country basis whether VMware vSphere Foundation (VVF) can still be procured.

It is important to be precise, though. The recent discontinuation of VVF applies only to specific countries and, as of today, it seems it does not include VVF for VDI for existing Omnissa customers. Horizon customers can still consume VVF for VDI in those environments, and there has been no formal announcement that this specific bundle will be withdrawn.

At the same time, it would be naive to ignore the broader context. VVF for VDI ultimately depends on the commercial and strategic relationship between Omnissa and Broadcom. Omnissa does not fully control the underlying hypervisor roadmap, its regional availability, or future sales policies. Any material change requires negotiation between two vendors with different priorities and incentives.

Currently, VVF for VDI, which can be bundled with Horizon, includes vSphere 8.  Support for the vSphere portion of the bundle will continue to be provided by VMware by Broadcom. The bundled offerings are available to be purchased in up to 5-year terms (restrictions may apply).  Subject to their general terms, Broadcom/VMware will provide vSphere 8 for the period of the license that a customer has purchased. Broadcom has not yet announced timelines for vSphere 9 support with VVF for VDI.  We are working with Broadcom to enable VVF for VDI in an upcoming vSphere 9.x release, but no date has yet been committed. If a customer has a current requirement to move to vSphere 9, they will need to buy VCF or VVF separately from Broadcom.

Recent decisions around VVF in parts of EMEA illustrate this clearly. Even if VVF for VDI remains available today, customers are implicitly betting on the continued alignment between Omnissa and Broadcom. Packaging may simplify procurement in the short term, but it also concentrates dependency at the most critical layer of the stack. For VDI environments, where stability and predictability are non-negotiables, this dependency becomes an integral part of the risk assessment.

Why This Context Matters for NCI-VDI

This is where Nutanix Cloud Infrastructure for VDI starts to look less like an alternative and more like a structurally safer choice.

With Horizon supported on AHV, customers can decouple broker choice from hypervisor dependency. But the value goes beyond commercial optionality. It also shows up in how the platform behaves operationally.

Omnissa Horizon Agents on Nutanix AHV

Enhanced refresh workflows introduce recovery points for desktop refresh operations. Instead of rebuilding or troubleshooting desktops under pressure, IT teams gain a practical rollback mechanism. It is essentially an undo button for virtual desktops, reducing downtime, simplifying remediation, and improving resilience for business continuity scenarios.

GPU-accelerated VDI is another area where the platform advantage becomes tangible. Managed NVIDIA vGPU support is integrated into compute profiles for Horizon workloads. GPU profiles are no longer an afterthought or a separate administrative domain. This makes it significantly easier to deliver high-performance virtual workstations for AI, design, healthcare imaging, or analytics workloads, while reducing operational complexity for administrators.

For environments relying on RDSH, NCI-VDI now brings full automation for farms, published desktops, and applications. Farm creation, scaling, and app publishing no longer require manual orchestration. 

ClonePrep customization completes the picture. Virtual machines can be customized rapidly during pool or farm creation, giving IT teams precise control over how desktops are initialized. Configurations remain consistent across pools, while still allowing organizational requirements to be enforced centrally.

These are the current Nutanix configuration maximums for AHV:

  • Cluster size – The maximum AHV hosts per cluster is 32
  • VMs per host – The maximum powered on VDI VMs per AHV node is 200.
  • VMs per cluster – The maximum number of powered-on VMs per AHV cluster is 4096.

Note: The Horizon 8 reference architecture for AHV deployments is available here.

Licensing That Reflects How VDI Is Actually Used

Licensing discussions around VDI often focus narrowly on user counts and price points. What is frequently overlooked is what is not included, as well as the architectural assumptions that are quietly embedded in the bundle.

VVF for VDI, whether consumed by Omnissa Horizon customers or Citrix customers (regular VVF), does not include NSX and its distributed firewalling capabilities. Network micro-segmentation, east-west traffic control, and fine-grained security policies are not part of the VVF for VDI entitlement. Customers that require these capabilities must either accept architectural gaps or upgrade to VMware Cloud Foundation (VCF).

NCI-VDI approaches this differently, particularly in the Ultimate edition. Licensing remains per concurrent user, pooled and based on the highest usage, but the functional scope expands in a way that directly impacts architecture and resilience.

With NCI-VDI Ultimate, customers gain native micro-segmentation capabilities as part of the platform. Security is enforced at the workload level without relying on an external networking stack or add-on products. For VDI environments, especially in regulated or multi-tenant scenarios, this enables consistent isolation between desktop pools, user groups, and supporting services without introducing operational complexity.

Replication and availability are another area where licensing and architecture intersect. NCI-VDI Ultimate includes advanced replication capabilities, including metro availability as well as Async DR and NearSync replication.

The key point here is alignment. Licensing reflects how VDI is actually used in production, including security boundaries within the platform, continuous availability expectations, and the need to protect stateful desktops without redesigning the entire environment. When these capabilities are included by design, TCO becomes more predictable and ROI improves over the full lifecycle.

Storage Included

User data has always been one of the hidden cost drivers in VDI projects. Profiles, documents, shared data, and application artifacts often introduce additional products, licenses, and operational silos.

With NCI-VDI, up to 100 GiB of Nutanix Unified Storage (NUS) per user is included and pooled. Home directories, profile data, shared file services, or other workloads can all be covered without introducing a separate storage platform.

Nutanix Unified Storage (NUS) is a software-defined storage platform consolidating file, object, and block storage into a single platform. Integrated with Nutanix hyperconverged infrastructure (HCI), NUS enhances the security and performance of virtual desktops and applications, while simplifying administration of storage. Your team can easily manage and control all file, object, and block data in one place—both on-premises and in the cloud such as AWS and Azure.

Again, fewer products and fewer operational boundaries translate directly into lower TCO.

Support Models Matter When VDI Becomes Business-Critical

Support is rarely part of the initial VDI design discussion. It usually becomes relevant when something breaks or when an upgrade behaves differently than expected.

In the VMware vSphere Foundation model, support is typically delivered through distributors and channel partners. While many partners do excellent work, this structure introduces an additional layer between the customer and the platform vendor. When issues span multiple layers, including broker, hypervisor, and storage, responsibility can become fragmented.

With NCI-VDI, customers running Horizon or Citrix on AHV engage directly with Nutanix for the infrastructure layer. Compute, storage, and virtualization are owned by a single support organization with a Net Promoter Score (NPS) consistently above 90.

Fewer handoffs, faster root-cause analysis, and clearer accountability directly improve operational efficiency and ROI.

Compliance Without Disruption – A Public-Sector Perspective

For healthcare organizations and federal agencies, licensing compliance is a continuity topic. Clinical systems and public services cannot be interrupted because of a licensing issue.

With NCI-VDI, license enforcement preserves operational continuity. Existing workloads continue to run even if a customer temporarily falls out of compliance. There is no forced shutdown and no service interruption.

Restrictions apply elsewhere, such as cluster expansion, access to support, management UIs, or upgrades and patches. Compliance remains enforceable, but without turning it into an operational incident. For public sector environments, this behavior is essential.

Closing Thought

VDI is no longer just about delivering desktops and virtual applications. It has become a platform decision that directly affects cost control, resilience, compliance, and long-term autonomy. Combined offerings like VVF for VDI may simplify procurement in the short term, but they also increase dependency at the most critical layer of the stack, a layer that recent changes have shown can shift regionally, commercially, and strategically.

Nutanix does not force customers into a single broker strategy, Horizon runs on AHV and Citrix remains a long-standing partner. The broker is important, but it is not where most long-term cost, risk, and complexity accumulate. The real differentiation lies below the broker layer.

When compute, storage, virtualization, security, and availability are delivered as one integrated platform, TCO drops almost naturally. Fewer vendors reduce dependency risk, and fewer dependencies reduce roadmap uncertainty. Lastly, fewer handoffs reduce operational friction. Together, these effects compound over time and translate directly into a higher return on investment.

Nutanix NCI-VDI gives customers the freedom to decouple the broker choice from hypervisor dependency, embedding security and availability into the platform, and aligning licensing with how VDI is actually used in production, it reduces TCO in ways that only become fully visible over multiple renewal cycles. 

Nutanix Is Quietly Redrawing the Boundaries of What an Infrastructure Platform Can Be

Nutanix Is Quietly Redrawing the Boundaries of What an Infrastructure Platform Can Be

Real change happens when a platform evolves in ways that remove old constraints, open new economic paths, and give IT teams strategic room to maneuver. Nutanix has introduced enhancements that, taken individually, appear to be technical refinements, but observed together, they represent something more profound. The transition of the Nutanix Cloud Platform (NCP) into a fabric of compute, storage, and mobility that behaves as one system, no matter where it runs.

This is the dismantling of long-standing architectural trade-offs and the business impact is far greater than the technical headlines suggest.

In this article, I want to explore four developments that signal this shift:

  • Elastic VM Storage across Nutanix clusters
  • Disaggregated compute and storage scaling
  • NC2 is generally available on Google Cloud
  • The strategic partnership between Nutanix and Pure Storage

Individually, these solve real operational challenges. Combined, they create an infrastructure model that moves away from fix constructs and toward an adaptable, cost-efficient, cloud-operating fabric.

Elastic VM Storage – The End of Cluster-Bound Thinking

Nutanix introduced Elastic VM Storage, which the ability for one AHV cluster to consume storage from another Nutanix HCI cluster within the same Prism Central domain. It breaks one of the oldest implicit assumptions in on-premises virtualization that compute and storage must live together in tightly coupled units.

By allowing VMs to be deployed on compute in one cluster while consuming storage from another, Nutanix gives IT teams a new level of elasticity and resource distribution.

It introduces an operational freedom that enterprises have never truly had:

  1. Capacity can be added where it is cheapest. If storage economics favour one site and compute expansion is easier or cheaper in another, Nutanix allows you to make decisions based on cost, not on architectural constraints.
  2. It reduces stranded resources. Every traditional environment suffers from imbalanced clusters. Some run out of storage, others out of CPU, and upgrading often means over-investing on both sides. Elastic VM Storage dissolves those silos.
  3. It prepares organizations for multi-cluster private cloud architectures. Enterprises increasingly distribute workloads across data centers, edge locations, and cloud-adjacent sites. Being able to pool resources across clusters is foundational for this future.

Nutanix is erasing the historical boundary of the cluster as a storage island.

Disaggregated Compute and Storage Scaling

For years, Nutanix’s HCI architecture was built on the elegant simplicity of shared-nothing clusters, where compute and storage scale together. Many customers still want this. In fact, for greenfield deployments, it probably is the cleanest architecture. But enterprises also operate in a world full of legacy arrays, refresh cycles that rarely align, strict licensing budgets, and specialized workload patterns.

With support for disaggregated compute and storage scaling, Nutanix allows:

  • AHV compute-only clusters with external storage (currently supported are Dell PowerFlex and Pure Storage – more to follow)
  • Mixed configurations combining HCI nodes and compute-only nodes
  • Day-0 simplicity for disaggregated deployments

This is a statement from Nutanix, whose DNA was always HCI: The Nutanix Cloud Platform can operate across heterogeneous infrastructure models without making the environment harder to manage.

  1. Customers can modernize at their own pace. If storage arrays still have years of depreciation left, Nutanix allows you to modernize compute now and storage later instead of forcing a full rip-and-replace.
  2. It eliminates unnecessary VMware licensing. Many organizations want to exit expensive hypervisor stacks while continuing to utilize their storage investments. AHV compute-only clusters make this transition significantly cheaper.
  3. It supports high-density compute for new workloads. AI training, GPU farms, and data pipelines often require disproportionate compute relative to storage. Disaggregation aligns the platform with the economics of modern workloads.

This is the kind of flexibility enterprises have asked for during the last few years and Nutanix has now delivered it without compromising simplicity.

Nutanix and Pure Storage

One of the most significant shifts in Nutanix’s evolution is its move beyond traditional HCI boundaries. This began when Nutanix introduced support for Dell PowerFlex as the first officially validated external storage integration, which was a clear signal to the market, that the Nutanix platform was opening itself to disaggregated architectures. With Pure Storage FlashArray now becoming the second external storage platform to be fully supported through NCI for External Storage, that early signal has turned into a strategy and ecosystem.

Nutanix NCI with Pure Storage

Nutanix now enables customers to run AHV compute clusters using enterprise-grade storage arrays while retaining the operational simplicity of Prism, AHV, and NCM. Pure Storage’s integration builds on the foundation established with PowerFlex, but expands the addressable market significantly by bringing a leading flash platform into the Nutanix operating model.

Why is this strategically important?

  • It confirms that Nutanix is committed to disaggregated architectures, not just compatible with them. What began with Dell PowerFlex as a single integration has matured into a structured approach. Nutanix will support multiple external storage ecosystems while providing a consistent compute and management experience.
  • It gives customers real choice in storage without fragmenting operations. With Pure Storage joining PowerFlex, Nutanix now supports two enterprise storage platforms that are widely deployed in existing environments. Customers can keep their existing tier-1 arrays and still modernize compute, hypervisor, and operations around AHV and Prism.
  • It creates an on-ramp for VMware exits with minimal disruption. Many VMware customers own Pure FlashArray deployments or run PowerFlex at scale. With these integrations, they can adopt Nutanix AHV without replatforming storage. The migration becomes a compute and virtualization change and not a full infrastructure overhaul.
  • It positions Nutanix as the control plane above heterogeneous infrastructure. The combination of NCI with PowerFlex and now Pure Storage shows that Nutanix is building an operational layer that unifies disparate architectures.
  • It aligns modernization with financial reality. Storage refreshes and compute refreshes rarely align. Supporting multiple external arrays allows Nutanix customers to modernize compute operations first, defer storage investment, and transition into HCI only when it makes sense.

Nutanix has moved from a tightly defined HCI architecture to an extensible compute platform that can embrace best-in-class storage from multiple vendors.

Nutanix Cloud Clousters on Google Cloud – A Third Strategic Hyperscaler Joins the Story

The general availability of NC2 on Google Cloud completes a strategic triangle. With AWS, Azure and now Google Cloud all supporting Nutanix Cloud Clusters (NC2), Nutanix becomes one of the very few platforms capable of delivering a consistent private cloud operating model across all three major hyperscalers. It fundamentally changes how enterprises can think about cloud architecture, mobility, and strategic independence.

Running NC2 on Google Cloud creates a new kind of optionality. Workloads that previously needed to be refactored or painfully migrated can now move into GCP without rewriting, without architectural compromises, and without inheriting a completely different operational paradigm. For many organizations, especially those leaning into Google’s strengths in analytics, AI, and data services, this becomes a powerful pattern. Keep the operational DNA of your private cloud, but situate workloads closer to the native cloud services that accelerate innovation.

NC2 on Google Cloud

When an enterprise can run the same platform – the same hypervisor, the same automation, the same governance model – across multiple hyperscalers, the risk of cloud lock-in can be reduced. Workload mobility and cloud-exit strategies become a reality.

NC2 on Google Cloud is a sign of how Nutanix envisions the future of hybrid multi-cloud. Not as a patchwork of different platforms stitched together, but a unified operating fabric that runs consistently across every environment. With Google now joining the story, that fabric becomes broader, more flexible, and significantly more strategic.

Conclusion

Nutanix is removing the trade-offs, that enterprises once accepted as inevitable.

Most IT leaders aren’t searching for (new) features. They are searching for ways to reduce risk, control cost, simplify operations, and maintain autonomy while the world around them becomes more complex. Nutanix’s recent enhancements are structural. They chip away at the constraints that made traditional infrastructure unflexible and expensive.

The platform is becoming more open, more flexible, more distributed, and more sovereign by design.

Moving away from VMware to Nutanix makes sense when…

Moving away from VMware to Nutanix makes sense when…

You shouldn’t be asking “Which platform has the longest feature list?” but “What outcome justifies the cost of moving from one private cloud stack to another?“. This is precisely where many VMware by Broadcom customers find themselves today. While there are still many loyal VMware customers, there are other organizations that want or must re-evaluate their current situation. And a simple but often forgotten truth is this: a like-for-like platform replacement rarely makes sense.

Not because Nutanix cannot do what VMware does. It absolutely can! But because the economics and operational impact of migrating an entire virtual estate purely to reproduce the status quo will not automatically create value. Unless Broadcom’s new price structure forces the customer’s hand or the relationship with the vendor becomes unbearable for non-technical reasons, a one-to-one replacement is just a reaction, and not a strategic move.

A change of platform needs a reason that transcends replacement. It needs intent.

And this is where the conversation becomes interesting, because the moment a customer begins thinking beyond “keep everything the same”, Nutanix suddenly becomes much more than a substitute or alternative. It becomes a platform for a new chapter.

Application Modernization

It’s almost 2026 and guess what, most enterprises (still) live in a VM-centric world and some of them are just starting now to modernize applications, modernize operations, and converge their infrastructure and cloud strategies. So, they look at Kubernetes, container orchestration and DevOps practices not as “modern” anymore, but as mandatory capabilities for the next decade.

Trying to retrofit these ambitions into a purely VMware-centric future is possible, but rarely elegant. Costs accumulate. Tooling becomes fragmented. Operational models start to diverge.

Nutanix provides a clean path into a Kubernetes-native, cloud-architected operational model through Nutanix Kubernetes Platform (NKP) and Nutanix Cloud Infrastructure (NCI) as the unified foundation.

Nutanix Kubernetes Platform Open Source

If an organization wants to build for the next generation of workloads rather than the last, platform migration becomes a strategic investment. And the cost of change is suddenly justified by the long-term trajectory.

AI becomes real. Sovereignty becomes mandatory.

Over the past year, enterprise AI has evolved from theory to a board-level priority. However, deploying secure, compliant, and controlled GenAI infrastructure is not something legacy stacks were designed for. GPU clusters, high-throughput storage, inference pipelines, and air-gapped architectures. All these require a platform that is not only modern, but sovereign, composable and operationally manageable.

Nutanix Enterprise AI

Nutanix offers a cohesive, GPU-ready, open ecosystem designed to host your own models, your own data, and your own AI stack.  Sovereign, isolated, and fully under your control.

Nutanix Enterprise AI (NAI) turns AI infrastructure into something deployable rather than experimental. Together with NCI and NKP, it forms an environment where customers can build internal AI factories without relying on hyperscalers or exposing sensitive data.

Flexibility in storage architecture

Recently, Nutanix announced support for external storage – starting with Dell and Pure Storage.

Nutanix and Pure Storage

 

For the first time, customers can bring their existing enterprise storage arrays into a Nutanix architecture without forcing a forklift replacement or abandoning multi-year investments.

This fundamentally changes the economics of a VMware-to-Nutanix transition. What used to be a full-stack change can now become an incremental evolution. Keep the storage infrastructure you already trust, maintain the performance characteristics your applications rely on, and modernize the compute and virtualization layer above it.

Nutanix is acknowledging that customers do not live in greenfield worlds, that not every journey starts with a clean slate, and that sovereignty and autonomy often require preserving existing assets rather than discarding them.

For customers who want to move away from VMware but cannot replace their storage systems, Nutanix now offers a transition path that aligns with financial and architectural realities. For customers planning application modernization or sovereign AI initiatives, the ability to combine dedicated storage arrays with NCI and NKP gives them the freedom to architect the right performance tiers for each workload without vendor lock-in.

Cost pressure meets VDI realities

Desktop virtualization has always been the domain where infrastructure complexity causes the most harm. VDI environments are sensitive, cost-intensive, and operationally unforgiving. If a customer is looking for a cheaper, simpler and more predictable platform for VDI, Nutanix becomes a compelling candidate and it offers an architectural shortcut by providing consolidated storage and compute, extremely fast storage performance, linear scaling, and dramatically simpler day-to-day operations. The cost-to-outcome ratio is hard to ignore.

Nutanix and Omnissa

In such scenarios, the platform transition is less about “leaving VMware” and more about optimizing the future economics of delivering virtual desktops with a more efficient stack.

Recently, Nutanix and Omnissa announced that Omnissa Horizon now fully supports Nutanix AHV.

Conclusion

Ultimately, the decision to move away from VMware (or any other vendor) should never be driven purely by frustration or speculation. It should be driven by clarity.

If the only goal is to continue exactly what you do today, with the same architecture and application landscape, then the cost of change often outweighs the benefits. Unless Broadcom pricing leaves no room for rational continuity.

Nutanix is about “accelerating”, and your decision shouldn’t be about “escaping”. And that distinction is what separates good decisions from expensive reactions.

When motivation is driven by evolution, Nutanix becomes a foundation for the next chapter of your digital strategy.

And that is exactly the moment when moving away from VMware begins to make profound sense.

How to Install Nutanix Community Edition (NCE) on a Single-Node Server

How to Install Nutanix Community Edition (NCE) on a Single-Node Server

For quite some time, my small home lab has been the place where I like to test and learn new things. It started with three nodes, but today I just run a single ESXi server. On that host, I experimented with PiHole and Kubernetes, but recently I decided it was time to try something new since I have hardware lying around: Nutanix Community Edition (NCE)

Preparing for the Installation

Create an account on next.nutanix.com and download the ISO from here: https://next.nutanix.com/discussion-forum-14/download-community-edition-38417

Download the appropriate USB imaging software, such as Rufus (you must use Rufus v3.2.1) or UNetBootin, and image your USB drive from the Installer ISO file.

In the Rufus UI, you can set the partition scheme and target system in one of the following ways:

  • Partition scheme: MBR, Target system: BIOS or UEFI
  • Partition scheme: GPT, Target system: UEFI (non CSM)

Note: This step is not needed if you load the Community Edition installer ISO directly with the Virtual Drive feature of IPMI on your host instead of a USB flash drive. That’s the case for me.

Important: Nutanix Community Edition reserves IP addresses 192.168.5.0 through 192.168.5.254 for internal networking. Since the same address range cannot be used, the host (hypervisor) and the Controller VM (CVM), must be connected to a network with a different subnet other than 192.168.5.0.

Good to know: All host and Controller VMs in the same cluster must be on the same subnet.

  • Host IP address (for the Community Edition hypervisor host)
  • Controller VM IP address – This value becomes the virtual IP address that enables you to log on and manage the cluster through the Prism web console or an SSH terminal connection

I followed these instructions to install Nutanix Community Edition: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Community-Edition-Getting-Started-v2_1:top-installing-ce-t.html

Booting and Installation

1) Start the node and boot from ISO (IPMI) or USB.

2) When the boot sequence finishes, the CE installer dialog appears.

3) Verify or adjust the disk selections and enter the requested network details.

NCE Installer Disks

4) Press Enter and go to the next page. Wait for the CE EULA to appear.

Important: You need to scroll down to the end of the EULA. Otherwise, the installation will fail at the next step.

5) Press Tab and accept the EULA. Use the arrow keys to navigate to “Start” and press “Enter”.

6) The installation process displays status messages on the screen.

7) When the imaging process finishes, a prompt appears to remove the CE installation media.

8) Remove the CE installation media and press the y key and press “Enter”

The host automatically restarts and finishes the installation process. After the host restarts, the initial CVM configuration is automatically applied.

After the host restarts, the AHV host and the CVM run their first boot setup processes. These processes can take 15 to 20 minutes to complete, depending on host performance.

After these processes finish running, you can perform the following steps:

9) Open an SSH session to the CVM IP address (192.168.2.21 in my case)

  • The username is nutanix and the password is nutanix/4u.

10) If you are creating a single-node cluster, run cluster create as follows, replacing cvm_ip with the CVM IP address: cluster -s cvm_ip –redundancy_factor=1 create

Important: Use the IP address that you assigned to the CVM during installation. Don’t use the CVM internal IP address (192.168.5.2).

11) A series of messages indicates that the cluster is being created and cluster services are starting. When the process is finished – this took about 10 minutes for me, the cluster creation message is displayed, and the prompt returns.

12) Define the cluster name by using the command “ncli cluster edit-params new-name=cluster_name

13) Configure a name server for the cluster by using the command “ncli cluster add-to-name-servers servers=public_name_server_ip_address

14) Configure an external IP address for the cluster by using the command “ncli cluster set-external-ip-address external-ip-address=cluster_ip_address

15) Add an NTP server IP address to the list of NTP servers by using the command “ncli cluster add-to-ntp-servers servers=NTP_server_ip_address

Logging into Prism

Now it’s time to access the web console.

16) In a web browser, navigate to http://management_ip_addr, replacing management_ip_addr with the IP address of any CVM in the cluster.

  • The browser redirects to the encrypted port (9440) and displays an SSL certificate warning.
  • Sign in with the default admin account username and password.
    • Username: admin
    • Password: nutanix/4u

17) After you are requested to change the default password, you’ll be asked to log in again.

18) At the next step, you have to enter your Nutanix community account username and password.

19) Congratulations! You now have deployed your first Nutanix Community Edition node like me! 😀