FC-0 — Physical & Virtual Substrate

Hardware lifecycle management · score 3, gap opinion, DAPM Ceded Included: Lifecycle Manager (LCM) provides coordinated lifecycle management across AOS, AHV, firmware, BIOS, BMC, and Nutanix services as one cluster-level operation on certified HCL nodes. Within certified configurations, LCM manages firmware updates through the Nutanix toolchain — operators do not need to use iDRAC or iLO separately for firmware lifecycle on HCL-certified nodes. AHV maintenance mode drains VMs automatically before node maintenance. AHV HA restarts VMs automatically on surviving nodes. LCM reads IPMI and OEM health metrics to inform update scheduling. Dell PowerFlex synchronous DR coordination extends lifecycle integration across external storage. Note: Foundation Central (GA .NEXT 2026) is a Day 0 deployment tool simplifying initial cluster imaging on certified OEM nodes — it does not change the ongoing lifecycle management story. Gap from 4: lifecycle management is bounded to certified HCL node configurations. Physical supply chain — provisioning new hardware — remains outside Nutanix control. Full maintenance transparency at the hyperscaler benchmark level requires the enterprise to operate within Nutanix-certified hardware configurations. Opinion gap — the enterprise configures maintenance windows using existing LCM primitives. Two-model consensus (Gemini, ChatGPT) confirms F1=3. Score corrected from v1.0 F1=2. DAMP correction (v1.2): Corrected from Delegated. LCM lifecycle opinions are Nutanix-proprietary — the enterprise cannot take LCM's coordinated firmware and software lifecycle management and operate it on a competing HCI platform without rebuilding. Not substitutable; Ceded.

Substrate heterogeneity · score 2, gap structural, DAPM Ceded Nutanix manages multiple certified OEM hardware configurations through unified Prism Central primitives — Dell XC Plus, HPE, Cisco UCS, Lenovo, Fujitsu, and NX appliances are all managed through one management surface with consistent operational model. External storage integrations (Dell PowerFlex GA, Pure Storage FlashArray GA) add validated compute-storage combinations under Prism Central management. This is genuine heterogeneity management across certified configurations. Critical HCL constraint: Nutanix's Hardware Compatibility List is component-combination-specific. The enterprise cannot bring existing OEM servers from its estate — even if the server model matches an HCL entry, the specific NIC model, NVMe drive configuration, and firmware version must match the certified combination exactly. Hardware options are NX appliances or OEM-certified node configurations purchased through Nutanix's channel. The community forum is explicit: "a Nutanix node is HCL specific and you cannot just buy something and add the correct hardware." Nutanix's official support policy excludes configuration and usage support for non-Nutanix-branded hardware platforms. Score 2 reflects: genuine heterogeneity management across certified configurations through unified Prism primitives, with the HCL constraint preventing arbitrary OEM hardware from the enterprise estate. Structural — the HCL constraint is a deliberate design choice. Score corrected from v1.0 F2=1 (too aggressive) and from two-model consensus of F2=3 (ignores HCL constraint). F2=2 is the correct calibration.

Substrate portability · score 3, gap structural, DAPM Ceded Included: NC2 (Nutanix Cloud Clusters) runs the full AOS/AHV stack on bare metal instances in AWS, Azure, and Google Cloud — the same Prism Central management plane, same AHV hypervisor, same NCM for lifecycle management, same NKP for Kubernetes. An enterprise runs Nutanix on-premises (NX appliances or certified OEM nodes) and extends to NC2 on cloud bare metal without changing management toolchain. GC2 (Government Cloud Clusters) extends this to AWS GovCloud and AWS European Sovereign Cloud for regulated industries. The operational model is genuinely consistent across on-premises and cloud deployments. Gap from 4: NC2 requires cloud provider bare metal instances — it runs Nutanix software on cloud bare metal, not on cloud virtual instances. This means NC2 does not provide fully elastic auto-scaling equivalent to cloud-native managed services. NC2 on Google Cloud added C3 bare metal and Hyperdisk storage support (.NEXT 2026), expanding the cloud substrate flexibility. Score 3 reflects genuine same-control-plane substrate portability across on-premises and three major hyperscalers — the strongest on-premises vendor substrate portability in this instrument.

FC-1 — Distributed Data & Context Fabric

Data location and gravity awareness · score 2, gap closeable, DAPM Retained Additional Nutanix licensing required (NUS): Nutanix Unified Storage 5.3 provides S3-compatible object storage, file services (NFS, SMB), and block storage with programmatic location awareness through Prism Central APIs. Smart tiering knows data temperature — hot data on local NVMe, cold data tiered automatically to Google Cloud or OVHcloud S3. NUS 5.3 adds multitenant object scaling and quotas for AI data lakes. NDB (additional Nutanix licensing) provides location awareness for managed databases (Oracle, SQL Server, PostgreSQL, MySQL, MongoDB) provisioned within Nutanix. Prism Central knows where VMs, NUS volumes, and NDB databases are placed across the cluster. Gap from 3: data location awareness is bounded to the Nutanix storage estate. Enterprise data outside Nutanix — Oracle databases on legacy SAN, mainframe records, SaaS data — is invisible to Prism's data location awareness. No unified enterprise data catalog spanning all data types. Closeable through third-party data catalog tooling deployed on Nutanix VMs or NKP. Score 2 reflects programmatic data location awareness for the Nutanix storage estate — the strongest on-premises vendor at this function within their storage scope.

Governance and compliance metadata · score 2, gap closeable, DAPM Retained Additional Nutanix licensing required (Data Lens 2.0, GA .NEXT 2026): Nutanix Data Lens provides ransomware detection, anomalous access monitoring, data audit trails, access governance, and permissions visualization for Nutanix Unified Storage files and objects — on-premises including air-gapped environments. Security Central (NCI Ultimate) provides infrastructure compliance posture management against CIS and NIST frameworks at the VM and infrastructure level. Data Lens is security-primary: who accessed which NUS files, anomalous behavior patterns, data age analytics, file distribution insights. It is not a compliance metadata engine that classifies enterprise data and propagates regulatory tags to placement enforcement decisions. Score 2 reflects: genuine file and object governance analytics through Data Lens within NUS scope, genuine infrastructure compliance through Security Central — both real Nutanix capabilities providing more than zero governance metadata. Comparable to OpenShift's ACS scoring F1=2 for infrastructure and Kubernetes workload compliance bounded to OpenShift scope. Gap from 3: governance metadata is bounded to NUS files/objects and Nutanix infrastructure; not spanning external databases, mainframe data, or SaaS systems; not propagating compliance metadata to placement enforcement. Closeable through third-party data governance tooling. Score corrected from v1.0 F2=1 following two-model consensus (Gemini, ChatGPT both score 2 with same reasoning as our corrected position).

Retrieval and context services · score 2, gap closeable, DAPM Ceded Additional Nutanix licensing required (NAI + NDB): Nutanix provides validated infrastructure patterns for retrieval workloads through GPT-in-a-Box blueprints — deployment automation for Milvus and pgvector on NKP with NUS storage. NDB provides managed PostgreSQL with pgvector extension — a managed database service that can store and query vectors with Nutanix support. NAI AI Gateway connects retrieval results to inference endpoints with RBAC and rate limiting. The distinction from F1=3: NDB pgvector is a managed database that stores vectors, not a purpose-built managed vector search service. GPT-in-a-Box is an infrastructure automation blueprint for deploying retrieval components, not a fully managed platform-native RAG API service — the enterprise deploys and operates the retrieval software on Nutanix infrastructure. Score 2 reflects: validated retrieval infrastructure patterns and managed database-backed vector storage, without a fully managed hyperscaler-equivalent RAG pipeline service. Gap from 3: the enterprise operates the retrieval software stack; Nutanix provides the infrastructure and database management layer beneath it. Closeable through additional tooling or NAI evolution. Score corrected from v1.0 F3=3 following two-model consensus (Gemini, ChatGPT both score 2). DAMP correction (v1.2): Corrected from Delegated. Primary scored capability is NDB pgvector — a Nutanix-managed database service whose operational opinions are Nutanix-proprietary and captive. Secondary path (Milvus via NKP) is genuinely Delegated (open-source with real alternatives) and noted in the narrative. The DAPM reflects the primary managed service path.

Data pipeline and lineage · score 1, gap closeable, DAPM Retained Included: NUS smart tiering provides automated data movement between on-premises NVMe storage and cloud object storage (Google Cloud, OVHcloud S3) based on data temperature — storage lifecycle automation within the NUS estate. NKP catalog provides open-source MLOps engines (Kubeflow, MLflow) for deployment — community tooling without Nutanix management. Additional Nutanix licensing (NAI): MLOps workflow engines available through NKP AI catalog provide ML pipeline orchestration for AI workloads — open-source tools delivered through NKP, not Nutanix-proprietary managed services. No Nutanix product provides managed ETL, CDC, streaming pipeline management, or enterprise data lineage tracking. The NUS storage tiering is storage lifecycle automation, not enterprise data pipeline management. MLOps engines through NKP are open-source tooling the enterprise deploys and operates. Score 1 reflects: NUS automated storage tiering included, open-source ML pipeline tooling accessible through NKP catalog without Nutanix management, no managed enterprise data pipeline services. Closeable through third-party tooling — same path available on any platform.

FC-2A — Infrastructure Orchestration

Workload universality · score 3, gap structural, DAPM Ceded Additional Nutanix licensing required (NKP, NDB, NAI): Prism Central provides a unified management surface across VMs (AHV — included), Kubernetes workloads (NKP), managed databases (NDB), and AI inference workloads (NAI). Operators and developers interact with Prism Central for all workload types — one management surface covering the full enterprise workload portfolio. Multi-hypervisor support (AHV, ESXi, Hyper-V) through Prism Central is a genuine included differentiator: enterprises with mixed hypervisor estates manage both AHV and ESXi workloads through one management pane. The underlying control plane architecture is federated — AHV for VMs, NKP for Kubernetes, NDB for databases, NAI for AI inference — but the management experience is unified through Prism Central. Per the instrument's scoring rule: score at product family capability, note additional licensing. Gap from 4: GPU scheduling intelligence for demanding AI workloads benefits from NVIDIA GPU Operator integration. Structural — same constraint as all on-premises platforms. Score 3 reflects product family workload universality through Prism Central with additional Nutanix licensing flag.

Resource lifecycle automation · score 2, gap structural, DAPM Ceded Included: AHV Acropolis Dynamic Scheduler (ADS) automatically rebalances VMs across nodes based on resource utilization within available cluster capacity. AHV HA automatically restarts VMs on surviving nodes when a host fails. NCM Intelligent Operations provides capacity forecasting, anomaly detection, and automated remediation recommendations. Strong lifecycle automation within fixed cluster capacity. NC2 provides a cloud burst path — when on-premises capacity is exhausted, the enterprise can extend to AWS, Azure, or GCP bare metal through the same Prism Central management plane without changing operational tooling. On cloud substrate, NC2 approaches F2=3 behavior through cloud infrastructure provisioning. Single score of 2 reflects the on-premises structural constraint — the platform is scored as a platform, not split by deployment model. Physical supply chain for new on-premises hardware remains outside Nutanix control. NC2 cloud burst capability is noted as a genuine operational differentiator: no other on-premises HCI vendor provides a managed cloud capacity expansion path through the same control plane. Structural — physical supply chain constraint applies universally to on-premises deployments. Score corrected from v1.0 F2=3 following two-model consensus (Gemini, ChatGPT both score 2). Same methodology rule applied to OpenShift: ROSA approaches F2=3 on cloud substrate but platform scores at on-premises position.

Policy and quota enforcement · score 3, gap opinion, DAPM Ceded Included in NCP (NCI Pro/Ultimate): Prism Central project-based resource quotas governing vCPUs, memory, and storage across all clusters simultaneously. Flow Network Security provides microsegmentation — VM category-based network security policies enforced at the hypervisor layer. Flow Virtual Networking provides VPC-equivalent network isolation with consistent policy enforcement. Security Central (NCI Ultimate) provides continuous security posture management and compliance benchmarking. Multi-hypervisor policy enforcement: Prism Central enforces the same project quotas, security policies, and compliance posture across AHV and ESXi clusters simultaneously — the only vendor in the instrument managing mixed hypervisor estates under unified policy. NCM Self-Service enforces approval gate workflows — developer provisioning requests governed by policy before resource consumption. Gap from 4: policy does not automatically propagate to application-layer enforcement within Kubernetes pods (NKP has its own policy primitives). Opinion gap — enterprise configures NKP NetworkPolicy and RBAC alongside Prism policies using existing Nutanix primitives.

Substrate lifecycle integration · score 3, gap structural, DAPM Ceded Included: LCM coordinates software updates across AOS, AHV, NCC, and Nutanix services as one cluster-level coordinated operation. LCM reads IPMI and OEM health metrics to inform update scheduling — hardware health awareness integrated into software update decisions. AHV maintenance mode automatically drains VMs before node maintenance across all workload types — VM and Kubernetes workloads are evacuated before scheduled maintenance. Dell PowerFlex synchronous DR coordination (.NEXT 2026 GA) extends lifecycle integration across external storage — AHV maintenance mode and PowerFlex replication state are coordinated through LCM and Prism Central. AHV HA automatically recovers workloads from node failures. Gap from 4: hardware firmware lifecycle requires OEM tooling — LCM reads hardware health but does not push firmware updates. Full firmware-plus-software lifecycle coordination in one operation requires OEM management platform integration alongside LCM. Structural — same physical constraint as all software control planes without OEM HSM-equivalent native integration.

Accelerator and GPU management · score 2, gap vendor-roadmap, DAPM Delegated Included: AHV provides GPU passthrough (VMs access physical GPUs directly) and NVIDIA GRID vGPU (multi-tenant GPU sharing through hardware partitioning) — GA and mature. Hardware-enforced GPU partitioning through vGPU is a genuine Nutanix capability providing multi-tenant isolation. NKP provides NVIDIA GPU Operator integration for Kubernetes GPU workload management. Gap from 3: GPU scheduling intelligence above vGPU partitioning — topology-aware placement, automatic GPU right-sizing, demand-driven GPU allocation — relies on NVIDIA operators deployed in guest clusters rather than native Prism scheduling intelligence. AHV GPU topology-aware automatic placement optimization is part of the Nutanix Agentic AI solution (early access, GA H2 2026) — this specific capability will move the score toward 3 when GA. NAI 2.6 AI Gateway manages inference endpoints with RBAC and rate limiting across GPU-backed model servers. Score 2 reflects GA capabilities: hardware-enforced vGPU partitioning, NKP GPU Operator for Kubernetes workloads, NAI inference endpoint management — without native Prism-level topology-aware GPU scheduling. Vendor roadmap — H2 2026 AHV GPU topology-aware placement GA will close the gap to F5=3. Score corrected from v1.0 F5=3 following two-model consensus (Gemini, ChatGPT both score 2). DAMP correction (v1.2): Corrected from Retained. AHV vGPU relies on NVIDIA GRID/AI Enterprise — NVIDIA-proprietary firmware for hardware-enforced GPU partitioning. Not commodity substrate; not open-source with real alternatives at scale. Delegated — NVIDIA is the primary dependency, substitutable in principle with AMD GPU support (if certified) but NVIDIA is the de facto standard. Same classification as NVIDIA GPU dependencies across all assessed vendors.

FC-2B — Execution & Runtime

Runtime universality · score 3, gap structural, DAPM Ceded Additional Nutanix licensing required (NKP, NDB, NAI): AHV executes VM workloads natively — included. NKP executes Kubernetes container workloads. NDB executes managed databases (Oracle, SQL Server, PostgreSQL, MySQL, MongoDB). NAI executes AI inference workloads through Models-as-a-Service. All workload types execute within the Nutanix platform under Prism Central management. Multi-hypervisor execution: enterprises with existing ESXi workloads can execute both ESXi VMs and AHV VMs through Prism Central during migration, providing runtime continuity through the transition. Gap from 4: AI inference through NAI uses a different API surface (NAI Models-as-a-Service endpoint API) than VM and Kubernetes workloads through Prism Central — same structural exception as all on-premises platforms. Structural.

Persona abstraction at execution · score 3, gap opinion, DAPM Ceded Included: NCM Self-Service provides developer self-service for VM workloads through blueprint-based provisioning — developers request resources through the NCM portal without operator intervention, with approval gates enforced by NCM policy. Operators retain full Prism Central visibility into cluster health, hardware state, and resource utilization. Security Central provides security audit surfaces. Multi-hypervisor self-service: the same NCM Self-Service portal serves developers provisioning AHV VMs and ESXi VMs — developers do not experience a toolchain change during hypervisor migration. Additional Nutanix licensing (NKP): Kubernetes developer self-service through NKP interface. Additional Nutanix licensing (NAI): AI developer self-service through NAI portal. Gap from 4: developer self-service for Kubernetes (NKP), AI (NAI), and databases (NDB) uses separate portals from the NCM VM self-service — not a single unified interface across all workload types. Opinion gap — enterprise configures NKP, NAI, and NDB self-service alongside NCM using existing Nutanix primitives. Score 3 reflects product family persona abstraction with per-workload-type portal acknowledgment.

Execution lifecycle and observability · score 3, gap mixed, DAPM Ceded Included: NCM Intelligent Operations provides cross-VM-infrastructure observability with native correlation — VM performance, storage I/O, network metrics, and cluster health correlated in one Prism Central view with anomaly detection and automated remediation recommendations. This is partial native correlation across the VM infrastructure layer, stronger than telemetry exposure alone. NCM Intelligent Operations includes capacity forecasting and automated remediation — the platform surfaces correlated insights rather than raw metrics. Nutanix has a certified partnership with Dynatrace (Global Innovation Partner of the Year at .NEXT 2026) — extends cross-workload correlation to application-layer observability for enterprises with Dynatrace. Gap from 4: native NCM correlation covers VM infrastructure comprehensively; application-layer correlation across containers (NKP), databases (NDB), and AI inference (NAI) requires Dynatrace integration (third party, Opinion for enterprises with Dynatrace) or configuration of additional Nutanix telemetry streams. Mixed gap ownership — Opinion for enterprises with existing observability platforms, Closeable for enterprises without.

AI inference and agent execution · score 3, gap vendor-roadmap, DAPM Ceded Additional Nutanix licensing required (NAI 2.6, GA March 2026): Models-as-a-Service providing endpoint APIs for NVIDIA NIM and Hugging Face models. AI Gateway with unified policy control over cloud-hosted and private LLMs — RBAC, token-based rate limiting, showback dashboards, full observability. MCP server support with tool-level filtering and API key injection at the gateway — agents connect to enterprise tools through managed MCP access governance with audit trails. Fine tuning (LoRA/PEFT) within the NAI platform. NVIDIA Nemotron model support. Air-gapped deployment supported. NAI AI Gateway's MCP governance is a genuine differentiator: API key injection at the gateway level (not per-server), tool-level filtering (read-only vs. write capabilities), and full audit trails distinguish NAI from basic MCP access control. Gap from 4: cross-framework agent orchestration — governing agents from LangFlow, LangGraph, and A2A protocol alongside NAI-native agents — is part of the Nutanix Agentic AI full solution (early access, GA H2 2026). Vendor roadmap — H2 2026 GA confirmed for cross-framework orchestration. Inference scaling is Kubernetes-native through NKP (HPA/KEDA) — Opinion gap. DAMP correction (v1.2): Corrected from Retained. NAI AI Gateway — the inference governance layer providing RBAC, token-based rate limiting, MCP server access management, and audit trails — is Nutanix-proprietary. The enterprise that has configured NAI AI Gateway policies governing which teams access which models and which agents call which MCP tools has accumulated Nutanix-captive governance opinions that cannot be lifted to a competing inference gateway without rebuilding. Ceded for the NAI governance layer. The underlying NVIDIA NIM inference engines are Delegated (NVIDIA-provided, separately licensed).

FC-2C — The Reasoning Plane

Autonomous placement reasoning · score 0, gap structural, DAPM Retained Nutanix has the most developed FC-2C signal of any on-premises HCI vendor — and still does not pass the FC-2C litmus. NCM Intelligent Operations makes automated remediation recommendations based on infrastructure signals — resource utilization, anomaly patterns, capacity forecasting. AHV GPU topology-aware placement optimization (H2 2026 roadmap) will automatically optimize VM placement across GPU-dense servers based on topology — Infrastructure-2C for AI workload resource optimization. Neither consumes live FC-1 governance metadata to derive placement. Data Lens generates governance metadata for NUS files and objects; that metadata does not flow into AHV's scheduler or NCM's placement recommendations. When a new GDPR residency constraint arrives, an operator configures Prism project policies, Flow network policies, and VM placement affinities. NCM executes the configured policies — the constraint-to-rule translation is the operator's responsibility. Applying the first-principles derivation test: no Nutanix product derives placement from live FC-1 compliance metadata without operator rule authoring. Gap ownership Structural: no Nutanix product with confirmed timeline addresses the full FC-2C definition of compliance-metadata-derived placement across all workload types. The H2 2026 Agentic AI solution addresses Infrastructure-2C for AI workloads (GPU topology placement) but Structural for compliance-metadata placement derivation.

FC-3 — Application Distribution and Governance

Application catalog and distribution · score 3, gap opinion, DAPM Ceded Included: NCM Self-Service (formerly Calm) provides a governed application catalog through blueprints — pre-configured application stacks that developers deploy through the Nutanix Marketplace without building infrastructure. Blueprints are operator-authored deployment templates encoding provisioning, configuration, scaling, and Day 2 scripts. Nutanix Marketplace contains ready-to-use blueprints for common workloads. The blueprint model is comparable to VCF Automation templates in deployment intelligence depth — strong Day 1 provisioning and configuration, Day 2 operations through scripted runbooks rather than continuously running operators. Additional Nutanix licensing (NKP): NKP provides Kubernetes application distribution through Helm charts and Kubernetes operators — operators from the Kubernetes ecosystem encode Day 2 operational intelligence equivalent to OperatorHub. Additional Nutanix licensing (NAI): NAI model catalog with RBAC-governed access. Additional Nutanix licensing (NDB): managed database provisioning. With the full product family: VMs (NCM blueprints), Kubernetes applications (NKP operators/Helm), databases (NDB), and AI models (NAI catalog) covered across workload types. Gap from 4: Day 2 operational intelligence depth varies by workload type — NKP operators provide continuous Day 2 intelligence for Kubernetes applications; NCM blueprints provide deployment-time automation with scripted Day 2 for VM applications. Opinion gap — enterprise authors Day 2 scripts in blueprints for VM workloads using existing NCM primitives. Score 3 reflects product family catalog coverage with consistent governance across workload types. DAMP correction (v1.2): Corrected from Delegated. NCM blueprints encoding deployment automation, and NAI model catalog governance policies, are Nutanix-proprietary management opinions. An enterprise that has built NCM blueprints for its infrastructure automation cannot lift those blueprints to a competing HCI platform without rebuilding. The NKP operator catalog (community Kubernetes operators) is genuinely Delegated — noted in narrative — but the primary catalog governance mechanism (NCM blueprints, NAI catalog) is Ceded.

Application lifecycle governance · score 2, gap mixed, DAPM Ceded Included: NCM provides RBAC governance over blueprint access and approval gates for VM application provisioning. NCM audit logging records all self-service actions — who requested, who approved, what was deployed. LCM manages Nutanix platform component lifecycle. Security Central (NCI Ultimate) provides continuous compliance drift detection at infrastructure level. Additional Nutanix licensing (NKP): NKP provides Kubernetes-native lifecycle governance — Helm release management, Flux GitOps for declarative application state, namespace-level RBAC. NKP Flux GitOps is included in the NKP subscription without a separate subscription purchase. Additional Nutanix licensing (NDB): database lifecycle governance — automated patching, version management, backup governance. Additional Nutanix licensing (NAI): AI model lifecycle governance — model version management, token quota enforcement. Per-product lifecycle governance is genuine but operates in separate domains — NCM governs VMs, NKP governs Kubernetes apps, NDB governs databases, NAI governs AI models. No unified lifecycle governance surface correlating audit trails across all application types in one view. Gap from 3: unified audit trail across all application types in a single correlated surface requires SIEM integration. Mixed gap ownership — Opinion for enterprises with existing SIEM, Closeable for enterprises without. Score 2 reflects genuine per-product lifecycle governance without unified cross-product audit surface. DAMP correction (v1.2): Corrected from Delegated. NCM audit logging, NKP lifecycle governance opinions, and NAI model lifecycle management are Nutanix-proprietary. The enterprise cannot take its accumulated NCM blueprint governance history, NKP Flux GitOps configuration, or NAI model lifecycle policies and operate them on a competing platform without rebuilding. Ceded — Nutanix-captive lifecycle governance opinions across the product family.

Developer experience and self-service · score 3, gap opinion, DAPM Ceded Included: NCM Self-Service provides developer self-service for VM workloads — blueprint discovery through Nutanix Marketplace, parameter configuration within policy guardrails, deployment without operator intervention. Approval gates enforced by NCM policy — platform policy, not manual queue. Multi-hypervisor self-service: the same NCM portal serves AHV and ESXi VM provisioning during migration — developers do not experience a toolchain change. Additional Nutanix licensing (NKP): Kubernetes developer self-service through NKP interface. Additional Nutanix licensing (NAI): AI developer self-service through NAI portal. Additional Nutanix licensing (NDB): database self-service through NDB. Across the product family: strong developer self-service for VMs (NCM), Kubernetes (NKP), databases (NDB), and AI (NAI) — all workload types have platform-governed self-service with approval gates. Gap from 4: developer self-service for different workload types uses separate portals within the Nutanix product family — not a single unified interface across all workload types. This is a within-band qualitative gap, not a drop to F3=2. The F3=3 anchor requires strong self-service across primary workload types with approval gates enforced by platform policy — Nutanix meets this. Opinion gap — enterprise can configure consistent entry points using existing Nutanix primitives. Score corrected from v1.0 F3=2 following two-model consensus (Gemini, ChatGPT both score 3). Portal fragmentation is a within-F3=3-band gap, not a reason to score F3=2. DAMP correction (v1.2): Corrected from Delegated. NCM Self-Service portal configuration, approval gate workflows, and blueprint catalog publishing represent Nutanix-proprietary self-service opinions. Developer self-service for Kubernetes (NKP) and AI (NAI) similarly accumulates Nutanix-captive portal and policy configuration. The enterprise cannot lift these self-service opinions to a competing HCI platform without rebuilding the catalog, approval workflows, and portal configuration. Ceded.

AI application and agent distribution · score 3, gap vendor-roadmap, DAPM Ceded Additional Nutanix licensing required (NAI 2.6, GA March 2026): NAI provides AI application distribution through Models-as-a-Service catalog — model version management, RBAC-governed access, self-service endpoint provisioning, token quota enforcement. MCP server governance: API key injection at the gateway level (not per-server configuration), tool-level filtering controlling which capabilities agents can access (read-only vs. write), full audit trails for all MCP tool calls. This is platform-native AI governance — managed by Nutanix, not requiring enterprise-built governance infrastructure. NKP AI catalog provides open-source AI developer tools including notebooks, vector databases, MLOps engines, and agentic frameworks. Gap from 4: cross-framework agent distribution — governing agents from LangFlow, LangGraph, and A2A protocol alongside NAI-native agents — is part of the Nutanix Agentic AI full solution (early access, GA H2 2026). Vendor roadmap — H2 2026 GA confirmed. Score 3 reflects NAI 2.6 GA AI governance depth: model catalog, RBAC, MCP server governance with tool-level filtering and audit trails. DAMP correction (v1.2): Corrected from Delegated. NAI 2.6 model catalog governance — model versioning, RBAC policies, MCP server access governance, token quota configurations, and audit trails — is Nutanix-proprietary. An enterprise that has configured NAI MCP server governance policies governing which agents access which tools has accumulated Nutanix-captive AI governance opinions. Cannot be lifted to a competing AI inference platform without rebuilding. Ceded.

FC-4 — Integration Fabric

Event fabric and messaging · score 0, gap closeable, DAPM Retained Nutanix has no event fabric product. NCM runbook automation can trigger actions in response to events through webhook integrations but this is event-driven IT automation, not a managed enterprise event bus with schema enforcement, fan-out, delivery guarantees, and replay. No Nutanix product provides managed enterprise messaging — no Kafka equivalent, no AMQ equivalent, no managed event streaming. The enterprise must acquire and deploy third-party tooling (Kafka, RabbitMQ) on Nutanix VMs or through NKP. Score 0 reflects: no platform-native managed event fabric. Closeable through third-party tooling. No Nutanix product closes this gap.

API management and gateway · score 0, gap closeable, DAPM Retained NAI AI Gateway manages inference API endpoints — unified policy control over LLM endpoints with RBAC, rate limiting, and observability. This is AI-specific API management for inference endpoints, not enterprise API lifecycle management for application APIs. No publication workflow for business APIs, no developer portal for application API discovery, no versioning governance for enterprise service APIs, no transformation pipeline, no API-level audit for non-AI APIs. Flow Virtual Networking provides network-layer ingress — not API lifecycle management. Score 0 reflects: no enterprise API management platform. NAI AI Gateway is scoped to AI inference; it does not govern the enterprise's application or service APIs. Closeable through third-party tooling deployed on NKP.

Workflow and process orchestration · score 1, gap closeable, DAPM Retained Included: NCM runbooks provide IT infrastructure automation — scripted workflows for provisioning, scaling, backup, remediation, and operational tasks across VMs, Kubernetes, databases, and storage. NCM runbooks can be triggered by events through webhook integrations, chained across systems, and published through NCM Self-Service as operator-initiated workflows. The NCM ServiceNow integration connects NCM runbook execution to ITSM service catalog items. Score 1 reflects: basic workflow automation for IT operations tasks through NCM runbooks — available without additional enterprise support, providing infrastructure automation patterns. Gap from 3: NCM runbooks are IT automation workflows, not BPMN-compliant business process orchestration. Long-running business processes, saga patterns, compensation logic, cross-system business workflows, and AI agent chain orchestration require separate tooling. The distinction matches the community Camel K precedent at OpenShift: basic automation patterns available without enterprise support, full enterprise business process orchestration requires separate acquisition. Closeable — BPMN-compliant workflow engines can be deployed on NKP. Score corrected from v1.0 F4=0 following two-model consensus (Gemini, ChatGPT both score 1).

SaaS and enterprise system integration · score 0, gap closeable, DAPM Retained Nutanix has no maintained connector library to enterprise systems of record. NCM blueprints and runbooks can call external APIs through scripted tasks — an operator can write a runbook that calls a Salesforce API or SAP API. This is custom scripting, not maintained connector infrastructure. The NCM ServiceNow integration is one certified connector for one ITSM system, not a broad connector library for enterprise systems of record. Score 0 reflects: no platform-native maintained enterprise connector library. Custom API calls through runbook scripts do not constitute managed integration connectors. Closeable through third-party integration tooling deployed on NKP.

AI-native integration · score 2, gap closeable, DAPM Retained Additional Nutanix licensing required (NAI 2.6, GA March 2026): NAI AI Gateway provides MCP server access management with three genuine governance capabilities: (1) API key injection at the gateway interface rather than configuring it on every individual MCP server — centralized credential management for MCP connections; (2) tool-level filtering — controlling which specific tool capabilities (read-only vs. write access) agents can use; (3) enterprise observability — all MCP requests including latency and specific tools called are recorded with full audit trail for AI governance. This is access governance over MCP connections, not managed MCP connection infrastructure. The distinction: NAI governs which agents access which tools through what permissions; it does not discover MCP servers, maintain MCP server health, or route MCP connections dynamically. Score 2 reflects: AI-native integration available through platform governance framework applied to MCP patterns, with RBAC, tool-level filtering, and audit trails as genuine Nutanix-managed services. Stronger than basic access control (F5=1); below full managed connection infrastructure (F5=3). Gap: dynamic MCP connection routing, server discovery, and connection health management require enterprise-built infrastructure or additional tooling. Closeable.