HPE presents the most structurally interesting comparison to Dell in the 4+1 model because it makes genuine software authority claims that Dell does not. Three capabilities differentiate HPE's architectural position: GreenLake Intelligence (agentic AI mesh using domain-specific LLMs via MCP — HPE-owned Layer 2A/2C for IT operations), the $14B Juniper Networks acquisition (full networking IP stack from silicon to software — owned networking depth that Dell entirely delegates to NVIDIA Spectrum), and the Unleash AI program with Kamiwaza as the chosen Layer 2C orchestration partner (validated in production at Town of Vail).
The AI workload runtime (Layer 2B) remains structurally dependent on NVIDIA AI Enterprise, branded as ‘NVIDIA AI Computing by HPE.’ HPE co-engineers more deeply than Dell — Private Cloud AI is a jointly developed product — but the DAPM implication is the same: Layer 2B model execution authority is Ceded. However, HPE brackets the NVIDIA-controlled Layer 2B with HPE-owned governance above (GreenLake Intelligence at 2A/2C) and below (GreenLake platform at 2A), giving the enterprise governance authority even though it doesn’t control the runtime itself.
Kamiwaza's capabilities span multiple layers — context orchestration (1B), governed data pipelines (1C), agent execution coordination (2B), and decision authority placement (2C) — making it a multi-layer platform, not a point solution. The Town of Vail deployment serves as a by-proxy assessment of Kamiwaza's capabilities across this full span. HPE's DAPM classification for Kamiwaza-provided functions is Delegated — structurally superior to Dell's position where no Layer 2C partner fills the role.
The Cray supercomputing heritage gives HPE a sovereign AI positioning that Dell cannot match — exascale systems for Argonne, HLRS, HammerHAI (EU AI Factory). This is a differentiated Layer 0 capability with implications for sovereign data governance at Layer 1A.
HPE has one of the most credible on-prem AI infrastructure stacks in the market. Its credibility comes from genuine software authority (GreenLake Intelligence, Data Fabric, OpsRamp), depth of networking IP (Juniper/Aruba/Slingshot — three owned fabrics, each captive to its own stack but each representing real engineering investment), sovereign compute heritage (Cray), and a structured ecosystem model (Unleash AI) that deliberately addresses Layer 2C through a chosen partner rather than leaving it unaddressed.
Layer-by-layer status: Layer 0 (HPE Strength), Layer 1A (Solid), Layer 1B (Delegated), Layer 1C (HPE + Open Source), Layer 2A (HPE Strength), Layer 2B (Ceded to NVIDIA), Layer 2C (Retained (IT Ops) + Delegated (AI Workloads)), Layer 3 (+1) (Unleash AI Ecosystem).
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: June 22, 2026. Version: v1.6 - Naming Update.
Raw compute, networking, and acceleration fabric
Intel Xeon 6 / AMD EPYC. HPE iLO management silicon (HPE-owned). Improved perf/watt, security. Foundation for Private Cloud, Private Cloud AI, standalone.
Exascale-class supercomputing. GX5000 unifies AI+HPC. Cray Slingshot interconnect. Liquid-cooled blade (GX240) with up to 16 NVIDIA Vera CPUs, 640 per rack. Deployed at Argonne, HLRS, HammerHAI.
Proprietary DLC supporting up to 400kW per rack with warm water operation. 100% DLC across GX5000 blades. As Blackwell/Vera Rubin density increases, cooling becomes the physical constraint — Cray heritage is genuine differentiator.
Full IP stack: Junos OS, MX routers, QFX switches, SRX firewalls, Mist AI-native ops, Apstra intent-based DC automation. Networking revenue 151.5% YoY to $2.7B Q1 FY2026. DC networking revenue up 380%+. Junos opinions are captive to the Juniper stack — there is no commodity substrate equivalent to x86 that would let the enterprise move these networking opinions to Aruba or Cisco without rebuilding.
HPE-owned high-performance interconnect delivering 400 Gbps at scale with ultra-low tail latency for AI workloads. Distinct from NVIDIA InfiniBand — this is HPE networking IP for the supercomputing fabric. Slingshot opinions are captive to the Cray/HPE HPC stack — there is no commodity substrate that would let the enterprise move these fabric configurations to InfiniBand or Ethernet without rebuilding.
Campus and edge networking with AI-native Central platform. Being retooled on GreenLake Intelligence agentic mesh. Complementary to Juniper's DC focus and Slingshot's HPC fabric. Aruba opinions are captive to the Aruba/HPE stack — there is no commodity substrate that would let the enterprise move campus networking configurations to Juniper or Cisco without rebuilding.
Full-stack AI infra: compute, GPUs, networking, liquid cooling, software, services. Blackwell (RTX PRO 6000 now) through Vera Rubin NVL72 (Dec 2026). Multi-tenancy via MIG with GPU passthrough (Spring 2026). Air-gapped configs for sovereign. NVIDIA Cloud Partner endorsed. STIG-hardened, FIPS-enabled.
GX5000 supports NVIDIA AND AMD GPUs in the same rack architecture: GX440n blade (4 Vera CPUs + 8 Rubin GPUs), GX350a blade (1 AMD Venice CPU + 4 AMD MI430X GPUs), GX250 blade (8 AMD Venice CPUs, CPU-only). Up to 24 GPU blades per rack = 192 Rubin GPUs or 112 MI430X per rack. Neither Dell nor VAST offers multi-GPU-vendor blades in the same platform.
First factory-built offering with embedded DAOS (Distributed Asynchronous Object Storage). Purpose-built I/O acceleration for AI/HPC workloads. Ships early 2026. Complements Alletra at the supercomputing tier.
RTX PRO 6000 Blackwell now. Vera Rubin NVL72 (72 Rubin GPUs, 36 Vera CPUs, NVLink, ConnectX-9, BlueField-4) Dec 2026. All AI acceleration depends on NVIDIA silicon.
Quantum-X800 InfiniBand for Cray GX5000 (144 ports, 800 Gb/s, 2027). ConnectX-9 SuperNICs, BlueField-4 DPUs, NVLink 6th-gen. Competes with HPE’s own Slingshot/Juniper/Aruba in AI fabric — structural tension.
AI Factory at-scale management planned for later 2026. GPU cluster operations, scheduling, resource allocation. HPE AI Factory will support Mission Control for large-scale deployments.
HPE's generic compute hardware is Retained: ProLiant servers and the underlying x86/NVIDIA silicon are a commodity substrate, so the enterprise can swap OEMs (Dell, HPE, Lenovo) without rebuilding workloads. But HPE's proprietary integrated systems are Ceded: the Cray EX/GX supercomputer and the full-stack AI Factory are turnkey, opinion-bearing platforms (proprietary blade form factor, Slingshot fabric, integrated software and services) that cannot be lifted to another vendor as deployed. The commodity-substrate test makes a generic server Retained; it does not make a proprietary supercomputer or a full-stack bundle Retained simply because commodity silicon sits inside it. HPE's networking is a different story. Juniper (Junos), Slingshot, and Aruba each represent deep proprietary opinion stacks with no commodity substrate equivalent. The enterprise cannot move Junos configs to Aruba gear, Slingshot fabric configs to InfiniBand, or Aruba campus configs to Juniper — each is captive to its own platform. All three score Ceded for the same reason Dell's PowerSwitch does. What HPE's networking depth does represent is capability breadth: three purpose-built fabrics (HPC, data center, campus/edge) vs. Dell's single NVIDIA Spectrum-X dependency vs. VAST's OEM networking reliance. The buyer gets more networking capability with HPE. They Cede it to three separate proprietary stacks rather than one. That is a different trade, not a better authority position. Two genuine differentiators remain: (1) Silicon agnosticism: GX5000 supports NVIDIA Rubin AND AMD MI430X in the same rack. Dell's AI Factory is NVIDIA-only under the primary SKU. VAST is NVIDIA-only. The enterprise retains GPU vendor optionality that peers don't offer. (2) Cray heritage for sovereign AI: national labs (Argonne), EU AI Factories (HammerHAI), government deployments where full stack traceability is required. This is a market position, not a DAPM distinction. The Cray K3000 with embedded DAOS adds HPC storage capability at the supercomputing tier that Dell Exascale and VAST DataStore do not provide in a factory-built form factor.
Generic compute: Low borrowed judgment. x86/NVIDIA is a commodity substrate, and ProLiant workloads are portable to Dell, Lenovo, or any other OEM (Retained). Proprietary integrated systems: the Cray EX/GX supercomputer and the AI Factory full-stack bundle are Ceded, their fabric, blade, and software opinions captive and not liftable as deployed. GPU silicon dependency is universal (NVIDIA or AMD); silicon agnosticism in GX5000 provides a hedge that Dell and VAST do not currently offer. Networking: High borrowed judgment across all three fabrics. Junos opinions are captive to Juniper. Slingshot fabric configs are captive to the Cray HPC stack. Aruba campus configs are captive to Aruba's platform. The enterprise Cedes networking authority to three separate HPE stacks. The depth of that networking capability is real; the authority position is Ceded across the board.
HPE Compute XD700 (OCP-inspired AI server on NVIDIA HGX Rubin NVL8, liquid-cooled, early 2027) targets neoclouds and service providers. Similar positioning to Dell's PowerRack but with OCP design philosophy. The three-tier networking portfolio (Slingshot for HPC, Juniper for DC, Aruba for campus/edge) is unique among the vendors assessed. Each fabric is purpose-built and deep — and each is captive to its own proprietary stack. The integration complexity (three platforms, three management tools) is the operational cost of that depth. Argonne, HLRS, HammerHAI (EU AI Factory), Hudson River Trading, and KISTI are named Cray GX5000 customers — reflecting a sovereign and hyperscale customer profile distinct from Dell's enterprise-focused AI Factory base.
Durable, governed data foundation — the Governance Catalog that Layer 2C queries
Disaggregated, all-flash, scale-out. Native file + object on single platform. 16 nodes, 23PB raw. 100% availability guarantee. RDMA-enabled for AI pipeline optimization across training, inference, KV cache. 2.5 PB/hr backup ingest. Storage opinions (configs, tiering, performance tuning) are captive to the HPE platform.
Mission-critical block storage. 6-controller-node scaling (50% more perf vs 4-node). Dual-node fault tolerance. 5:1 data reduction guarantee. Real-time agentic support (v10.6.0): coordinated specialized AI agents for semantic understanding, adaptive reasoning, and prescriptive intelligence. Agents draw from system telemetry metadata, best practices, and accumulated product knowledge across installed base. Storage opinions captive to HPE platform.
Policy-based data placement and movement (tiering) across hybrid environments. Conversational interface and agentic AI assistant for natural language access to global namespace. Enhanced metadata integration for visibility, classification, lineage. Apache Polaris catalog support for Iceberg tables — consistent governance and compliance across platforms. Real-time S3-to-S3 object movement between any S3-compatible storage systems. Data Fabric governance opinions are captive to the HPE platform — Polaris provides open metadata portability but the orchestration layer is proprietary.
Continuous data protection, AI-powered assistant, Microsoft Defender integration, live VMware-to-HPE VM migration. Near-zero RPO/RTO. Replication and recovery opinions are captive to the Zerto/HPE platform.
RDMA via CX-8/CX-9 SuperNICs for GPU-direct storage access. Same acceleration Dell and VAST also use.
HPE’s Layer 1A is a capable storage foundation with genuine HPE-owned governance intelligence. Three characteristics position it in the 4+1 model: First, the B10000’s agentic support architecture (v10.6.0) goes beyond predictive analytics into semantic understanding and adaptive reasoning — a coordinated set of specialized AI agents drawing from telemetry metadata and accumulated product knowledge. This is HPE-owned intelligence at the storage layer, architecturally aligned with GreenLake Intelligence’s domain-specific agent model. Dell’s storage management is infrastructure monitoring (CloudIQ, MetadataIQ indexing). VAST’s Element Store enriches metadata inline at write time. Three different approaches to storage intelligence. Second, Data Fabric v8.1 with Apache Polaris catalog for Iceberg tables provides cross-platform governance that participates in open-standard ecosystems. Dell’s MetadataIQ indexes within Dell storage boundaries. VAST’s Catalog indexes within the VAST namespace. HPE’s Polaris support means governance metadata is portable across platforms — a federated approach vs Dell’s and VAST’s platform-bounded approaches. Third, Data Fabric’s real-time S3-to-S3 object movement enables AI data ingestion from any S3-compatible source into the governed Data Fabric environment. This addresses the heterogeneous enterprise data ingestion problem — similar in function to VAST’s SyncEngine (which ingests from Google Drive, Jira, Confluence, S3) but operating at the storage protocol level rather than the application API level. X10000’s unified file+object on one platform reduces the number of storage engines vs Dell’s portfolio approach (PowerScale for file, ObjectScale for object, Exascale for combined). VAST’s Element Store goes further by collapsing file, object, table, and vector into a single data structure. HPE’s consolidation is at the platform level; VAST’s is at the data structure level.
Low to moderate. HPE owns storage platforms (Alletra X10000, B10000), Data Fabric software, and Zerto outright. GPU acceleration for storage I/O depends on NVIDIA networking silicon (CX-8/CX-9), but the storage intelligence — policy engine, metadata, agentic management agents — is HPE IP. Apache Polaris support is a deliberate governance strategy: by using an open standard for metadata catalog, HPE reduces governance vendor lock-in for its customers. Compare to VAST, where the governance catalog is proprietary (Ceded to VAST). The trade-off: HPE’s open-standard approach is more portable but less deeply integrated; VAST’s proprietary approach is tightly integrated but less portable.
Commvault and Veeam partnerships add data resilience capabilities (Delegated partners at Layer 1A). The agentic support in B10000 is distinct from GreenLake Intelligence: B10000 agents are storage-domain specialists drawing from storage telemetry and product knowledge. GreenLake Intelligence agents are cross-domain (networking + storage + compute). The two agent architectures are designed to complement each other — B10000 agents resolve storage-specific issues autonomously while GreenLake Intelligence correlates cross-domain patterns. Whether these agent systems actually interoperate via MCP or operate independently is an open question. The Data Fabric’s real-time S3 ingestion capability addresses a practical enterprise challenge: AI teams need to pull data from diverse S3-compatible sources (AWS, MinIO, other object stores) into a governed environment for AI pipeline consumption. This is not a differentiating capability on its own (any S3-compatible system can ingest from S3) but the governance integration — data lands in the Data Fabric namespace with policy-based placement and lineage tracking — is the value. Watch-list (HPE Discover 2026, not scored): Alletra MP X10000 auto metadata + governance policies and AI-ready pipelines - Q4 2026.
Low-latency retrieval for RAG — vector/hybrid search, context windows
Global namespace with conversational access for AI-driven retrieval. Federates data across hybrid environments. Natural language queries against namespace. The discovery layer that retrieval pipelines query — Data Fabric knows where data is and what policies govern it. Proprietary retrieval surface captive to HPE platform.
Low-latency file and object access for AI inference pipelines. RDMA via CX-8/CX-9 reduces retrieval latency for RAG. KV cache storage support for inference state persistence. The storage substrate that retrieval reads from. Proprietary storage platform captive to HPE.
In Town of Vail: manages the full context pipeline for document-centric use cases. Identifies documents requiring processing (Section 508 compliance), ingests and extracts content (housing deeds), prepares contextual inputs for agent consumption. Determines what context each agent needs, from which sources, under what governance constraints. This is retrieval orchestration — above the storage layer, below the agent runtime. Governs cross-departmental context routing (legal, housing, admin).
Embedding models (NV-EmbedQA-E5-v5, Mistral7B-v2, Arctic-Embed-L) and reranking in unified microservice. GPU-accelerated retrieval for RAG pipelines on Private Cloud AI. Provides the embedding intelligence that HPE’s storage does not.
Research assistant and enterprise data agent blueprint. Connects enterprise data to AI agents via retrieval pipelines. Available on Private Cloud AI.
HPE’s reference RAG architecture uses NeMo Retriever for embedding, Milvus (open-source) for vector database, LangChain for chain serving. HPE does not own any retrieval intelligence component — it provides storage substrate and deployment platform.
Layer 1B is HPE’s thinnest proprietary layer. HPE provides storage infrastructure (Data Fabric namespace, Alletra RDMA) but does not own a vector database, an embedding engine, or a retrieval framework. The retrieval intelligence stack is entirely NVIDIA (NeMo Retriever) + open source (Milvus, LangChain). The three-vendor comparison at Layer 1B: • Dell: storage (PowerScale/ObjectScale) + Elastic (search intelligence, Delegated ISV) + NVIDIA (cuVS acceleration). Three authorities. • HPE: storage (Alletra/Data Fabric) + NVIDIA (NeMo Retriever, embedding) + open source (Milvus, LangChain). No proprietary retrieval intelligence. When Kamiwaza is added via Unleash AI, it provides governed retrieval orchestration above the storage and embedding layers. • VAST: storage + embedding + vector search + retrieval pipeline all in one platform (InsightEngine, native vector search, DataBase). One authority. HPE’s retrieval gap is structural: the company has no analog to Dell’s Elastic partnership or VAST’s native InsightEngine. This is a deliberate architectural choice — HPE provides infrastructure substrate and delegates retrieval intelligence to NVIDIA and open-source components. When Kamiwaza enters via Unleash AI, the retrieval story changes. Kamiwaza provides governed context orchestration that neither the storage layer nor the NVIDIA retrieval components provide independently: cross-departmental context routing, authority-constrained retrieval, and document-pipeline coordination. In the Town of Vail, this means the Section 508 compliance agent receives only the documents it’s authorized to process, with retrieval governed by department boundaries. This is a layer of retrieval intelligence that storage-native search (VAST) and embedding-accelerated search (Dell+Elastic) don’t address — the governance of who receives what context under what authority. The 4+1 model question: is governed context orchestration a Layer 1B function (retrieval) or a Layer 2C function (governance)? Kamiwaza’s context management spans both — it retrieves content (1B) according to governance policies (2C). The assessment classifies the retrieval function at 1B and the governance function at 2C.
Moderate to high. HPE’s own Layer 1B authority is limited to storage infrastructure. Embedding intelligence is NVIDIA (NeMo Retriever). Vector storage is open source (Milvus). Retrieval framework is open source (LangChain). Governed context orchestration is Kamiwaza (Delegated via Unleash AI). Compare to Dell: Dell delegates retrieval intelligence to Elastic (proprietary ISV partnership) and acceleration to NVIDIA. Dell’s borrowed judgment at 1B is Moderate — split between a proprietary ISV and NVIDIA. Compare to VAST: VAST’s borrowed judgment at 1B is Low — InsightEngine, vector search, and the retrieval pipeline are VAST IP. Only embedding model execution (NIM) is NVIDIA-provided, and InsightEngine is model-agnostic. HPE’s Layer 1B borrowed judgment is the highest of the three vendors because HPE owns the least retrieval IP. The mitigation: Kamiwaza’s governed orchestration adds a unique capability that pure retrieval engines don’t provide.
The HPE Developer Portal’s RAG reference architecture is instructive: NeMo Retriever embedding + Milvus vector DB + LangChain + Llama3-70B. This is a standard NVIDIA reference stack, not an HPE-differentiated architecture. Any NVIDIA partner (Dell, Lenovo, Supermicro) could deploy the identical stack. HPE’s Layer 1B differentiation comes not from the retrieval stack but from the storage substrate below it (Data Fabric governance, Alletra RDMA performance) and the orchestration layer above it (Kamiwaza context governance). The KV cache storage support in Alletra X10000 is worth noting as a Layer 1B/2B bridge: inference state persistence in storage allows agents to maintain context across sessions without holding GPU memory. Dell’s equivalent is the CMX KV cache offload (NVIDIA technology). HPE’s is storage-native. VAST’s CNode-X collocates cache and compute.
Move/transform data — ETL/ELT, lineage, cost-aware movement, KV cache tiering
Policy-based data placement considering performance, sovereignty, costs, compliance. Data lineage and compliance tagging. Agentic AI assistant for automated reporting and data placement decisions. Real-time S3-to-S3 object movement for AI data ingestion from external sources. Proprietary pipeline orchestration captive to HPE platform.
Enterprise-hardened packaging of the full open-source ML pipeline stack: Apache Airflow (workflow orchestration), Kubeflow (ML pipelines + model serving via KServe), Ray (distributed compute), Feast (feature store), MLflow (experiment tracking), Apache Spark (data engineering), Presto SQL (federated query), Apache Superset (visualization). Connectors to Snowflake, MySQL, Delta Lake, Teradata, Oracle. Built through acquisitions: BlueData (2018), MapR (2019), Ampool (2021), Arrikto/Kubeflow team (2023). Open-source substrate — enterprise could swap to alternative packaging of the same tools.
Hybrid and multicloud management, orchestration, migration, automation. VMware-to-HPE VM migration paths. Cloud-native workflow orchestration.
In Town of Vail: orchestrates governed data flows across department boundaries — housing deeds from ingestion through verification to audit across legal, housing, and admin functions. Decision-driven data movement where pipeline logic is governed by authority constraints and compliance policy, not static ETL schedules.
GPU-accelerated data prep, model training, and visualization within Ezmeral Unified Analytics. Up to 29x faster development. Spark acceleration is the primary NVIDIA contribution at Layer 1C.
Pre-built AI application patterns deployed on Private Cloud AI. Pipeline templates, not pipeline infrastructure.
Three vendors, three distinct architectural strategies for Layer 1C: • Dell: acquired Dataloop (proprietary orchestration, no-code/low-code). Dell’s strongest software move, but the broader pipeline layer depends on ISV partners (ClearML, DataRobot, Starburst). Multiple authority boundaries. • HPE: packages the full open-source ML pipeline lifecycle (Airflow → Kubeflow → Ray → Feast → MLflow → Spark) under enterprise-grade guardrails. Four acquisitions (2018–2023) demonstrate deliberate investment. Value is in curation, hardening, support, integration — not proprietary technology. • VAST: built a proprietary DataEngine (event-driven serverless execution on CNodes). Entirely VAST IP. Tightly integrated with storage and retrieval layers. One authority. HPE’s open-source approach creates a specific DAPM trade-off: the enterprise avoids vendor lock-in (Airflow and Kubeflow are portable), but HPE’s authority is in packaging rather than core technology. If Apache Airflow’s community changes direction, HPE is affected. This is a different risk profile than Dell’s (proprietary Dataloop, partner-dependent beyond it) or VAST’s (proprietary DataEngine, VAST-dependent entirely). Data Fabric’s policy-based movement with Apache Polaris governance connects Layer 1C to Layer 2C: data moves according to explicit policies that consider performance, data locality, sovereignty, costs, and compliance. This governance-aware data movement feeds both GreenLake Intelligence (infrastructure decisions) and Kamiwaza (AI workload decisions). Dell’s Dataloop provides orchestration without integrated governance policy. VAST’s DataEngine has Event Broker for data-event-driven movement without an explicit policy engine. When Kamiwaza is selected via Unleash AI, it adds decision-driven pipeline capability: documents move across department boundaries based on decision logic (legal review required? accessibility compliance met? authority approval needed?). This connects infrastructure-level pipeline capabilities to business-level decision flows — where Layer 1C meets Layer 2C.
Low for pipeline packaging and integration (HPE owns Ezmeral, Data Fabric, Morpheus). Underlying components are open-source, limiting deep technical authority but also limiting NVIDIA dependency — RAPIDS for Spark is the only NVIDIA contribution at this layer. Open-source components are substitutable by the enterprise without HPE’s permission. Compare to Dell: Dell owns Dataloop (Retained) but depends on partners for everything else at Layer 1C. Four authority boundaries. Compare to VAST: VAST owns everything at Layer 1C (Retained by VAST, Ceded by the enterprise). One authority but total vendor dependency. HPE’s Layer 1C authority model is distinct: HPE curates and supports, the enterprise can substitute, NVIDIA acceleration is additive not required.
The acquisition history (BlueData 2018, MapR 2019, Ampool 2021, Arrikto 2023) shows deliberate multi-year investment in the data pipeline layer. HPE chose to build this capability rather than delegate entirely to partners. Dell’s Dataloop acquisition is a similar strategic move but more recent (2024) and narrower in scope. The NVIDIA RAPIDS Accelerator for Spark (up to 29x faster) is meaningful but optional — Ezmeral runs without GPU acceleration. Same pattern as VAST’s DataEngine (runs on standard CNodes, CNode-X adds GPU acceleration). Data Fabric’s real-time S3-to-S3 movement bridges Layer 1A and 1C: ingest from external S3-compatible sources into the governed namespace, where policy-based placement takes over.
GPU scheduling, quotas, RBAC, fair-share scheduling, utilization optimization
Consumption-based hybrid cloud (4th gen). Unified VM + K8s management. Pay-per-use AI infrastructure. Dashboard for capacity, utilization, cost. Self-service cloud experience with full lifecycle management. Proprietary management platform — orchestration opinions captive to HPE.
HPE-owned agentic AI framework infused across the entire hybrid stack (not a standalone product). Multiple domain-specific LLMs trained on HPE data, communicating via Model Context Protocol (MCP). Agents form an agentic mesh for inter-agent communication with secure, contextual data sharing. Domain agents for networking (Aruba/Juniper), storage (Alletra), compute (OpsRamp), orchestration, and FinOps. Cross-domain correlation: traces performance issues across application to storage to network chain. Can process real-time infrastructure metrics and execute actions across multiple vendor environments. Human-in-the-loop: agents take action subject to approval. Proprietary agentic framework captive to HPE platform.
Multi-domain agentic system coordinating compute, network, storage, virtualization, and software layers. Use cases: root-cause analysis, explainability, capacity planning. AI-driven alerts, incident management, GPU monitoring, workload observability. Operations copilot with conversational product help and agentic command center. CrowdStrike integration for security monitoring. MCP support for connecting to GreenLake Intelligence and third-party tools. Proprietary management platform captive to HPE.
Model Context Protocol servers built natively into X10000 storage. Enables GreenLake Intelligence agents to communicate directly with storage for data management orchestration. Connects storage operations to the broader agentic mesh via GreenLake Copilot and natural language interfaces. MCP is an open protocol but these servers are captive to Alletra/GreenLake.
Cloud-native server lifecycle management for ProLiant fleet. Compute Copilot for AI-assisted infrastructure operations. Proprietary management platform captive to HPE.
K8s management with ProLiant Gen12. Unified cloud-native + virtualized workload management. Independent scaling for cloud-native workloads. Upgrade path to Morpheus for hybrid/multicloud.
GPU fractionalization for multi-tenancy in AI Factory portfolio.
AI Factory at-scale management. Planned later 2026. GPU cluster ops, scheduling, resource allocation.
Lifecycle management for AI software stack. Pre-integrated with ProLiant.
Layer 2A is where HPE makes its most substantial software authority claim. GreenLake Intelligence is not a rebranded monitoring tool — it is an agentic AI framework with domain-specific LLMs communicating via MCP, designed to be infused across the entire HPE hybrid stack. Four characteristics define HPE’s Layer 2A position: (1) Cross-domain agentic correlation. GreenLake Intelligence agents trace performance issues across application → storage → network chains, coordinating remediation across domains. Dell’s OpenManage and NVIDIA’s Run:ai operate within single domains (rack management and GPU scheduling respectively). VAST’s Polaris orchestrates VAST clusters but not the broader infrastructure around them. (2) MCP as the inter-agent communication standard. GreenLake Intelligence is compliant with MCP, enabling connection to third-party agents and devices. The X10000 has native MCP servers built in. This means the agentic mesh is architecturally open — ITSM systems can collaborate with GreenLake, and third-party infrastructure can be brought under GreenLake management. HPE positions this as ‘the mesh is open to more stitches.’ (3) Multi-vendor infrastructure support. NAND Research notes that GreenLake Intelligence agents can process real-time metrics and execute actions across multiple vendor environments, not exclusively HPE hardware. This extends Layer 2A authority beyond HPE’s own equipment — a broader orchestration scope than Dell’s OpenManage (Dell hardware only) or VAST’s Polaris (VAST clusters only). (4) FinOps agent for workload placement. Orchestration, networking, and FinOps agents collaborate to determine workload placement across private and public clouds. This is an economic placement decision — where should this workload run based on cost, performance, and policy? This function overlaps with Layer 2C territory. Dell’s Layer 2A is split between Dell-managed rack deployment (OpenManage) and NVIDIA-managed GPU scheduling (Run:ai). HPE’s Layer 2A is unified under GreenLake with OpsRamp providing a multi-domain agentic system that coordinates compute, network, storage, virtualization, and software layers. GreenLake’s consumption model (pay-per-use) creates a natural authority surface: HPE maintains an ongoing operational relationship with the infrastructure — metering, capacity management, utilization optimization — that traditional capex purchases don’t provide. The gap: GPU-specific scheduling is still Ceded to NVIDIA (MIG for fractionalization, Mission Control for at-scale management, planned later 2026). HPE orchestrates the infrastructure around the GPU cluster; NVIDIA orchestrates inside it. This is the same Layer 2A boundary as Dell, but HPE’s surrounding orchestration is a unified platform rather than separate point tools.
Low for infrastructure orchestration (GreenLake platform, GreenLake Intelligence, OpsRamp, Compute Ops Management are HPE-owned IP). Moderate for GPU-specific scheduling (MIG, Mission Control are NVIDIA-controlled). The NAND Research caveat is relevant for the DAPM assessment: tight coupling with GreenLake creates potential vendor lock-in for organizations with diverse infrastructure portfolios. However, MCP compliance and multi-vendor agent support partially mitigate this concern — the agentic mesh can extend beyond HPE hardware. Compare to Dell: Dell’s infrastructure orchestration is fragmented (OpenManage for servers, separate tools for storage and networking). GPU scheduling is fully NVIDIA-controlled (Run:ai). No agentic cross-domain correlation. Compare to VAST: Polaris provides fleet-level VAST cluster orchestration (Retained by VAST). DataEngine provides workload scheduling within the data platform. But Polaris doesn’t orchestrate non-VAST infrastructure. GreenLake Intelligence’s multi-vendor, multi-domain scope is broader.
GreenLake Intelligence’s cross-domain correlation and FinOps-aware placement push beyond traditional Layer 2A into Layer 2C territory for IT operations. The assessment classifies it as spanning 2A–2C for IT ops: infrastructure orchestration (2A) + cross-domain governance decisions and economic placement reasoning (2C). This dual classification is important — GreenLake Intelligence is both an orchestrator and a decision-maker. The MCP openness is architecturally significant: by using an open protocol for agent communication, HPE enables third-party integration without custom APIs. ITSM systems (ServiceNow, BMC) can collaborate with GreenLake agents. Third-party infrastructure can be managed. This is an open-ecosystem approach to infrastructure orchestration that Dell’s proprietary OpenManage and VAST’s proprietary Polaris don’t provide. The X10000 native MCP servers represent infrastructure-level agent communication — the storage array itself participates in the agentic mesh as a first-class agent endpoint, not just a managed resource. This is a specific implementation of the 4+1 model’s vision of infrastructure that is natively agent-aware. Watch-list (HPE Discover 2026, not scored): Morpheus Central + intent-based closed-loop network automation + GreenLake Intelligence agent orchestration/copilots - rolling out Q2-Q3 2026 through 2027.
Model serving, agent execution, inference APIs, distributed inference
Co-engineered with NVIDIA. Pre-configured HW+SW stack with four right-sized configurations. Air-gapped capable. Scales to 128 GPUs with network expansion racks. OpsRamp integration for AI workload monitoring. Supports NVIDIA AI-Q, Omniverse, NeMo Retriever blueprints. Multi-tenancy via MIG with GPU passthrough (Spring 2026). The NVIDIA runtime is integral to the stack — the enterprise cannot substitute an alternative inference runtime without rebuilding.
Kubeflow for ML pipeline execution and model serving (KServe). Ray for distributed compute. MLflow for experiment tracking. Enterprise packaging of open-source ML runtime tools. Open-source substrate — enterprise could swap to alternative packaging.
CrewAI integration enables enterprises to build multi-agent solutions on Private Cloud AI. Deloitte Zora AI for Finance deploys on Private Cloud AI as an agentic platform for dynamic executive reporting (financial statement analysis, scenario modeling, competitive analysis). NIM Agent Blueprints provide pre-built agentic workflows. This is an emerging multi-framework agentic surface — not HPE-owned runtime IP but HPE-curated deployment options.
In Town of Vail: coordinates multiple specialized agents — accessibility identification, alt text generation, remediation guidance formatting. Determines which agents run, in what sequence, with what inputs, under what constraints. Enforces human-in-the-loop checkpoints. Manages agent lifecycle at the execution layer. ‘Coordination of multiple specialized AI agents and human workflows to execute multi-step decisions under explicit authority, governance, and audit constraints.’
The AI workload runtime: model serving (Triton), guardrails (NeMo Guardrails), distributed inference, training frameworks (NeMo). Pre-integrated on Private Cloud AI. STIG-hardened, FIPS-enabled for sovereign deployments.
Pre-optimized inference microservices for model deployment. Part of AI Enterprise platform. Available to all NVIDIA partners (Dell, Cisco, Lenovo) — not HPE-specific.
Pre-built agentic AI application patterns: Multimodal PDF Data Extraction, Digital Twins (Omniverse), AI-Q for enterprise data agents. Deployed on Private Cloud AI. Same blueprints available on Dell AI Factory, Cisco HyperFabric, Lenovo Hybrid AI.
Layer 2B reveals a more nuanced runtime architecture than Dell’s because authority is distributed across three actors rather than two. The three-actor model: • NVIDIA provides model execution — Triton (model serving), NeMo Guardrails (safety), NIM (optimized inference), NeMo (training). This is the compute execution layer. Identical across all NVIDIA partners (Dell, Cisco, Lenovo deploy the same stack). • HPE provides the deployment platform — Private Cloud AI (hardware, cooling, lifecycle), Ezmeral (ML runtime packaging), and increasingly an agentic framework surface (CrewAI, Deloitte Zora AI). This is infrastructure + curation. • Kamiwaza provides agent execution coordination (via Unleash AI) — determines which agents run, sequences execution, manages inputs/outputs, enforces execution-time constraints (authority boundaries, audit, human-in-the-loop). This is governance-aware agent coordination above model inference but below Layer 2C policy. This creates a layered runtime: NVIDIA executes individual model inference → Kamiwaza coordinates multi-agent workflows and enforces execution governance → Layer 2C (also Kamiwaza) makes policy decisions about what should run where. The 2B/2C boundary: 2B is execution coordination (how agents run), 2C is decision authority (why agents run, under what governance). The structural comparison across vendors: • Dell: NVIDIA at 2B (model execution + NemoClaw/OpenShell agent runtime). No agent coordination layer beyond NVIDIA. Dell provides packaging and services. • HPE: NVIDIA at model execution + Kamiwaza at agent coordination + CrewAI/ISV frameworks for agent building. Three layers of runtime capability from three sources. HPE provides infrastructure + curation. • VAST: AgentEngine provides a unified agent runtime (execution + coordination + lifecycle + observability) as VAST IP. NVIDIA provides GPU acceleration only. One authority. HPE’s ‘NVIDIA AI Computing by HPE’ branding signals co-engineering, but the DAPM question is precise: can HPE modify, extend, or replace NVIDIA runtime components independently? The answer appears to be no — ‘co-engineering’ means deeper integration and joint validation, not shared IP authority. NVIDIA controls the runtime; HPE controls the platform it runs on. The emerging agentic framework ecosystem (CrewAI, Deloitte Zora AI) on Private Cloud AI is worth noting: HPE is becoming a multi-framework agentic deployment surface, not locked to a single agent runtime. This is a platform strategy — provide the substrate that multiple agentic frameworks can run on — rather than a runtime strategy (build the definitive agent runtime, as VAST is attempting with AgentEngine).
High for AI workload runtime. NVIDIA controls model serving, inference optimization, guardrails, and training frameworks. The same NVIDIA AI Enterprise stack runs on Dell, Cisco, and Lenovo — this is not HPE-specific technology. The mitigating factor is the ‘bracketing’ architecture: HPE retains governance authority at Layer 2A (GreenLake Intelligence, HPE-owned) and delegates governance authority at Layer 2C (Kamiwaza via Unleash AI). The NVIDIA-controlled Layer 2B runtime is sandwiched between two layers where HPE has governance authority. The enterprise has governance coverage even where it doesn’t control execution. Compare to Dell: Dell has NVIDIA at 2B with no governance brackets. No Layer 2C (Absent). Layer 2A is split between Dell (OpenManage) and NVIDIA (Run:ai). The enterprise has neither governance authority above nor unified governance authority below the NVIDIA runtime. Compare to VAST: VAST owns AgentEngine (2B) and is building PolicyEngine (2C). No bracketing needed because VAST controls both the runtime and the governance layer. The enterprise Cedes both to VAST. HPE’s borrowed judgment at 2B is the highest of any layer in the HPE assessment. The bracketing architecture is the mitigation, not the solution.
The CrewAI and Deloitte Zora AI integrations signal that Private Cloud AI is evolving from a single-stack NVIDIA deployment platform into a multi-framework agentic surface. This is architecturally different from both Dell’s approach (NVIDIA-only runtime) and VAST’s approach (proprietary-only runtime). HPE is positioning Private Cloud AI as the substrate that multiple agent frameworks deploy on. The NIM Agent Blueprints (PDF Extraction, Digital Twins, AI-Q) are available identically on Dell AI Factory, Cisco HyperFabric, and Lenovo Hybrid AI. These do not differentiate HPE at Layer 2B. HPE’s differentiation comes from the bracketing architecture (2A and 2C governance around the NVIDIA 2B runtime) and the emerging multi-framework agent deployment model. The bracketing architecture has a structural analog in HPE’s networking story: NVIDIA InfiniBand handles GPU-to-GPU interconnect (HPE doesn’t control it), but HPE’s Juniper/Aruba/Slingshot handles everything around the GPU fabric (HPE owns it). The pattern: cede the NVIDIA-specific function, retain authority over everything surrounding it.
Policy-driven placement and resource coordination — the Autonomy Layer
MCP-based agent communication across infrastructure domains. Domain-specific agents for networking, storage, compute, operations. Cross-domain correlation and autonomous remediation. Layer 2C for IT infrastructure operations — but not for AI workload placement and policy. Proprietary agentic framework captive to HPE platform.
Agentic orchestration and decision routing for AI workloads. Policy-driven placement, mission decomposition, decision authority placement, cross-agent governance. Distributed Data Engines process data at the source without moving it or compromising security. Cross-environment evaluation: rather than treating anomalies as isolated alerts, Kamiwaza evaluates what else is happening across the environment to determine appropriate response. Town of Vail production agents: ARIA (accessibility auditing — independently audits websites, identifies Section 508 issues, provides developer fixes in days vs $1.5M and months for manual audits). Deed restriction processor (reviews documents spanning 60 years, extracts key data, answers compliance questions, generates Excel/PDF reports — work that previously required weeks of manual review). Fire detection coordinator (works with Vaidio/ProHawk video AI, evaluates cross-environment context, triggers workflows, supports operators as conditions change). HPE's chosen Layer 2C for AI workload orchestration, delivered under single-accountable-provider model.
Policy-based data placement considering performance, sovereignty, costs, compliance. Apache Polaris for cross-platform governance. Feeds governance signals into both GreenLake Intelligence (infrastructure) and Kamiwaza (AI workloads). Proprietary policy engine captive to HPE platform — Polaris provides open metadata portability but the policy orchestration layer is proprietary.
GreenLake Intelligence and Kamiwaza are HPE-owned and HPE-Delegated respectively. NVIDIA does not control the governance, placement, or policy reasoning layer in the HPE stack.
This is the most analytically interesting layer in the HPE assessment and where HPE’s approach diverges most from Dell’s. HPE has a two-part Layer 2C story: GreenLake Intelligence provides Layer 2C for IT infrastructure operations: correlates signals across networking, storage, compute to diagnose and resolve infrastructure issues. Routes decisions across domains. Takes autonomous action (subject to approval). Uses MCP for agent communication. HPE-owned IP. Kamiwaza provides Layer 2C for AI workload orchestration: agentic orchestration, decision routing, policy-driven placement, cross-agent governance. Distributed Data Engines process data at the source without data movement. Not an accidental ISV partnership — HPE’s deliberate architectural choice, curated, integrated, validated, and delivered under single-accountable-provider model. The Town of Vail as by-proxy Kamiwaza assessment — specific evidence: • ARIA accessibility agent: independently audits municipal websites, identifies Section 508 issues, provides developer fixes. Manual equivalent: $1.5M, months of work. ARIA delivers in days. This demonstrates decision automation with governance (the agent identifies what needs fixing, recommends how, but human developers implement). • Deed restriction processor: reviews housing documents spanning 60 years in disjointed legacy formats, extracts key data, answers compliance questions, generates reports. Previously required weeks of manual review and data entry in Excel. Single processing errors carry serious legal and financial consequences. This demonstrates governance-aware document intelligence with cross-departmental implications (legal, housing, administrative). • Fire detection coordinator: works with Vaidio video analytics and ProHawk enhanced vision. Rather than treating a video anomaly as an isolated alert, Kamiwaza evaluates what else is happening across the environment and determines the appropriate response. Agents surface relevant information, trigger correct workflows, and support operators as conditions change. This demonstrates cross-environment evaluation — the core Layer 2C pattern of reasoning across multiple data sources and agent outputs. • Deployment velocity: concept to first-phase production in three months. 20–30 additional use cases projected in first year. Additional use cases compose from existing primitives (decision flows, authority boundaries, governance constraints) rather than requiring new infrastructure. • Economic model: fixed-cost infrastructure on the town’s own solar/wind-powered data center. No cloud API token pricing. Billions of tokens without variable costs. • RBAC → REBAC governance: emerged from Kamiwaza’s production behavior. Traditional role-based access breaks when autonomous agents operate across department boundaries. Relationship-Based Access Control constrains agent permissions based on context, not just role. Structural comparison: • Dell: Layer 2C absent. No partner fills this role. No plan visible. • HPE: Layer 2C Retained for IT ops (GreenLake Intelligence), Delegated for AI workloads (Kamiwaza via Unleash AI) — validated in production with named agents and measurable outcomes. • Google: Layer 2C Retained (Inference Gateway + DWS + Knowledge Catalog). Productized and shipping. • VAST: Layer 2C Gap, emerging (Polaris ships as placement abstraction; PolicyEngine + TuningEngine GA end of 2026). Announced at VAST Forward 2026, GA end of 2026.
IT ops Layer 2C: Low — GreenLake Intelligence is HPE-owned IP. AI workload Layer 2C: Moderate — Delegated to Kamiwaza, but deliberately chosen, integrated, and delivered under HPE's accountability. Structurally stronger than Dell's position because the function exists and someone is accountable. The risk is partner dependency, not capability absence.
Strategic question: is Delegated Layer 2C transitional (HPE eventually builds/acquires orchestration IP) or permanent (HPE’s value is ecosystem curation, not owning every layer)? Town of Vail evidence suggests HPE is comfortable with the ecosystem model — and that it works operationally. The RBAC → REBAC governance shift from Town of Vail validates the 4+1 model’s claim that Layer 2C requires governance architecturally distinct from Layer 2A infrastructure RBAC. Watch-list (HPE Discover 2026, not scored): native agent registry + governance via GreenLake Intelligence, and Private Cloud AI secure cross-framework agent registration - core GA July 2026, agentic observability/data intelligence Q4 2026. Directionally shifts HPE 2C from Kamiwaza-delegated toward HPE-native, but it is Intelligence-2C (governance), not placement. Revisit at GA.
AI-powered business capabilities — business logic, workflow automation
Curated (not open) ISV partner ecosystem. HPE is ‘highly selective’ with its ISV pool. 26+ members focused on different AI use cases from vision AI to agentic analytics. Validates interoperability, provides unified deployment and support. Positions HPE as ‘one accountable provider.’ Field motion targets decision friction, not infrastructure features. Training, certifications, and enablement support for partners. India-based partners taking locally developed AI use cases into global markets.
Pre-configured foundation for ISV solutions. Supports NVIDIA blueprints and partner applications. Air-gapped for regulated industries. Now includes dedicated turnkey development system for fast-tracking AI project validation. Evergreen and always current.
Multi-agent automation framework pre-installed on HPE Private Cloud AI hardware. Enables enterprises to rapidly build and deploy tailored AI agents across industries: finance, healthcare, defense, retail, manufacturing, telecom, energy. On-premises deployment ensures data never leaves enterprise control.
Agentic AI solution reimagining executive reporting. Dynamic, on-demand, interactive experience driven by autonomous AI. Use cases: financial statement analysis, scenario modeling, competitive and market analysis. Deployed on Private Cloud AI. HPE is adopting internally first. Available worldwide.
AI agent platform for business users at enterprise scale. Completely autonomous specialized AI agents without requiring data science or ML engineering expertise. Auto-builds, coaches, and deploys AI agents across on-prem, hybrid cloud, and edge.
Pre-built AI application patterns (Multimodal PDF Extraction, Digital Twins, AI-Q) and inference microservices. Deployed on Private Cloud AI. Same blueprints available across all NVIDIA partners.
HPE correctly does not build Layer 3. The Unleash AI program is the most structured ecosystem curation approach among the infrastructure vendors assessed. Three characteristics define HPE’s Layer 3 approach: (1) Curated, not open. HPE is ‘highly selective’ with 26+ ISV members. Each partner is chosen for a specific AI use case domain and validated for interoperability. This is a deliberate contrast to Dell’s broader ISV partnership approach (more partners, less curation) and VAST’s smaller, focused ecosystem (CoreWeave, TwelveLabs, CrowdStrike). (2) Micro-focused agent model. Kamiwaza’s Luke Norris describes the approach: ‘tens if not hundreds of different agents that are micro-focused on particular jobs’ rather than one monolithic model. This is the operational philosophy behind Unleash AI — specialized agents from specialized partners, coordinated by Kamiwaza’s orchestration layer. (3) Pre-installed frameworks. CrewAI comes pre-installed on Private Cloud AI hardware. This is a different model than Dell’s (deploy NVIDIA NIM/NemoClaw as post-purchase software) or VAST’s (AgentEngine is the platform). HPE delivers the agent development framework as part of the infrastructure purchase. With Kamiwaza correctly positioned at Layer 2C (not Layer 3), the ecosystem layer map clarifies: • HPE provides infrastructure authority (Layers 0–2A) • Kamiwaza provides orchestration authority (Layer 2C, spanning 1B/1C/2B) • NVIDIA provides model execution runtime (Layer 2B) • ISVs provide domain applications (Layer 3): Deloitte Zora AI (finance), Aible (business users), ProHawk (video), Vaidio (vision AI), Blackshark.ai (geospatial), Gambit (citizen engagement) • Cross-cutting partners: CrowdStrike (security), Fortanix (confidential computing), Commvault/Veeam (data resilience), Red Hat (OS/K8s), SHI (integration services) The Town of Vail validates the ‘appliance-like operating model’ — unified deployment, lifecycle management, single escalation path. The coordination overhead that typically kills multi-vendor ecosystem solutions is addressed by HPE’s single-accountable-provider model and Kamiwaza’s orchestration layer. The SiliconANGLE analysis (May 2026) frames this as the emerging default for enterprise AI: ‘curated AI ecosystems’ where customers combine infrastructure, models, orchestration platforms, and ISV tooling without stitching every component together manually. HPE’s position is explicitly not a vertically integrated AI stack — it is a curated substrate model.
Distributed across partners, architecturally correct for Layer 3. Each partner maps to specific layers with identifiable authority boundaries. The structural comparison with Dell and VAST at Layer 3: • Dell’s ecosystem is load-bearing: ISV partners provide infrastructure-level functions (Cohere North for agent orchestration, DataRobot for lifecycle management) that Dell’s platform lacks. Remove Cohere North and Dell loses agent workflow orchestration. • HPE’s ecosystem is curated: ISV partners provide domain applications (Layer 3) while Kamiwaza provides orchestration (Layer 2C). Remove Deloitte Zora AI and HPE loses a finance use case, not a platform capability. • VAST’s ecosystem is additive: the platform is architecturally self-sufficient through Layer 2C. Partners add vertical use cases (TwelveLabs for video AI). Remove TwelveLabs and VAST loses a use case, not a platform function. HPE’s ecosystem structure is closer to VAST’s (additive) than Dell’s (load-bearing) at Layer 3, with the important distinction that HPE’s Layer 2C orchestration is Delegated to an ecosystem partner (Kamiwaza) rather than Retained as proprietary IP (VAST’s PolicyEngine).
The CrewAI pre-installation model is worth tracking: HPE hardware arrives with an agentic development framework already installed. This is a different go-to-market motion than selling infrastructure and then layering software. If this becomes the standard for Private Cloud AI, HPE is bundling Layer 3 development capability into the Layer 0 purchase. Deloitte and Aible represent enterprise-grade ISV deployments on Private Cloud AI — global SI (Deloitte) and AI platform vendor (Aible) choosing HPE’s infrastructure for agentic deployment. Dell’s equivalent is OpenAI Codex, SpaceXAI Grok, and ServiceNow. VAST’s equivalent is CoreWeave and TwelveLabs. Different ISV profiles reflect different customer bases. The SiliconANGLE ‘curated AI ecosystems’ framing from May 20, 2026 (one day ago) positions HPE’s Unleash AI approach as the emerging industry default. Whether this framing holds or whether vertically integrated stacks (VAST) or hyperscaler-controlled ecosystems (Google) prove more durable is an open question for the 4+1 assessment series.
HPE presents the most structurally interesting comparison to Dell in the 4+1 model because it makes genuine software authority claims that Dell does not. Three capabilities differentiate HPE's architectural position: GreenLake Intelligence (agentic AI mesh using domain-specific LLMs via MCP — HPE-owned Layer 2A/2C for IT operations), the $14B Juniper Networks acquisition (full networking IP stack from silicon to software — owned networking depth that Dell entirely delegates to NVIDIA Spectrum), and the Unleash AI program with Kamiwaza as the chosen Layer 2C orchestration partner (validated in production at Town of Vail).
The AI workload runtime (Layer 2B) remains structurally dependent on NVIDIA AI Enterprise, branded as ‘NVIDIA AI Computing by HPE.’ HPE co-engineers more deeply than Dell — Private Cloud AI is a jointly developed product — but the DAPM implication is the same: Layer 2B model execution authority is Ceded. However, HPE brackets the NVIDIA-controlled Layer 2B with HPE-owned governance above (GreenLake Intelligence at 2A/2C) and below (GreenLake platform at 2A), giving the enterprise governance authority even though it doesn’t control the runtime itself.
Kamiwaza's capabilities span multiple layers — context orchestration (1B), governed data pipelines (1C), agent execution coordination (2B), and decision authority placement (2C) — making it a multi-layer platform, not a point solution. The Town of Vail deployment serves as a by-proxy assessment of Kamiwaza's capabilities across this full span. HPE's DAPM classification for Kamiwaza-provided functions is Delegated — structurally superior to Dell's position where no Layer 2C partner fills the role.
The Cray supercomputing heritage gives HPE a sovereign AI positioning that Dell cannot match — exascale systems for Argonne, HLRS, HammerHAI (EU AI Factory). This is a differentiated Layer 0 capability with implications for sovereign data governance at Layer 1A.
HPE has one of the most credible on-prem AI infrastructure stacks in the market. Its credibility comes from genuine software authority (GreenLake Intelligence, Data Fabric, OpsRamp), depth of networking IP (Juniper/Aruba/Slingshot — three owned fabrics, each captive to its own stack but each representing real engineering investment), sovereign compute heritage (Cray), and a structured ecosystem model (Unleash AI) that deliberately addresses Layer 2C through a chosen partner rather than leaving it unaddressed.