# NetApp Intelligent Data Infrastructure — 4+1 Layer AI Infrastructure Assessment

> Mapped to the 4+1 Layer AI Infrastructure Model  
> Version: v1.1 - 1C Decision-Capability Clarification · Date: June 22, 2026  
> Source: NetApp INSIGHT 2025 (Oct 14-16, 2025), NVIDIA GTC 2026 (Mar 16-19, 2026), netapp.com / docs.netapp.com (ONTAP, AFF/ASA/AFX, StorageGRID, AIPod, AI Data Engine, NetApp Console/BlueXP, Trident), AWS/Azure/GCP first-party service docs, analyst/press coverage (TechTarget, Blocks & Files, StorageMath), published 4+1 model. v1.1 (instrument reconciliation): clarified that Layer 1C credits a data-movement decision/orchestration capability (policy-driven replication/tiering/caching), not transparent transport throughput — distinguishing NetApp's movement decisions from CoreWeave-style byte-transport acceleration.  
> Published by: The CTO Advisor LLC · thectoadvisor.com  
> Author: Keith Townsend

[Full interactive assessment](https://layer2c.web.app/assessment/netapp) · [Methodology](https://layer2c.web.app/methodology) · [What Is Layer 2C?](https://layer2c.web.app/what-is-layer-2c)

## Executive Summary

NetApp is a storage and data-management vendor whose authority concentrates in one of the most mature governed data foundations in the market (Layer 1A) and the storage-adjacent infrastructure around it — a software-defined storage fabric (Layer 0), best-in-class data movement (Layer 1C), and a hybrid-multicloud data control plane (Layer 2A). For the AI execution, reasoning, and application layers, NetApp is the data half of a meet-in-the-middle AI factory (AIPod): the compute, model-serving runtime, retrieval, and applications are NVIDIA's, sold alongside through the channel — not NetApp's.

The capture is decoupled and Oracle-shaped: open at the surface, captive beneath. Data is reached through standard protocols (NFS, SMB, S3) and travels freely — uniquely, as first-party services on all three clouds (Amazon FSx for NetApp ONTAP, Azure NetApp Files, Google Cloud NetApp Volumes). But the value accumulates in ONTAP's opinions — SnapMirror relationships, clone hierarchies, efficiency and snapshot policies, the data-management workflows enterprises build on — and those do not lift. Leaving ONTAP is a multi-year rebuild even though the bytes move freely; running it on a hyperscaler does not loosen the hold, because it is still ONTAP. Eight of ten scored components are Ceded, all in the data plane where the ONTAP opinions live.

NetApp's push up the stack — the AI Data Engine (global metadata catalog, data guardrails, and vector/RAG curation) — is early-access (lighthouse March 2026, broad availability targeted summer 2026) and not yet a deployable, scored capability. Until it ships broadly, NetApp's AI-native governance and retrieval are forward-looking; what an architect can deploy today is the mature data foundation plus the data movement around it.

The meet-in-the-middle structure is the defining authority finding. Unlike Dell and Cisco — primes that sell, curate, and support the full NVIDIA stack as their own AI factory, and are therefore credited for the runtime and retrieval they deliver — NetApp brings the storage half of AIPod while NVIDIA brings the compute, runtime, retrieval, and application ecosystem, and the channel integrates. Each vendor is credited for its half: NetApp owns the data plane; NVIDIA owns the intelligence. The NVIDIA dependency is heavy exactly where NetApp partners (Layer 0 compute, Layer 2B runtime, Layer 1B retrieval, Layer 3 applications) and near-empty where NetApp owns the layer (1A, 1C, 2A).

The buyer's trade: the buyer gets the most operationally proven, most portable, best-governed enterprise data foundation available — the safest home for data across on-prem and every major cloud — and in exchange accumulates ONTAP-specific opinions that are a multi-year lift to leave, even as the bytes stay open. For AI specifically, NetApp anchors the data; the intelligence is bought alongside from NVIDIA. NetApp's bet is that the governed data foundation is the durable position in the AI stack, and that when the AI Data Engine ships broadly it can convert that foundation into an AI-native data platform. The sharp contrast is VAST, its closest competitor: the same data-foundation strength, but where VAST verticalized into native retrieval and an agent runtime, NetApp partners for them while its own AI-native layer matures.

## Layer Status

| Layer | Status | Classification |
|---|---|---|
| Layer 0 · Compute | ◑ Software-Defined Storage Fabric | Compute & Network Fabric |
| Layer 1A · Storage | ● NetApp Strength — Data Foundation | Data Storage & Governance |
| Layer 1B · Retrieval | ○ Emerging (AI Data Engine, Early Access) | Context Management & Retrieval |
| Layer 1C · Pipelines | ◑ Best-in-Class Data Movement; AI Pipelines Pre-GA | Data Movement & Pipelines |
| Layer 2A · Orchestration | ◑ Data-Infrastructure Control Plane; No GPU Scheduling | Infrastructure Orchestration |
| Layer 2B · Runtime | ○ Runtime is NVIDIA's (Meet-in-the-Middle) | Application Runtime & Execution |
| Layer 2C · Reasoning | ○ No Reasoning Plane (Data Guardrails ≠ Agent Governance) | Agentic Infrastructure — The Reasoning Plane |
| Layer 3 (+1) · Applications | ○ No Value Plane — Data Foundation Beneath Others' Apps | AI Application Layer — The Value Plane |

## DAPM Profile

| Classification | Count | Meaning |
|---|---|---|
| Retained | 0 | Enterprise owns and controls this capability |
| Delegated | 2 | Provided by substitutable partner; enterprise retains swap authority |
| Ceded | 8 | Vendor controls this; enterprise has no governance authority |
| Absent | 0 | No capability at this layer |

## Strongest Layers

- **Layer 1A** (Data Storage & Governance) — NetApp Strength — Data Foundation

## Gap Areas

- **Layer 1B** (Context Management & Retrieval) — Emerging (AI Data Engine, Early Access)
- **Layer 2B** (Application Runtime & Execution) — Runtime is NVIDIA's (Meet-in-the-Middle)
- **Layer 2C** (Agentic Infrastructure — The Reasoning Plane) — No Reasoning Plane (Data Guardrails ≠ Agent Governance)
- **Layer 3 (+1)** (AI Application Layer — The Value Plane) — No Value Plane — Data Foundation Beneath Others' Apps

## Layer-by-Layer Detail

### ◑ Layer 0 · Compute: Compute & Network Fabric

*Raw compute, networking, and acceleration fabric*  
**Status:** Software-Defined Storage Fabric

**AFF / ASA / AFX (Disaggregated All-Flash Architecture)** [DAPM: Ceded]  
Proprietary all-flash storage systems running ONTAP. AFX disaggregates performance from capacity (AFX 1K controllers + NX224 NVMe enclosures, scale-out, DGX SuperPOD-certified); AFF/ASA cover unified and SAN all-flash. The architecture and its opinions cannot be lifted to another vendor as deployed. Proprietary NetApp platform — opinions captive, no open exit.

**Storage Networking (NVMe-oF / NVMe-TCP / Ethernet)** [DAPM: Delegated]  
Standard fabric interfaces connecting compute to the storage estate — NVMe-over-Fabrics, NVMe/TCP, Ethernet, pNFS/RDMA. Substitutable switching against multi-vendor standards; the connectivity opinions lift. Mirrors how VAST's NVMe-oF fabric is scored.

**Gap Analysis:** NetApp owns no silicon, GPUs, or networking fabric — but, like its closest competitor VAST, it owns a genuine software-defined storage architecture that belongs at Layer 0. AFX disaggregates ONTAP (separating performance from capacity: AFX 1K controllers + NX224 NVMe enclosures, scaling to 128 controllers and beyond an exabyte), connected over NVMe-oF. That fabric is NetApp's real Layer 0 capability, scored the way VAST's DASE/NVMe-oF architecture is scored at Layer 0.

The AI compute is NVIDIA's. AIPod (NetApp storage + NVIDIA DGX), AIPod Mini (ONTAP + Intel/OPEA), and FlexPod AI (Cisco UCS + NetApp AFF + NVIDIA + OpenShift AI) are validated, channel-assembled designs — NetApp brings the storage half, partners bring the compute. So Layer 0 sits at moderate: a software-defined storage fabric (NetApp's own), with the acceleration and networking-for-GPU entirely NVIDIA's. Below Dell and Cisco (strong), which own compute silicon and networking; level with VAST, which scores its storage architecture at this layer the same way.

**Borrowed Judgment:** Multi-directional. NetApp retains its storage-fabric architecture (AFF/ASA/AFX, disaggregated ONTAP, NVMe-oF) — that is its Layer 0 IP. It borrows all accelerated-compute and GPU-networking judgment from NVIDIA (DGX, DGX SuperPOD, Spectrum/ConnectX in the AIPod designs) and server hardware from OEM partners (Lenovo, Cisco). The storage fabric is NetApp's; the compute fabric is NVIDIA's.

### ● Layer 1A · Storage: Data Storage & Governance

*Durable, governed data foundation — the Governance Catalog that Layer 2C queries*  
**Status:** NetApp Strength — Data Foundation

**ONTAP Data Management (AFF/ASA/AFX, Cloud Volumes ONTAP, first-party FSx for ONTAP / Azure NetApp Files / Google Cloud NetApp Volumes)** [DAPM: Ceded]  
Multiprotocol data-management OS (NFS, SMB, S3, iSCSI, NVMe-oF) with SnapMirror, FlexClone, efficiency, and tiering — identical across on-prem and all three clouds. Standard protocols at the surface, but the ONTAP data-management opinions are captive: leaving ONTAP is a multi-year rebuild, and running it on a hyperscaler does not change that. Proprietary NetApp platform — opinions captive, no open exit.

**StorageGRID (Object / S3)** [DAPM: Delegated]  
Geo-distributed S3-compatible object storage. The S3 interface is a multi-vendor standard — bucket, lifecycle, and policy opinions lift to any S3 platform without rebuilding. Delegated, mirroring the instrument's treatment of S3-interface object storage.

**Data Classification + Data Infrastructure Insights + Autonomous Ransomware Protection** [DAPM: Ceded]  
PII/sensitive-data classification and mapping (formerly Cloud Data Sense), observability with AI-driven anomaly detection (formerly Cloud Insights), and ML-based ransomware protection in ONTAP (on by default on recent AFF/ASA platforms). Compliance and resilience governance — proprietary opinions captive to NetApp's tooling, not an AI-metadata catalog. Proprietary NetApp platform — opinions captive, no open exit.

**Gap Analysis:** This is NetApp's center of gravity and arguably the most mature data foundation on the instrument. ONTAP is a multiprotocol data-management OS (NFS, SMB, S3, iSCSI, NVMe-oF) with SnapMirror, FlexClone, efficiency, and tiering, running identically on-prem (AFF/ASA/AFX), as software (Cloud Volumes ONTAP), and as first-party services on all three clouds (Amazon FSx for NetApp ONTAP, Azure NetApp Files, Google Cloud NetApp Volumes). StorageGRID adds S3 object; Data Classification maps PII/sensitive data; Data Infrastructure Insights adds observability and anomaly detection; ONTAP Autonomous Ransomware Protection adds ML-based resilience, on by default in recent releases. It is the safest, most portable, most operationally proven data home in the market.

The authority reading is Oracle-shaped. The protocols are standard and reassuring, but the value accumulates in ONTAP's opinions — replication topology, clone hierarchies, snapshot and efficiency policies, the feature-set workflows enterprises build on — and those are captive. The governance is real but compliance-flavored (PII classification, ransomware, observability), not the AI-metadata catalog a reasoning plane would query; that piece, the AI Data Engine Metadata Engine, is early-access. NetApp earns strong here on data-foundation maturity and breadth — broader than any peer on pure enterprise data management, uniquely first-party across all three clouds — calibrated to VAST and Dell at this layer, with the AI-native catalog noted as the forward gap.

**Borrowed Judgment:** Low. ONTAP, StorageGRID, Data Classification, Insights, and ARP are NetApp IP — the data-management and governance opinions are Ceded to NetApp; StorageGRID's S3 surface keeps object opinions portable (Delegated). No partner or NVIDIA dependency in the GA foundation.

### ○ Layer 1B · Retrieval: Context Management & Retrieval

*Low-latency retrieval for RAG — vector/hybrid search, context windows*  
**Status:** Emerging (AI Data Engine, Early Access)

**Gap Analysis:** NetApp has no generally-available native retrieval or vector capability of its own. The would-be capability is the AI Data Engine Data Curator (embedding generation and a RAG retrieval endpoint, NVIDIA-NIM-powered), which is early-access (lighthouse March 2026, broad availability targeted summer 2026) and therefore not scored; and reporting suggests it generates embeddings before data moves to external vector databases rather than being a NetApp-owned vector DB.

In the AIPod meet-in-the-middle, retrieval is NVIDIA's half (NeMo Retriever / NIM), co-sold through the channel — NetApp is not the prime delivering it as its own solution (unlike Dell/Cisco). So today the enterprise brings its own vector database and retrieval pipeline; NetApp provides the governed data foundation underneath. This sits below VAST (strong, native vector search), Dell (moderate, Elastic + NVIDIA acceleration), and Nutanix (moderate, GA pgvector) — all of which have a GA retrieval capability NetApp lacks.

**Borrowed Judgment:** The enterprise retains the retrieval function — it brings its own vector database and RAG pipeline today, or consumes NVIDIA's NeMo Retriever as the co-sold half of AIPod. NetApp's own retrieval (AI Data Engine Data Curator) is early-access and, when it ships, NVIDIA-NIM-powered. No GA NetApp retrieval to inherit.

### ◑ Layer 1C · Pipelines: Data Movement & Pipelines

*Move/transform data — ETL/ELT, lineage, cost-aware movement, KV cache tiering*  
**Status:** Best-in-Class Data Movement; AI Pipelines Pre-GA

**SnapMirror (Replication & Data Mobility)** [DAPM: Ceded]  
Async and sync replication across sites and clouds — the logistics layer for staging and distributing datasets, including AI training and inference data. ONTAP-to-ONTAP; the replication relationships and opinions do not lift to another platform. Proprietary NetApp platform — opinions captive, no open exit.

**FlexCache + FabricPool (Caching & Cost-Aware Tiering)** [DAPM: Ceded]  
FlexCache caches hot data near compute; FabricPool auto-tiers cold data to object/cloud by temperature. A captive ONTAP caching and tiering engine — cost-aware data movement whose opinions are proprietary. Proprietary NetApp platform — opinions captive, no open exit.

**BlueXP / NetApp Console Copy & Sync (Migration & Cloud Ingest)** [DAPM: Ceded]  
Moves and synchronizes data from external, file, and SaaS sources into the estate across hybrid multicloud. NetApp-proprietary sync and migration service; the movement opinions are captive. Proprietary NetApp platform — opinions captive, no open exit.

**Gap Analysis:** NetApp's data movement is best-in-class for all data types, and it is a legitimate Layer 1C capability even though it is not marketed for AI: the layer's purpose explicitly includes movement, cost-aware movement, and cache tiering, and AI data logistics are exactly that. SnapMirror replicates and stages datasets across sites and clouds; FlexCache caches hot data near compute; FabricPool tiers cold data to object/cloud by temperature; BlueXP/Console Copy & Sync moves and synchronizes data from external and SaaS sources. An architect leverages these for AI today; the absence of an 'AI' label does not remove the capability. What earns the score is the movement-decision capability — configurable replication topologies, cost-aware tiering policies, and caching policy, where the enterprise accumulates opinions (the same opinions that make these Ceded to ONTAP) — not transparent byte-transport, which is a Layer 0/1A throughput property, not a Layer 1C decision.

What NetApp lacks at GA is the pipelines/transform/lineage half — ETL/ELT, transformation, and lineage. That capability is the AI Data Engine AI-ETL pipeline (sync, classify, vectorize), which is early-access. Best-in-class on the movement half plus a missing transform half is partial capability — moderate. This sits above Nutanix (gap — Time Machine is narrow copy-data-management, not a comprehensive movement platform) and below VAST (strong — DataEngine is a full event-driven AI pipeline platform). It is roughly level with Dell, for the inverse reason: Dell has pipeline IP (Dataloop) and thinner movement; NetApp has movement mastery and pre-GA pipelines.

**Borrowed Judgment:** Low for movement — SnapMirror, FlexCache, FabricPool, and Cloud Sync are NetApp IP, the data-movement opinions Ceded to NetApp. The AI-pipeline/transform/lineage half is absent: the enterprise brings its own ETL/orchestration (Airflow, Spark, Kubeflow) today, and NetApp's AI-ETL (AI Data Engine) is early-access.

### ◑ Layer 2A · Orchestration: Infrastructure Orchestration

*GPU scheduling, quotas, RBAC, fair-share scheduling, utilization optimization*  
**Status:** Data-Infrastructure Control Plane; No GPU Scheduling

**NetApp Console (Hybrid Multicloud Data Control Plane)** [DAPM: Ceded]  
Unified provisioning, protection, governance, mobility, and health across the on-prem and multicloud storage estate (AFF/ASA/FAS/AFX, StorageGRID, FSx for ONTAP, Azure NetApp Files, Google Cloud NetApp Volumes). Proprietary control plane — orchestration opinions captive to NetApp. Proprietary NetApp platform — opinions captive, no open exit.

**Trident (Kubernetes CSI Driver)** [DAPM: Ceded]  
Open-source (Apache 2.0), NetApp-maintained CSI driver provisioning NetApp storage to Kubernetes for AI and container workloads. The CSI interface is a multi-vendor standard, but Trident is NetApp-storage-specific — it binds provisioning to NetApp platforms. Mirrors the instrument's treatment of vendor CSI drivers.

**Gap Analysis:** NetApp orchestrates the data infrastructure, not the AI compute. NetApp Console (formerly BlueXP) is a mature, unified control plane for the entire storage and data estate across on-prem and all three clouds — provisioning, protection, governance, mobility, and health from one surface. Trident is NetApp's open-source Kubernetes CSI driver, dynamically provisioning ONTAP/StorageGRID/FSx/ANF storage to containerized and AI workloads. Together they are genuine infrastructure-orchestration capability for the data plane.

The AI core of this layer — GPU scheduling, quotas, fair-share — NetApp does not provide; that belongs to the enterprise's Kubernetes and NVIDIA. So Layer 2A sits at moderate, calibrated to VAST and Dell: a storage/data control plane plus a vendor CSI driver, with GPU scheduling absent or borrowed from NVIDIA (universal across these peers). NetApp Console is a genuinely deep multicloud data control plane, comparable in kind to VAST Polaris; the GPU-scheduling gap is the same one Dell and VAST carry, so it does not dock NetApp below them.

**Borrowed Judgment:** NetApp owns the data-infrastructure control plane (Console) and the CSI driver (Trident) — Ceded to NetApp. AI-compute orchestration (GPU scheduling, quotas, fair-share) is not NetApp's at all; the enterprise's Kubernetes and NVIDIA own it.

### ○ Layer 2B · Runtime: Application Runtime & Execution

*Model serving, agent execution, inference APIs, distributed inference*  
**Status:** Runtime is NVIDIA's (Meet-in-the-Middle)

**Gap Analysis:** NetApp has no model serving, no inference runtime, and no agent runtime — none. Where inference runs in a NetApp-anchored stack it is NVIDIA NIM / AI Enterprise (AIPod) or Red Hat OpenShift AI (FlexPod AI). This is the runtime half of the meet-in-the-middle: NetApp brings the storage, NVIDIA brings the runtime, the channel integrates. Crucially, NetApp is not the prime that sells, curates, and supports the NVIDIA runtime as its own factory — unlike Dell (2B moderate, delivered NVIDIA runtime) or Cisco (2B moderate, own security IP over the runtime). So the capability is not credited to NetApp's row; it is NVIDIA's, scored there.

The enterprise inherits NVIDIA's (NIM) or Red Hat's (OpenShift AI) execution layer entirely. NetApp is the data foundation beneath it. This sits below every storage and platform peer at Layer 2B — VAST (strong, built AgentEngine), Dell (moderate, delivered NVIDIA runtime), Nutanix (moderate, NAI serving) — because NetApp built no runtime IP and does not deliver the runtime as its own solution.

**Borrowed Judgment:** Total. NetApp provides no runtime. In a NetApp-anchored AI factory the runtime is NVIDIA's (NIM / AI Enterprise) or Red Hat's (OpenShift AI), co-sold via the channel rather than delivered by NetApp. NetApp is the storage beneath someone else's execution layer.

### ○ Layer 2C · Reasoning: Agentic Infrastructure — The Reasoning Plane

*Policy-driven placement and resource coordination — the Autonomy Layer*  
**Status:** No Reasoning Plane (Data Guardrails ≠ Agent Governance)

**Gap Analysis:** Applying the 'Routing Is Not Reasoning' test: NetApp has no agent governance, no model routing, no policy-driven inference placement, and no multi-agent orchestration. Its only adjacent capability is the AI Data Engine Data Guardrails, which scan, classify, and exclude sensitive data from AI/RAG pipelines — 'guardrails follow the data.' That is data-access governance (a Layer 1A-style claim), not agent-action governance (Intelligence-2C) and not request-time placement (Infrastructure-2C). It is the wrong function for this layer, and it is early-access regardless.

This is a clean gap, consistent with the entire data and infrastructure cohort — Dell, Nutanix, VMware, VAST, NVIDIA, CoreWeave — none of which productizes a reasoning plane. The enterprise retains policy-driven placement and agent governance in full. The live-placement gap is universal across the instrument, noted rather than penalized.

**Borrowed Judgment:** Inverted — there is no Layer 2C to borrow. The enterprise retains policy-driven placement and agent governance entirely. NetApp's data guardrails (early-access) govern data, not agents; the meet-in-the-middle NVIDIA stack has no reasoning plane either.

### ○ Layer 3 (+1) · Applications: AI Application Layer — The Value Plane

*AI-powered business capabilities — business logic, workflow automation*  
**Status:** No Value Plane — Data Foundation Beneath Others' Apps

**Gap Analysis:** NetApp ships no first-party AI applications and curates no AI-application ISV program of its own. Its ecosystem is infrastructure and compute (NVIDIA, Cisco, Lenovo, Intel, Red Hat) and channel (distribution and integration) — not value-plane ISVs. In the AIPod meet-in-the-middle, the application ecosystem is NVIDIA's (AI Enterprise) plus the customer's own apps; NetApp is the data foundation beneath the value plane, not a provider of it.

This sits below the partner-ecosystem vendors at Layer 3 — Dell, HPE, and Cisco curate genuine AI-application ISV programs (Dell's OpenAI/Palantir/ServiceNow, HPE Unleash AI's 26+ ISVs) — and below VAST (moderate, Cosmos Community partner tracks). NetApp has neither a first-party app nor a curated AI-app ISV program, so it does not address the value plane even via partners: gap, not partner. The value plane is entirely the customer's, NVIDIA's, and ISVs'.

**Borrowed Judgment:** The value plane is the customer's plus NVIDIA's plus ISVs' — NetApp provides no AI applications and curates no AI-application ISV ecosystem. The enterprise brings its own apps; NetApp supplies the governed data beneath them.

---
*Layer2C · AI Infrastructure Decision Intelligence · The CTO Advisor LLC · thectoadvisor.com*