# HPE Private Cloud — Fourth Cloud Assessment *Fourth Cloud Control Plane Assessment — HPE Morpheus + VM Essentials on HPE Private Cloud* **Version:** v1.1 **Date:** July 14, 2026 **Status:** complete **Evolution model:** continuous **Source:** HPE Discover 2026 press materials (June 2026) and HPE Discover 2025 (June 2025); HPE Morpheus Enterprise Software and HPE Morpheus VM Essentials product pages and QuickSpecs; HPE Private Cloud Business Edition, Private Cloud Enterprise, and Private Cloud AI product pages; HPE Compute Ops Management product page, QuickSpecs, and subscription-tier documentation; HPE Data Fabric Software and HPE Ezmeral Unified Analytics documentation; HPE AI Essentials documentation; HPE OpsRamp documentation and the OpsRamp Operations Copilot announcement; HPE GreenLake identity-governance and IAM documentation; HPE Alletra Storage MP B10000/X10000 materials; Juniper acquisition close (July 2025) and Apstra/Mist integration coverage; analyst and trade coverage (Futurum, NAND Research, Moor Insights & Strategy, HyperFRAME, Virtualization Review, StorageReview, Network World, TechTarget, Blocks & Files); Fourth Cloud methodology v2.4. GA-versus-roadmap verified against mid-2026 sources; roadmap capability is flagged, not scored. v1.1 prose revision: added the coverage-versus-continuity closing verdict and a maturity-caveat scoping note explaining why this row alone carries it; no score changes. ## One Platform, or One Storefront? HPE Private Cloud, orchestrated by HPE Morpheus with VM Essentials as HPE's own hypervisor, is a genuine Fourth Cloud control plane. This row scores the vendor-recommended path for the audience the instrument primarily serves: the architect building a Fourth Cloud to land new applications on, or to migrate applications to. Where some vendors deploy other vendors' control planes, HPE kept and rebuilt its own. Morpheus supplies the unified orchestration, governance, and self-service surface. VM Essentials supplies a native runtime. Both run under one HPE vendor relationship. The strength concentrates in the operational tri-plane. FC-2A orchestration, FC-2B runtime, and FC-3 catalog all land at the strong band. Morpheus unifies VMs, containers, bare metal, and multi-tier application stacks under one catalog with per-business-unit quota, policy, and approval governance, and the consumer effectively gets workload universality whether or not a single scheduler sits underneath. VM Essentials runs VMs natively with high availability and live migration. The persona-separation and self-service primitives are complete, and observability through OpsRamp ships genuine cross-workload correlation. FC-1 is where the audience split matters, and the instrument states it plainly. On HPE's recommended path, HPE Data Fabric is the data layer, and it is a deep one: a global namespace across the estate, catalog federation, and classification with policy-driven data placement. For the Fourth Cloud native designing around that path, FC-1 is a real strength. For the buyer migrating off an existing virtualization estate who keeps existing or competing storage, Data Fabric's contribution must be weighed heavily. It is a workload-shape-dependent data platform, not a capability the migration inherits, and for that buyer FC-1 reads as a structural gap. The governance metadata, however deep, still lacks workload awareness. It can place data against a residency constraint. It cannot derive where a workload runs. Two structural gaps set the ceiling. FC-2C, the reasoning plane, scores zero. Morpheus places VMs on capacity and topology, and the agentic operations roadmap is IT-operations automation, not compliance-metadata-derived workload placement. HPE holds both prerequisites internally, a strong metadata fabric and its own scheduler, but the derivation engine that would wire them does not exist, and no product with a confirmed timeline closes it. FC-4, the integration fabric, is the second gap portfolio: no managed API platform, no business-process orchestration, no maintained system-of-record connectors. A Kafka-compatible event store and an IT-automation workflow engine are the only partial credit, and both sit low. Identity plane continuity scores 2, partial. GreenLake identity and access management is a real federation spine that pulls Morpheus, VM Essentials, Private Cloud AI, and OpsRamp under one workspace sign-on, but FC-0 substrate identity does not natively control FC-2B runtime execution, and Morpheus carries its own role model federated in rather than one native context. The profile is assembled from several subscriptions under one vendor relationship: Private Cloud with Morpheus and VM Essentials, plus Data Fabric, AI Essentials with Private Cloud AI, OpsRamp, and Compute Ops Management, each named where it carries a score. The buyer's trade is explicit. A broad, mostly generally-available Fourth Cloud control plane, with real orchestration, runtime, and catalog maturity and a deep optional data fabric, in exchange for owning the reasoning plane and a full integration fabric, and for composing the data layer to fit the workload. A closing discipline, and the reason it applies to this row and not the field-established ones. This instrument scores documented capability and names no winner. Every capability here is real. What a document cannot establish is whether the pieces operate as one platform, and that question weighs more here than elsewhere because of when and how the claims were assembled. This control plane is recent: the orchestration layer arrived by acquisition and relaunched in 2025, the owned hypervisor in late 2024, the AI pieces through 2026. The claim is also broad, a full platform stood up across several products the operator crosses in the life of one workload, from Morpheus and VM Essentials to Data Fabric, Private Cloud AI, OpsRamp, and Compute Ops Management. Where integration has years in production behind it, its maturity is a known quantity and the assessment can lean on demonstrated experience. Here it is neither demonstrated nor disproven. Whether identity, policy, state, and telemetry survive the seams, whether Morpheus stays the operational surface after provisioning rather than handing off to separate consoles, whether a firmware event drives workload evacuation and return as one lifecycle, is unverified. Coverage is not continuity. That is the decisive question for this platform, the one a document cannot answer and a score does not capture, and it is settled by operating the stack, not by counting its parts. The gap portfolio counts 10 structural, 6 closeable, 6 opinion, 2 mixed, and 2 vendor-roadmap, a map of what to test, not a rank. ## Scoping note This assessment scores the HPE Private Cloud family — Private Cloud Business Edition, Private Cloud Enterprise, and Private Cloud AI — orchestrated by HPE Morpheus (Morpheus Enterprise Software plus Morpheus VM Essentials, HPE's own KVM hypervisor) under one HPE vendor relationship. HPE's own add-on subscriptions are named inline where they carry a score: HPE Compute Ops Management at FC-0, HPE Data Fabric and HPE Ezmeral Unified Analytics at FC-1 and FC-4, HPE AI Essentials with Private Cloud AI at FC-1 and FC-2B, and HPE OpsRamp at FC-2B. The row scores the vendor-recommended Fourth Cloud path for the audience the instrument primarily serves: the architect building a Fourth Cloud to land new applications on, or to migrate applications to. On that path HPE Data Fabric is the recommended data layer and is scored as such. A second audience — the buyer replacing an existing virtualization estate who retains separate or competing storage — does not inherit Data Fabric, which is a workload-shape-dependent data platform rather than a capability the migration carries with it; for that buyer FC-1 must be weighed as a structural gap. That distinction is named in the FC-1 narratives, not scored twice. Scoring is on generally available capability as of mid-2026; announced and roadmap capability is flagged in the narratives and does not lift a score. This row carries a maturity caveat the instrument's field-established rows do not, and for a specific reason: the HPE control plane is recently assembled and broad in scope, and its integrated operation is not yet demonstrated in production. The instrument scores documented capability the same way for every vendor; whether these products operate as one platform across their seams is unverified here, and it is the question a hands-on validation resolves, not this row. ## Identity Plane Continuity **Score:** 2 **Classification:** partial **Gap ownership:** mixed **Layers in plane:** fc2a, fc2b, fc3 **Layers siloed:** fc0, fc1, fc2c, fc4 HPE GreenLake identity and access management is a genuine federation spine: SAML and OpenID Connect federation to the enterprise identity provider, SCIM provisioning, and dynamic role-based access evaluated per session, with Morpheus, VM Essentials, Private Cloud AI, and OpsRamp consolidating under one workspace sign-on. That federation spans the operational plane from Compute Ops Management and GreenLake through Morpheus orchestration (FC-2A), VM Essentials and Private Cloud AI runtime (FC-2B), and catalog access (FC-3). The plane is partial rather than continuous. Morpheus carries its own role model federated into the workspace rather than one native context; per-runtime identity persists, with governance reaching Morpheus-managed workloads but not every runtime uniformly; and FC-0 substrate identity does not reach FC-2B runtime enforcement. The data fabric governs data access through its own catalog identity model at FC-1, the reasoning plane at FC-2C does not exist, and there is no integration fabric identity at FC-4. **Buyer implication:** No, not natively. FC-0 substrate identity cannot control what application runtimes execute at FC-2B without operator-configured policy bridges. The GreenLake spine federates administrator and operator sign-on across the operational layers, but workload-identity enforcement from substrate to runtime, and reconciling Morpheus's own role model with per-runtime identity, is the enterprise's configuration and bridge burden. The federation is real and reduces the number of identity islands; it does not yet make one identity context enforceable at every layer. ## Layer-by-layer scoring | Layer | Avg score | Status | |---|---|---| | FC-0 · Substrate — Physical & Virtual Substrate | 2.00 | Moderate | | FC-1 · Context — Distributed Data & Context Fabric | 2.75 | Moderate | | FC-2A · Orchestration — Infrastructure Orchestration | 2.40 | Moderate | | FC-2B · Runtime — Execution & Runtime | 3.00 | Strong | | FC-2C · Reasoning — The Reasoning Plane | 0.00 | Absent | | FC-3 · Catalog — Application Distribution and Governance | 2.50 | Moderate | | FC-4 · Integration — Integration Fabric | 0.60 | Absent | **DAPM profile:** Retained 4 · Delegated 4 · Ceded 18 ### FC-0 · Substrate — Physical & Virtual Substrate *The physical foundation the control plane lifecycles — scored on the control plane's relationship to substrate, not on the substrate itself.* #### Hardware lifecycle management *(universal)* **Score:** 3 · **Gap ownership:** structural · **DAPM:** Ceded HPE Compute Ops Management provides cloud-delivered hardware lifecycle management for the HPE ProLiant fleet: firmware, BIOS, and driver baselines with compliance tracking, staged and policy-driven updates, delta-based downloads across large fleets, health monitoring, and provisioning. The enterprise operates a genuine hardware lifecycle plane rather than assuming healthy hardware. The gap from 4 is that the hardware pane and the workload pane are distinct surfaces. Compute Ops Management runs firmware and health; VM Essentials and Morpheus run workloads; the two converge at the operations-view level rather than as one lifecycle operation. Coordinated firmware-to-workload maintenance is generally available only where the hypervisor is VMware and vSphere Lifecycle Manager drives the workload evacuation. An HPE-native path from a firmware event to automated workload draining, patching, and rejoin on HPE's own hypervisor is not shipped. Structural: the distinct-surface reality and the physical operating model hold this below fully integrated, invisible hardware lifecycle. The lifecycle opinions accumulate in HPE-proprietary, HPE-hardware-bound tooling. Ceded. #### Substrate heterogeneity *(universal)* **Score:** 1 · **Gap ownership:** structural · **DAPM:** Ceded The substrate the control plane lifecycles is HPE's own. VM Essentials runs on certified HPE ProLiant (Gen10 Plus and newer, Gen11 recommended), and Compute Ops Management manages firmware and health for the ProLiant and Alletra estate. Multi-vendor reach exists for monitoring only: Compute Ops Management can surface third-party servers for health and insight, but firmware, BIOS, and driver lifecycle through unified primitives remains HPE ProLiant. Third-party host qualification for the VM Essentials hypervisor is roadmap, and the broad heterogeneity that Morpheus provides belongs to workload orchestration rather than substrate lifecycle and is credited at FC-2A. Accelerator handling is GPU passthrough and GPU pooling, generally available, with the control-plane-integrated accelerator story centered on NVIDIA; vGPU in the management interface is not yet generally available. Score 1 reflects unified management of a single vendor's hardware family, which is operational coherence rather than heterogeneity. Structural: the hardware-attach model is a deliberate design choice. The management opinions are HPE-proprietary and HPE-hardware-bound. Ceded. #### Substrate portability *(universal)* **Score:** 2 · **Gap ownership:** structural · **DAPM:** Ceded The same VM Essentials and Morpheus control plane runs on-premises and at the edge, the latter through SimpliVity with VM Essentials, and Morpheus manages public clouds as first-class deployment targets. What the control plane does not do is run on public-cloud substrate: the VM Essentials hypervisor does not run on cloud bare metal, cloud is reached as a managed target through cloud interfaces, and Morpheus Central, delivered as a cloud service, is a governance federation overlay rather than the provisioning control plane running on cloud substrate. Edge consistency is achieved through differently sized appliances rather than one identical artifact everywhere. Score 2 reflects on-premises and edge on one control plane with cloud addressed as a separate managed capability, short of a control plane that runs unchanged across on-premises, cloud, and edge. Structural. The control-plane opinions are HPE-proprietary. Ceded. *Notes: FC-0 shows the shape of hardware ownership. F1=3 because Compute Ops Management is a genuine cloud-delivered firmware-through-health lifecycle plane for HPE's own fleet. F2=1 and F3=2 because that same ownership binds the lifecycled substrate to HPE ProLiant and anchors the control plane on-premises and at the edge, with cloud reached as a managed target rather than substrate the control plane runs on.* ### FC-1 · Context — Distributed Data & Context Fabric *The data fabric the reasoning plane queries for placement decisions — covers the full enterprise data estate, not AI workloads only.* #### Data location and gravity awareness *(universal)* **Score:** 3 · **Gap ownership:** structural · **DAPM:** Ceded On the vendor-recommended path, HPE Data Fabric is the data layer, and it provides a genuine location and gravity picture: a global namespace spanning edge, core, and public cloud across heterogeneous storage protocols, Apache Polaris catalog federation, and a programmatic query interface over unified metadata. The architect designing an estate around this path can ask where data lives across the estate programmatically. Two gaps hold it below 4. No reasoning plane consumes this metadata to derive workload placement, and the coverage is the estate conformed to the fabric rather than any data anywhere. A buyer migrating from an existing virtualization estate who retains separate or competing storage does not inherit this capability; Data Fabric is a workload-shape-dependent data platform, and for that buyer the location picture is bounded to infrastructure telemetry. Structural: the gap from 4 is the absent reasoning-plane consumer, and extending the fabric to an unconformed estate is a data re-architecture rather than a configuration. The namespace and placement opinions are HPE-proprietary; catalog-format portability is not authority. Ceded. #### Governance and compliance metadata *(universal)* **Score:** 2 · **Gap ownership:** structural · **DAPM:** Ceded Data Fabric performs classification, tagging, and policy-driven data mobility across the estate it manages, with Polaris maintaining governance consistency across distributed platforms and object storage adding automatic metadata tagging and policy enforcement for unstructured data. This is real governance metadata. It stops short of the function's defining requirement: the metadata has no workload awareness, so it cannot enforce placement of a workload against a compliance constraint. A new residency requirement can move or pin the data; it cannot derive where a workload runs. Governance also reaches the fabric-conformed estate rather than the full enterprise data estate, and for the migrating buyer who keeps existing storage it does not reach the workloads at all. Score 2 reflects genuine classification and propagation to data placement without workload-placement enforcement. Structural: closing the workload-awareness gap is the reasoning-plane problem, and extending governance to an unconformed estate is a data re-architecture. Ceded. #### Retrieval and context services *(ai-workload)* **Score:** 3 · **Gap ownership:** opinion · **DAPM:** Ceded HPE AI Essentials, included with Private Cloud AI, ships a managed retrieval experience: automatic conversion of source data into embeddings, a managed vector database, automated embedding management and data synchronization, and configurable chunking and retrieval built on NVIDIA NIM microservices. This is platform-native managed retrieval in the base AI offering rather than a bare vector store. The gap from 4 is the on-premises, enterprise-operated ceiling: the enterprise configures and operates retrieval within the platform rather than consuming a fully managed service it never touches. Opinion: closing the gap is configuration within the acquired AI Essentials primitives, not a new capability. The managed retrieval opinions are HPE-proprietary; the underlying vector store is open-source and substitutable. Ceded. #### Data pipeline and lineage *(universal)* **Score:** 3 · **Gap ownership:** closeable · **DAPM:** Delegated HPE Ezmeral Unified Analytics delivers managed machine-learning and analytics pipelines through a curated open-source tool set, with connectors to common enterprise data sources, and Data Fabric adds event streaming and cross-engine lineage through the lakehouse catalog. Primary analytical and machine-learning data types are covered with lineage. The gap from 4 is the traditional and general estate: managed change-data-capture and movement from systems of record and mainframe sources is assembled rather than delivered as one named managed service, and enterprise-wide lineage across every type is partial. Closeable: covering the traditional-estate movement requires acquiring integration capability with its own lifecycle burden. The pipeline stack is curated open-source with real alternatives; lineage within the fabric is the proprietary component. Delegated. *Notes: FC-1 is scored on the vendor-recommended path, where HPE Data Fabric is the data layer, and it is the layer where the two audiences diverge. For the Fourth Cloud native building around that path, F1=3 and F4=3 are real strengths. For the buyer replacing an existing virtualization estate who keeps separate or competing storage, Data Fabric is not inherited by the migration and FC-1 reads as a structural gap. F2 is capped at 2 regardless of audience: the governance metadata has no workload awareness, so it cannot derive placement against a compliance constraint.* ### FC-2A · Orchestration — Infrastructure Orchestration *Unified orchestration of the full enterprise workload portfolio through one control plane — VMs, databases, batch, containers, and AI workloads with shared resource pools, shared quota enforcement, and unified visibility.* #### Workload universality *(universal)* **Score:** 3 · **Gap ownership:** structural · **DAPM:** Ceded HPE Morpheus provides one orchestration and governance surface across VMs, containers, bare metal, and multi-tier application stacks, with a unified catalog, per-business-unit quota, policy, and visibility. HPE's own runtimes cover the major workload types: VM Essentials for VMs, container runtimes for Kubernetes workloads, bare metal, and Private Cloud AI for AI. The consumer requests any workload type from one surface under one governance model. The gap from 4 is that Morpheus is a unifying orchestration plane rather than a single scheduler with shared pools: scheduling and resource pools live in the underlying runtimes, and GPU scheduling is held by the accelerator vendor. Whether one scheduler sits underneath is not visible to the consumer, who effectively receives workload universality. Structural: the delegated-scheduling model and the accelerator-vendor GPU dependency are inherent. The orchestration opinions are HPE-proprietary. Ceded. #### Resource lifecycle automation *(universal)* **Score:** 2 · **Gap ownership:** structural · **DAPM:** Ceded Morpheus and VM Essentials automate provisioning, scaling within capacity, high availability, live compute and storage migration, distributed placement, and blueprint-driven lifecycle. The automation operates within the capacity the enterprise already owns; the platform does not control the physical supply chain. Expandable capacity beyond owned hardware is achievable only through a vendor-managed consumption model, where the vendor pre-stages and operates buffer capacity. That is a managed control plane, structurally distinct from a platform the enterprise operates, and the instrument scores the capability the enterprise operates and sustains rather than the managed path. Score 2 reflects strong automated lifecycle within fixed capacity. Structural by definition: crossing into expandable capacity requires becoming a vendor-managed consumption model, which is outside what the platform itself provides. The lifecycle opinions are HPE-proprietary. Ceded. #### Policy and quota enforcement *(universal)* **Score:** 3 · **Gap ownership:** opinion · **DAPM:** Ceded Policy and quota is core Morpheus capability: role-based access mapped from identity into fine-grained guardrails, a governance and policy engine, per-business-unit quotas, approval workflows, audit trails, and budget enforcement, all across the managed estate from one surface. The gap from 4 is that policy does not propagate automatically to every enforcement layer; network policy and in-cluster Kubernetes policy are configured separately in the underlying platforms. Opinion: the enterprise configures per-layer enforcement using existing Morpheus primitives, not a new capability. The policy opinions accumulate in HPE-proprietary formats. Ceded. #### Substrate lifecycle integration *(universal)* **Score:** 2 · **Gap ownership:** closeable · **DAPM:** Ceded VM Essentials integrates workload lifecycle with host maintenance for VM workloads: maintenance mode drains a host by live-migrating running VMs, high availability recovers workloads from host failure, and distributed placement rebalances. On the VMware path, Compute Ops Management feeds firmware into vSphere Lifecycle Manager. The gap is that firmware and workload maintenance are separate panes on HPE's own hypervisor: there is no automated path from a firmware event to workload draining, patching, and rejoin as one operation, and event-time integration between hardware failures and scheduling is not shipped. Score 2 reflects real maintenance-window integration without firmware-integrated or event-time coordination. Closeable: Compute Ops Management exposes health and event webhooks and VM Essentials exposes maintenance interfaces, so the coordination loop is buildable by the enterprise. Ceded. #### Accelerator and GPU management *(ai-workload)* **Score:** 2 · **Gap ownership:** structural · **DAPM:** Delegated VM Essentials provides GPU passthrough and GPU pooling, discovering host GPUs into an assignable pool, and Private Cloud AI adds multi-tenant GPU isolation and fractional and quota management through the accelerator vendor's software, with GPU observability through OpsRamp. The scheduling intelligence — fractional sharing, quota, and topology awareness — is held by the accelerator vendor rather than native to the control plane, and native vGPU in the management interface is not yet generally available. Score 2 reflects accelerator management through validated integration with scheduling owned by the accelerator vendor. Structural: the accelerator-vendor scheduling dependency is common to the on-premises model. The accelerator software is the de facto standard, substitutable in principle. Delegated. *Notes: FC-2A is the strongest layer alongside FC-2B. F1=3 because Morpheus delivers unified orchestration and governance across the major workload types, scored on the buyer outcome rather than whether one scheduler sits underneath. F2=2 is structural by definition: automated lifecycle within owned capacity, with expandable capacity reachable only through a vendor-managed consumption model the instrument does not score. F3=3 is a Morpheus strength; F4=2 and F5=2 reflect the separate firmware pane and the accelerator-vendor scheduling dependency.* ### FC-2B · Runtime — Execution & Runtime *Execution environments for the full enterprise workload portfolio with consistent developer experience, persona abstraction, and observability.* #### Runtime universality *(universal)* **Score:** 3 · **Gap ownership:** structural · **DAPM:** Ceded HPE's own runtimes execute the major workload types: VM Essentials runs VMs natively with high availability and live migration, container runtimes execute Kubernetes workloads, bare metal is native, and Private Cloud AI executes AI workloads, all provisioned and managed through Morpheus. The gap from 4 is that these are separate execution surfaces under a shared management plane rather than one intent-declared surface, and the developer experience differs by type. The consumer nonetheless runs every major workload type on HPE runtimes through one management surface. Structural: the multi-surface runtime and the AI workload's separate interface are inherent to the composition. The runtime opinions are HPE-proprietary. Ceded. #### Persona abstraction at execution *(universal)* **Score:** 3 · **Gap ownership:** opinion · **DAPM:** Ceded The persona-separation primitives are present and complete across the managed estate: developer intent through the self-service catalog, blueprints, and infrastructure-as-code; operator substrate visibility and override through the governance surface; and security audit through audit trails, role-based access, and approval gates. The catalog and blueprint model shields developers from substrate detail across VMs, containers, bare metal, and application stacks. The gap from 4 is that complete separation is not shipped as uniform defaults across every type, and the AI persona runs through the Private Cloud AI surface. Opinion: extending uniform abstraction uses existing Morpheus primitives. The self-service opinions accumulate in HPE-proprietary formats. Ceded. #### Execution lifecycle and observability *(universal)* **Score:** 3 · **Gap ownership:** mixed · **DAPM:** Ceded HPE OpsRamp ships a genuine cross-workload correlation layer: AI-driven event correlation across VMs, containers, GPU and AI infrastructure, applications, network, and storage in one pane, with automated remediation, and an operations copilot adding agent and large-language-model observability with token-consumption governance. Morpheus provides the execution lifecycle across types. The gap from 4 is that lifecycle and correlated observability are integrated products rather than one plane, and correlation across sources outside the HPE estate is configured. Mixed ownership: for buyers who adopt OpsRamp the extension is configuration; for buyers without it OpsRamp is a separate acquisition. The correlation intelligence is captive to HPE's operations service. Ceded. #### AI inference and agent execution *(ai-workload)* **Score:** 3 · **Gap ownership:** opinion · **DAPM:** Ceded Private Cloud AI delivers platform-native inference in the base offering through NVIDIA NIM microservices, with a managed retrieval pipeline through AI Essentials, as a co-engineered turnkey AI runtime. The score rests on that generally available inference and retrieval. The gap from 4 is the on-premises managed ceiling, and the depth of agent execution: a unified model gateway for governed multi-model access and an agent toolkit for policy enforcement and behavior monitoring are recent or roadmap rather than long-established generally available capability. Opinion: the enterprise operates within the Private Cloud AI primitives to close the ceiling. The inference governance layer is HPE-proprietary; the underlying serving engines are the accelerator vendor's. Ceded. *Notes: FC-2B lands at the strong band across all four functions on generally available capability. F1=3 for native runtimes across the major workload types under one management plane; F2=3 for complete persona primitives; F3=3 for OpsRamp cross-workload correlation shipped as one layer; F4=3 for platform-native inference and managed retrieval, with the model gateway and agent-execution depth flagged as recent or roadmap rather than the basis for the score.* ### FC-2C · Reasoning — The Reasoning Plane *Autonomous, policy-driven placement for ALL workload types — derives placement from live FC-1 and FC-2A metadata without operator rule-writing.* #### Autonomous placement reasoning *(universal)* **Score:** 0 · **Gap ownership:** structural · **DAPM:** Retained Applying the integration-versus-coexistence test: no HPE component derives placement by consuming live data-governance metadata simultaneously with capacity and topology state. Morpheus distributed placement schedules VMs on capacity and topology within a cluster, the policy engine executes operator-written rules, and the agentic operations layer — spanning the operations copilot, agent registry, and telemetry correlation — performs IT-operations automation and root-cause analysis with a human in the loop. Routing and capacity-based scheduling are not reasoning. Applying the workload-universality test: the only autonomous placement is VM-scoped within a cluster. Documented cross-constraint flow: when a new residency requirement arrives, Data Fabric can move or pin the data against it, but an operator must hand-write the workload placement policy; the system does not derive where the workload runs from the constraint. Score 0. HPE holds both prerequisites internally, a strong metadata fabric and its own scheduler, so an eventual reasoning plane would face a low wiring cost, but the derivation engine does not exist and no product with a confirmed timeline closes it. Structural. The enterprise owns the function because nobody provides it. Retained. *Notes: FC-2C is absent, as it is across the on-premises category. What distinguishes HPE is that both prerequisites sit inside the boundary: a strong metadata fabric at FC-1 and a scheduler HPE owns at FC-2A. The gap is the derivation engine that would consume the metadata to place workloads, not the plumbing to feed it, but that engine does not exist and no product with a confirmed timeline addresses it.* ### FC-3 · Catalog — Application Distribution and Governance *The governed surface through which enterprise applications of all types are published, versioned, discovered, and consumed across the enterprise estate.* #### Application catalog and distribution *(universal)* **Score:** 3 · **Gap ownership:** opinion · **DAPM:** Ceded Morpheus provides a governed self-service catalog for VMs, containers, bare metal, application services, and multi-tier application stacks, with governance at publication through authored and validated blueprints and at consumption through role-based access and approval gates. These are application-topology templates rather than a bare deployment mechanism. The gap from 4 is that catalog depth for traditional enterprise middleware is narrower than for containerized and application-stack workloads, short of a uniform native catalog across every type. Opinion: additional application types are configured with existing blueprint primitives. The blueprint opinions are HPE-proprietary. Ceded. #### Application lifecycle governance *(universal)* **Score:** 2 · **Gap ownership:** mixed · **DAPM:** Ceded Morpheus governs the application lifecycle from one surface: blueprint versioning, approval-gated publication and consumption, role-based access, audit trails, policy enforcement, and budget policy across the managed estate. The gap is that the governance surface sits over an estate whose identity plane is federated rather than continuous: Morpheus carries its own role model, and per-runtime identity persists, so a unified audit across every application type still requires bridging identity contexts. Score 2 reflects genuine per-scope lifecycle governance without one continuous identity plane backing a unified audit. Mixed ownership: for buyers who federate everything through the workspace identity provider the bridging is configuration; where cross-runtime identity bridging is required it is closeable. The governance opinions are HPE-proprietary. Ceded. #### Developer experience and self-service *(universal)* **Score:** 3 · **Gap ownership:** opinion · **DAPM:** Ceded Developer self-service is strong: catalog discovery, parameter configuration within guardrails, deployment without operator intervention, and policy-enforced approval gates, extended by a Terraform provider, REST interfaces, a browser cloud shell, and developer project workspaces with continuous integration. The gap from 4 is per-type interface variance across VM, container, and AI self-service, a within-band quality gap rather than a drop. Opinion: consistent entry points are configured with existing primitives. The self-service opinions are HPE-proprietary. Ceded. #### AI application and agent distribution *(ai-workload)* **Score:** 2 · **Gap ownership:** vendor-roadmap · **DAPM:** Ceded Private Cloud AI provides native AI distribution: one-click-deploy AI applications and a role-based model catalog. The AI-specific governance that would distinguish a stronger score — agent tool authorization, model-version enforcement, and output audit — is announced for delivery later in the year through the accelerator vendor's agent toolkit and HPE's agent registration, rather than generally available today. Score 2 reflects native AI distribution without shipped AI-specific governance. Vendor roadmap: specific products with a confirmed timeline are announced to close the gap. The distribution and governance opinions are HPE-proprietary. Ceded. *Notes: FC-3 is a Morpheus strength at F1 and F3. F2=2 because the governance surface sits over a federated, not continuous, identity plane, so a unified audit across every application type still requires bridging identity contexts. F4=2 on generally available AI distribution without shipped AI-specific governance, which is announced for delivery later in the year.* ### FC-4 · Integration — Integration Fabric *Event bus, API management, workflow orchestration, and system connectors connecting enterprise applications to each other and to systems of record — without point-to-point integrations.* #### Event fabric and messaging *(universal)* **Score:** 1 · **Gap ownership:** closeable · **DAPM:** Delegated On the recommended path, HPE Data Fabric includes a Kafka-compatible event store with topics, consumer-group fan-out, offset replay, global replication, and multi-tenancy. It is a data-plane streaming component of a self-operated data platform positioned for data pipelines rather than an operated enterprise application event fabric with schema-registry enforcement, dead-letter handling, and identity propagation across integrations. The platform's own event catalog carries only HPE platform audit and subscription events, not a customer event bus. Score 1 reflects a real streaming engine short of an operated application event fabric. Closeable: a full enterprise event fabric is a separate platform acquisition. The engine is Kafka-compatible with real alternatives. Delegated. #### API management and gateway *(universal)* **Score:** 0 · **Gap ownership:** closeable · **DAPM:** Retained There is no capability for managing the customer's own APIs. The platform's API gateway registers a client application to call HPE's own platform interfaces, a different function from managing the lifecycle of customer APIs. No publication and versioning workflow, rate limiting, transformation, developer portal, or API-level audit for customer APIs exists. Score 0. Closeable through acquiring an API-management platform. The enterprise owns the function because nobody provides it. Retained. #### Workflow and process orchestration *(universal)* **Score:** 1 · **Gap ownership:** closeable · **DAPM:** Retained Morpheus provides genuine IT and infrastructure automation: a task and workflow library, Terraform and Ansible orchestration, provisioning pipelines, and a natural-language orchestration copilot. This is infrastructure automation rather than business-process orchestration; there is no long-running-transaction engine, no saga or compensation, and no business-process modeling. Score 1 reflects basic workflow automation for operational tasks. Closeable: business-process orchestration requires separate tooling. The enterprise owns the business-process function. Retained. #### SaaS and enterprise system integration *(universal)* **Score:** 0 · **Gap ownership:** closeable · **DAPM:** Retained Morpheus advertises a large integration library, but its integrations are infrastructure and IT-service-management tools: hypervisors, clouds, infrastructure-as-code engines, service-management and configuration-management systems, backup, and identity providers. There are no maintained managed connectors to systems of record: no enterprise resource planning, customer relationship management, human capital management, or mainframe integration as a managed service. The service-management tie is IT-service-management, not a system-of-record data connector. Score 0, the most operationally expensive function to own when absent. Closeable through acquiring an integration platform. The enterprise owns the function. Retained. #### AI-native integration *(ai-workload)* **Score:** 1 · **Gap ownership:** vendor-roadmap · **DAPM:** Delegated Generally available today is basic AI interface connectivity: inference endpoints and retrieval reachable and governed by role-based access. The managed AI-integration fabric is roadmap rather than shipped: a unified model gateway for model interface federation is recent and unverified as delivered, the data fabric's tool-connection support for agentic workflows is dated later in the year, and agent governance through the accelerator vendor's toolkit and an agent registry is announced for later delivery. There is no generally available managed tool-connection gateway, agent-to-agent identity propagation, or semantic routing. Score 1 reflects basic AI connectivity below a managed AI-integration fabric. Vendor roadmap: specific products with a confirmed timeline are announced. The connectivity rests on the accelerator vendor's interfaces. Delegated. *Notes: FC-4 is HPE's gap portfolio. F2 and F4 are 0: no customer API management, no maintained system-of-record connectors. F1=1 and F3=1 are the only partial credit, a Kafka-compatible event store within Data Fabric and IT-automation workflow within Morpheus, both short of an operated application event fabric and business-process orchestration. F5=1 on generally available basic AI connectivity, with the managed AI-integration fabric announced for later delivery.*