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 — reached GA and is now scored: the Metadata Engine gives Layer 1A its AI-metadata catalog, and AIDE's vectorization and retrieval endpoints give NetApp a first-party, storage-integrated retrieval surface at Layer 1B (moderate — first-release, license-gated, and hardware-gated to AFX plus Data Compute Node clusters; the software-only deployment is metadata-only). The architect can now deploy NetApp-native AI data governance and retrieval on an AFX estate; everywhere else, the mature data foundation plus data movement remains the deployable core.
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-by-layer status: Layer 0 (Software-Defined Storage Fabric), Layer 1A (NetApp Strength — Data Foundation), Layer 1B (AIDE Retrieval — Storage-Integrated), Layer 1C (Best-in-Class Movement + AI-Ingest Pipeline), Layer 2A (Data-Infrastructure Control Plane; No GPU Scheduling), Layer 2B (Runtime is NVIDIA's (Meet-in-the-Middle)), Layer 2C (No Reasoning Plane (Data Guardrails ≠ Agent Governance)), Layer 3 (+1) (No Value Plane — Data Foundation Beneath Others' Apps).
Assessment framework: 4+1 Layer AI Infrastructure Model. Scoring model: Decision Authority Placement Model (DAPM) — Retained, Delegated, or Ceded. Published by The CTO Advisor LLC. Author: Keith Townsend. Date assessed: July 13, 2026. Version: v1.4 - AIPod Mini Whose-Paper Ruling.
Raw compute, networking, and acceleration fabric
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.
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.
All AI compute in NetApp's AI factories is NVIDIA's: AIPod pairs ONTAP storage with NVIDIA DGX systems; AFF A90 and AFX are certified for NVIDIA DGX SuperPOD. NetApp supplies storage; NVIDIA supplies the accelerated compute. This is the compute half of the meet-in-the-middle.
AIPod holds the NVIDIA-Certified Storage designation; AFX/AIDE align to the NVIDIA AI Data Platform reference design. The DX50 data-compute node ships with an NVIDIA L4 for storage-side data-engine acceleration (AIDE, now GA), not general AI compute.
AIPod Mini is the lone NVIDIA-free path — Intel Xeon 6 (AMX) compute with Intel's open-source OPEA RAG framework for departmental inference. Everywhere else, NetApp's AI compute is NVIDIA.
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.
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.
AIPod and FlexPod AI are reference/validated designs, channel-assembled ('meet in the middle') — NetApp does not manufacture or sell the GPU compute. AFX is GA and DGX SuperPOD-certified. Future support announced for NVIDIA RTX PRO Servers (Blackwell) and STX (BlueField-4 / Vera Rubin) is roadmap, not GA.
Durable, governed data foundation — the Governance Catalog that Layer 2C queries
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.
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.
GA per product documentation: automated metadata extraction and cataloging of files and objects across local and peered ONTAP clusters; workspaces with RBAC and OIDC; Data Sync keeps catalogs current via policy-driven SnapMirror; centralized REST query and filtering APIs. Included with base ONTAP One licensing per the AIDE FAQ; full GPU-dependent capability gated to AFX + Data Compute Node clusters, with a metadata-only software deployment on customer RHEL servers (AIDE 1.0.0). The catalog structure and workspace opinions are captive to the NetApp platform.
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.
ONTAP, StorageGRID, Data Classification, Insights, and Autonomous Ransomware Protection are NetApp IP over standard protocols — no NVIDIA. (The AI Data Engine's NIM-powered vectorization, now GA and scored at Layer 1B, adds an NVIDIA dependency inside the retrieval surface.)
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 arrived: the AI Data Engine Metadata Engine reached GA (AIDE 9.18.1 U0; software-only on third-party RHEL servers as AIDE 1.0.0, April 30, 2026) — automated metadata extraction and cataloging across peered ONTAP clusters, workspaces with RBAC/OIDC, Data Sync via policy-driven SnapMirror, REST query APIs. The AI-metadata catalog a reasoning plane would query now exists on NetApp paper, scoped to ONTAP estates (full capability on AFX + Data Compute Nodes). 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, now with the AI-native catalog shipping rather than forward-dated.
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.
AI Data Engine Metadata Engine promoted from the watch-list July 12, 2026 on doc-confirmed GA (docs.netapp.com/us-en/ai-data-engine). Channel note: ONTAP also ships on Lenovo paper (ThinkSystem DM/DG) — the capture is NetApp's through any channel, and the Lenovo row scores those arrays Ceded-to-NetApp by design; the pairing is deliberate two-row structure, not drift.
Low-latency retrieval for RAG — vector/hybrid search, context windows
Data collections, embeddings, and retrieval endpoints created and served in AI Data Engine Console (AIDE 9.18.1 U1, license-gated), with guardrail policies defined in AIDE and bound to workspaces in System Manager. Storage-integrated: retrieval runs where the governed data lives, on AFX + Data Compute Node clusters. Proprietary NetApp surface — collection, embedding-pipeline, and guardrail opinions are captive to the platform.
AIDE's vectorization pipeline is NVIDIA-NIM-powered — the embedding intelligence inside NetApp's retrieval surface is NVIDIA's, the same split as every storage vendor's GA retrieval.
In the meet-in-the-middle AIPod, the co-sold retrieval path remains NVIDIA's NeMo Retriever / NIM within NVIDIA AI Enterprise. AIDE now gives NetApp a first-party alternative on AFX estates.
AI Data Engine reached GA and moved this cell. Per NetApp's product documentation (AIDE 9.18.1 U1; AIDE 1.0.0 followed April 30, 2026), AIDE creates data collections, embeddings, and retrieval endpoints in the AI Data Engine Console — a NetApp-owned, storage-integrated retrieval surface with guardrail-based governance, not embedding-prep for external vector databases. That settles the watch-list's open fact question in NetApp's favor. Why moderate and not more: the capability is first-release, license-gated (vectorization and RAG require the appropriate AIDE licenses), and hardware-gated — full capability requires ONTAP AI data platform clusters (AFX 1K storage nodes plus NetApp Data Compute Nodes), while the software-only third-party-server deployment (AIDE 1.0.0) is explicitly metadata-only with no vectorization, RAG, or GPU services. Calibration: at Dell's moderate (Elastic productized) and Nutanix's moderate (GA pgvector), still below VAST's strong (native vector search, mature, not gated to a single hardware line). Off-AFX estates and the AIPod channel path still consume NVIDIA's retrieval or bring their own.
Moderate. On AFX estates the enterprise can now inherit NetApp's retrieval judgment — collections, embeddings, retrieval endpoints, guardrails — with NVIDIA NIM providing the embedding intelligence inside it. The retrieval opinions accumulate in AIDE (workspaces, collections, guardrail policies) and are captive to the NetApp platform. Everywhere else the pre-AIDE reading holds: bring your own retrieval or consume NVIDIA's co-sold half of AIPod.
Promoted from gap July 12, 2026 on doc-confirmed GA (docs.netapp.com/us-en/ai-data-engine — release notes plus vectorization/data-collections and guardrails administration sections). The earlier watch-list question — native vector DB vs. embedding-prep to external DBs — resolved native: AIDE serves its own retrieval endpoints. Scope facts worth keeping: AFX 1K + Data Compute Node hardware gate for full capability; the AIDE 1.0.0 software-only path is metadata-only with a supported upgrade path when GPU services land there.
Move/transform data — ETL/ELT, lineage, cost-aware movement, KV cache tiering
Fixed-function AI data pipeline, GA per product documentation: Data Sync keeps sources current via policy-driven SnapMirror (AIDE 9.18.1 U0), guardrail classification screens sensitive data, NIM-powered vectorization transforms into embeddings and collections (U1) — terminating in AIDE's own retrieval surface. Fails the never-anticipated-workload test (no arbitrary stages, no external destinations, no lineage), so it is scored as the slice it is; the retrieval-endpoint facet is scored at 1B. Pipeline and policy opinions captive to the NetApp platform.
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 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.
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.
SnapMirror, FlexCache, FabricPool, and Cloud Sync are NetApp IP — no NVIDIA. (The AI Data Engine's NIM-powered vectorization and Data Sync are now GA — see notes on the pending 1C re-read.)
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 keeps this cell at moderate is the general-versus-fixed-function rule. The AI Data Engine pieces of the transform story (Data Sync, vectorization, guardrail classification) reached GA in July 2026 and are scored below — but they are a fixed-function AI-ingest pipeline: fixed stages (sync, classify, vectorize) terminating in AIDE's own retrieval surface. Applying the decidable test — can it run a pipeline workload NetApp never anticipated? — the answer is no: there is no arbitrary transformation, no insertable stages, no choosable destination, and no lineage. The general half of the layer (ETL/ELT, transformation, lineage) remains the enterprise's, met with its own tooling (Airflow, Spark, Kubeflow). Best-in-class movement plus a shipping fixed-function slice is partial capability — moderate, calibrated against VAST's DataEngine (general, event-driven, arbitrary functions — strong) and Dell's Dataloop (general in kind, maturity-gated — the moderate anchor). 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.
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: the enterprise brings its own ETL/orchestration (Airflow, Spark, Kubeflow) today; NetApp's AIDE sync/vectorize/classify pieces are now GA and under re-read for whether they close that half.
Re-read resolved July 12, 2026 under the general-versus-fixed-function criterion (methodology, capability rule 4): AIDE's GA'd pipeline pieces are a purpose-built slice, so the cell holds at moderate with the slice scored as a component. What would move this cell toward strong: arbitrary/insertable transformation stages, destinations beyond AIDE's own surfaces, or lineage tracking — general-pipeline capability, documented.
GPU scheduling, quotas, RBAC, fair-share scheduling, utilization optimization
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.
Open-source (Apache 2.0), NetApp-maintained CSI driver provisioning NetApp storage to Kubernetes for AI and container workloads. The consumed interface is CSI/Kubernetes — a genuine multi-vendor standard: provisioning opinions live in Kubernetes-standard objects (StorageClasses, PVCs) and survive a swap to another vendor's CSI driver without rebuilding the layer. What the driver connects to is NetApp storage, and that capture is scored where it lives, at 1A. Matches the Dell CSI Operator precedent.
NetApp does no GPU scheduling, quotas, or fair-share. That function sits with NVIDIA (Run:ai / GPU Operator) and the enterprise's Kubernetes — the same universal Layer 2A gap that Dell and VAST carry. NetApp orchestrates the data infrastructure, not the AI compute.
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.
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.
Trident is open source (Apache 2.0, NetApp-maintained), but it is a NetApp-storage-specific CSI driver — the Kubernetes interface is portable, the driver is not. NetApp Console was renamed from BlueXP in 2025.
Model serving, agent execution, inference APIs, distributed inference
The model-serving and inference runtime in a NetApp-anchored AI factory is NVIDIA NIM / AI Enterprise — the runtime half of the meet-in-the-middle AIPod, co-sold and channel-integrated, not a NetApp-delivered or NetApp-supported solution. NetApp supplies the governed data beneath.
In FlexPod AI (Cisco + NetApp), model serving comes from Red Hat OpenShift AI. Again a partner runtime; NetApp provides the storage.
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), Red Hat OpenShift AI (FlexPod AI), or open-source OPEA / Intel AI for Enterprise RAG on Intel Xeon 6 AMX (AIPod Mini with Intel) — three partner runtimes, none NetApp's. 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.
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.
The meet-in-the-middle distinction is load-bearing: Dell and Cisco are primes that deliver and support the NVIDIA stack as their own factory (and are credited at 2B); NetApp is the storage half of a channel-assembled co-sell, so the NVIDIA runtime is credited on NVIDIA's row, not NetApp's. Assessed July 13, 2026 (NetApp AIPod Mini with Intel, solution brief SB-4332 + TR-5010): fails the whose-paper test and does not move this cell. Per NetApp's own documentation it is a 'validated reference design,' not a NetApp-paper product — compute is Supermicro (222HA-TN-OTO-37), switch is Arista, the runtime is open-source OPEA / Intel AI for Enterprise RAG cloned from GitHub, and delivery is through distributors and integration partners (Arrow, TD SYNNEX; Insight, CDW, Presidio, Long View). NetApp brings storage plus the reference architecture; it does not sell or support the runtime on its own paper. It is a second meet-in-the-middle path (Intel/OPEA-CPU alongside NVIDIA-GPU), which strengthens the storage-half finding rather than closing it.
Policy-driven placement and resource coordination — the Autonomy Layer
Neither NetApp nor NVIDIA provides a reasoning plane in this stack. As with Dell — which sells the full NVIDIA AI factory as prime and is still Layer 2C gap — NVIDIA's stack (AI-Q, Dynamo) is routing and scaffolding, not policy-driven placement. Selling or anchoring an NVIDIA factory does not create a 2C capability.
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 — a verdict GA does not change: the guardrails shipped (AIDE 9.18.1 U1) and the cell still reads gap, because what shipped governs data, not agents. 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.
Inverted — there is no Layer 2C to borrow. The enterprise retains policy-driven placement and agent governance entirely. NetApp's data guardrails (GA, scored at 1B) govern data, not agents; the meet-in-the-middle NVIDIA stack has no reasoning plane either.
AI Data Engine Data Guardrails reached GA (AIDE 9.18.1 U1) and are scored inside the 1B retrieval component, where they function. At 2C they remain the wrong function — data-access governance, not an agent or reasoning plane; the gap holds.
AI-powered business capabilities — business logic, workflow automation
The application ecosystem delivered alongside AIPod is NVIDIA AI Enterprise — NIM microservices, blueprints, and models — NVIDIA's ecosystem, co-sold through the channel, not a NetApp-curated AI-application program. NetApp supplies the governed data beneath the apps.
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'.
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.
AIPod and FlexPod AI position NetApp storage in AI solutions, but the application logic and ecosystem are NVIDIA AI Enterprise (NIM/blueprints/models) and the customer's — co-sold via the channel, not NetApp-curated.
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 — reached GA and is now scored: the Metadata Engine gives Layer 1A its AI-metadata catalog, and AIDE's vectorization and retrieval endpoints give NetApp a first-party, storage-integrated retrieval surface at Layer 1B (moderate — first-release, license-gated, and hardware-gated to AFX plus Data Compute Node clusters; the software-only deployment is metadata-only). The architect can now deploy NetApp-native AI data governance and retrieval on an AFX estate; everywhere else, the mature data foundation plus data movement remains the deployable core.
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.