# IBM / Red Hat OpenShift AI — 4+1 Layer AI Infrastructure Assessment

> Mapped to the 4+1 Layer AI Infrastructure Model  
> Version: v1.0 — Draft, Editorial Review Pending · Date: May 23, 2026  
> Source: IBM Think 2026, Red Hat Summit 2026, Red Hat AI 3.4 GA, watsonx Orchestrate next-gen preview, IBM Sovereign Core GA, IBM Concert public preview, IBM Confluent acquisition, Granite 4.1 release, analyst coverage (SiliconANGLE, NAND Research, Futurum Group, ECI Research)  
> Published by: The CTO Advisor LLC · thectoadvisor.com  
> Author: Keith Townsend

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

## Executive Summary

IBM / Red Hat is the only vendor in this assessment series attempting to build an enterprise AI operating model from middleware outward. Where Dell builds upward from hardware, VAST builds upward from storage, and Google builds downward from model intelligence, IBM builds from the platform layer — Red Hat OpenShift as the universal substrate — and extends authority in both directions: downward into infrastructure governance (Sovereign Core, Concert) and upward into agent orchestration (watsonx Orchestrate). The platform is the distribution vehicle, not the value. The value is the governance and orchestration intelligence that rides on top.

The critical analytical lens for IBM is separating defensible proprietary IP from open-source packaging. The majority of IBM's AI platform capabilities — OpenShift (Kubernetes), vLLM (inference), KServe (model serving), Ray (distributed compute), Kubeflow (ML pipelines), MLflow (experiment tracking), Tekton (CI/CD), even InstructLab (model customization) — are open-source projects that run identically on VMware Tanzu, Amazon EKS, or bare Kubernetes. An enterprise could replicate most of IBM's Layer 2A/2B capabilities on any CNCF-compliant Kubernetes distribution. IBM's structural moats — capabilities that cannot be replicated without IBM — are concentrated in a narrow but strategically critical band: watsonx.governance (cross-platform AI assurance), watsonx Orchestrate (agentic control plane), Confluent integration with watsonx.data (governed real-time streaming), and Sovereign Core (runtime sovereignty). These are the components where IBM provides genuine authority above the Kubernetes baseline.

IBM does not own compute silicon, does not own GPU scheduling, does not own networking fabric, does not own a high-performance AI-optimized storage platform, and does not own a frontier foundation model. Layer 0 is entirely Delegated or Absent — IBM provides no compute hardware, no server chassis, no networking switches, no cooling infrastructure, and no GPU fabric interconnect. IBM would be perfectly content for customers to run Layers 1A through 3 on a Dell AI Factory, HPE Private Cloud AI, or any OEM hardware. IBM's business model depends on someone else solving Layer 0.

The consulting and services model reinforces the open-source strategy. IBM Consulting (~160,000 consultants) provides implementation expertise for the AI platform — but consulting is a competitive services market, not a platform dependency. Enterprises switch from IBM Consulting to Deloitte or Accenture for platform support the same way they switch SAP BASIS support providers: the structural moat is the platform IP (watsonx.governance, Orchestrate), not the services engagement. IBM Consulting is a competitive advantage in the services market, not a structural advantage in the platform architecture.

The structural question for IBM is whether governance and orchestration authority — owning the narrow band of non-substitutable AI control plane software while everything else is open-source — is more durable than infrastructure authority (Dell, HPE), storage authority (VAST), or model authority (Google). The 4+1 model suggests this bet is architecturally sound — Layer 2C is where authority concentrates — but IBM must prove that watsonx Orchestrate's control plane is substantive, not just well-named, and that watsonx.governance's cross-platform assurance creates sufficient switching costs to justify the subscription when the rest of the stack is free.

## Layer Status

| Layer | Status | Classification |
|---|---|---|
| Layer 0 | ○ Delegated to Partners | Compute & Network Fabric |
| Layer 1A | ◑ Governance Strength, Storage Gap | Data Storage & Governance |
| Layer 1B | ◑ Open-Source Assembled | Context Management & Retrieval |
| Layer 1C | ● Confluent + Open-Source Pipeline | Data Movement & Pipelines |
| Layer 2A | ● OpenShift Strength | Infrastructure Orchestration |
| Layer 2B | ◑ Open-Source Runtime + NVIDIA | Application Runtime & Execution |
| Layer 2C | ◑ Most Explicit 2C Claim | Agentic Infrastructure — The Reasoning Plane |
| Layer 3 (+1) | ◇ Consulting-Led Ecosystem | AI Application Layer — The Value Plane |

## DAPM Profile

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

## Strongest Layers

- **Layer 1C** (Data Movement & Pipelines) — Confluent + Open-Source Pipeline
- **Layer 2A** (Infrastructure Orchestration) — OpenShift Strength

## Gap Areas

- **Layer 0** (Compute & Network Fabric) — Delegated to Partners

## Layer-by-Layer Detail

### ○ Layer 0: Compute & Network Fabric

*Raw compute, networking, and acceleration fabric*  
**Status:** Delegated to Partners

**Red Hat Enterprise Linux for NVIDIA** [DAPM: Delegated]  
RHEL 26.01 with Day 0 Blackwell support. Co-engineering for Vera Rubin. Validated driver, firmware, and runtime integration for NVIDIA AI Factory deployments on OpenShift. Integration work, not hardware authority.

**Red Hat AI Factory with NVIDIA (Software Platform)** [DAPM: Delegated]  
Co-engineered software stack: Red Hat AI Enterprise + NVIDIA AI Enterprise. Unified lifecycle management across RHEL AI, OpenShift AI, Red Hat AI Enterprise. Not a hardware product — a validated software integration path that runs on OEM hardware IBM does not provide.

**Multi-Accelerator Platform Support (OpenShift AI 3.4)** [DAPM: Delegated]  
NVIDIA GPU, AMD GPU (ROCm), Intel Gaudi, IBM Spyre (Tech Preview). Each accelerator uses a different vLLM ServingRuntime variant for KServe. Broadest accelerator support of any AI platform assessed — but this is Layer 2A/2B software integration, not Layer 0 hardware authority.

**No Networking Fabric IP** [DAPM: Absent]  
IBM provides no networking hardware, no GPU fabric interconnect, no software-defined AI networking. OpenShift SDN handles container networking but not the GPU-to-GPU fabric that determines distributed training performance. East-west bandwidth is entirely OEM-dependent. Compare to Dell (PowerSwitch/Spectrum), HPE (Juniper + Slingshot + Aruba), AWS (EFA/SRD).

**Gap Analysis:** IBM does not own compute silicon, server hardware, networking switches, cooling infrastructure, or AI-optimized network fabric. This is the emptiest Layer 0 of any vendor assessed. Dell owns PowerRack/PowerEdge/PowerSwitch/PowerCool. HPE owns ProLiant/Cray/Juniper/Slingshot/Aruba. VAST co-designs CNode-X storage hardware. Google owns TPUs and custom networking. AWS owns Trainium and EFA/SRD. IBM owns none of these.

IBM's Layer 0 story is entirely indirect: Red Hat OpenShift runs on any x86/ARM hardware from any OEM. This is presented as a strength (hardware agnosticism, no vendor lock-in) but in 4+1 terms it means IBM has no Layer 0 authority whatsoever. Abstraction is not authority. Layer 0 defines what physical capabilities exist — compute density, thermal envelope, east-west bandwidth, accelerator topology. IBM has no opinion on any of these because IBM provides none of them.

The networking gap is particularly significant for AI workloads. GPU-to-GPU bandwidth determines distributed training performance. Dell has PowerSwitch (NVIDIA Spectrum silicon). HPE owns Juniper + Slingshot for HPC fabric. AWS built EFA with SRD custom transport. IBM has no networking IP — not hardware, not software-defined networking for GPU fabrics. OpenShift's SDN handles container networking, not the GPU fabric networking that AI training requires. When an enterprise runs distributed training across 64 GPUs on OpenShift, east-west bandwidth depends entirely on whatever the OEM provided. IBM contributes nothing.

The Red Hat AI Factory with NVIDIA co-engineering is significant: Day 0 Blackwell support, Vera Rubin co-engineering, NVIDIA Run:ai integration. But this is validation and integration work, not silicon or fabric authority. The same NVIDIA software stack runs on Dell, HPE, and Lenovo hardware.

Note: IBM Z/Power with Telum on-chip AI inference is classified at Layer 3 (AI Application Layer), not Layer 0. Telum's value is transactional AI inference co-located with enterprise ledgers (banking, insurance) — this is an application-layer advantage where AI capability is adjacent to business data, not an infrastructure fabric capability. The same logic applies to SAP HANA on dedicated hardware: the value is in the application adjacency, not the compute fabric.

**Borrowed Judgment:** Total at Layer 0. IBM borrows all compute, networking, cooling, and fabric judgment from OEM partners and NVIDIA. The enterprise retains hardware vendor choice — a genuine governance benefit — but IBM adds no proprietary hardware value at any sub-layer: no silicon, no thermal engineering, no network fabric, no rack integration. Compare to Dell (retains mechanical/thermal/rack authority), HPE (retains networking end-to-end post-Juniper, cooling via Cray DLC, silicon agnosticism within owned chassis), VAST (retains storage hardware co-design with CNode-X).

The abstraction-as-authority argument fails the 4+1 test. OpenShift abstracting hardware is a Layer 2A capability (infrastructure orchestration), not a Layer 0 capability. Layer 0 asks: what physical capabilities does the vendor provide? IBM's answer: none.

### ◑ Layer 1A: Data Storage & Governance

*Durable, governed data foundation — the Governance Catalog that Layer 2C queries*  
**Status:** Governance Strength, Storage Gap

**watsonx.governance** [DAPM: Retained]  
Enterprise AI governance: Governance Graph (connected map of AI assets, policies, risks, regulations), model monitoring (bias, drift, fairness), agentic monitoring and security, regulatory library (EU AI Act, HIPAA, GDPR). Cross-platform: governs IBM, OpenAI, AWS, Meta models. IDC named IBM a Leader in AI governance.

**watsonx.data (Data Lakehouse)** [DAPM: Retained]  
Open data lakehouse with Presto and Spark engines, Iceberg table format. Shared metadata layer across clouds and on-premises. GPU-accelerated Presto (private preview). Context layer for AI-queryable metadata (private preview). watsonx.data intelligence provides data lineage, classification, quality, and Master Data Management.

**IBM Confluent (Real-Time Streaming)** [DAPM: Retained]  
Kafka + Flink + Tableflow integrated into watsonx.data. Zero-copy data sharing: query live Kafka streams as Iceberg tables without ETL. $11B acquisition positions IBM as the only infrastructure vendor with owned real-time streaming substrate.

**IBM Storage Ceph + IBM Storage Fusion** [DAPM: Retained]  
Ceph: distributed S3-compatible object storage for watsonx.data lakehouse. Fusion: storage services for OpenShift applications with data caching and acceleration. Storage Fusion HCI provides hosted platform for watsonx on-premises. Competent but not AI-optimized at competitor level.

**IBM Sovereign Core (Data Sovereignty)** [DAPM: Retained]  
GA May 2026. Software platform enforcing data sovereignty across four pillars: operational, data, technology, AI sovereignty. Embeds policy at infrastructure runtime. Built on Red Hat OpenShift. Mistral AI as first certified model partner. Ensures data residency, model execution, and inference all operate within sovereign boundary.

**Gap Analysis:** IBM's Layer 1A is structurally split: strong governance, moderate storage.

The governance stack is the strongest in this assessment. watsonx.governance provides end-to-end AI lifecycle governance — model monitoring, bias detection, drift monitoring, regulatory compliance (EU AI Act, HIPAA, GDPR), and a Governance Graph that maps relationships between AI assets, policies, risks, and regulatory requirements across platforms. Unlike Dell's Trust3 AI (partner overlay) or VAST's PolicyEngine (proprietary, platform-bounded), watsonx.governance operates across IBM and third-party platforms (OpenAI, AWS, Meta). This is the only cross-platform AI governance solution assessed.

The watsonx.data lakehouse provides a governed data foundation with Presto and Spark engines, Iceberg table format, and shared metadata across cloud and on-premises. IBM Storage Ceph provides S3-compatible object storage. IBM Storage Fusion provides storage services for OpenShift applications. The Confluent acquisition adds real-time streaming (Kafka + Flink + Tableflow) with zero-copy data sharing — AI models can query live Kafka streams as Iceberg tables without ETL.

But the storage infrastructure itself is not AI-optimized at the level of competitors. Compare: Dell Exascale provides 10+ PB/rack unified file+object+fast-file with MetadataIQ indexing billions of files. HPE Alletra X10000 provides unified file+object with Data Fabric policy-based placement. VAST Element Store collapses file, object, table, and vector into a single governed data structure. IBM Storage Ceph is competent distributed object storage but lacks the AI-specific metadata enrichment, inline embedding, or vector-native capabilities of Dell, HPE, or VAST storage platforms.

The watsonx.data intelligence layer (data lineage, automated classification, Master Data Management, data quality) partially compensates by providing governance above storage — but the storage layer underneath is less performant and less AI-native than competitors' purpose-built solutions.

**Borrowed Judgment:** Low for governance (watsonx.governance, watsonx.data intelligence are IBM IP). Moderate for storage (IBM Storage Ceph and Fusion are IBM-owned but lack AI-specific optimizations). Low for streaming data (Confluent is now IBM-owned post-acquisition). The cross-platform governance capability is unique: watsonx.governance monitors models running on OpenAI, AWS, or Meta — not just IBM. This is the only assessed solution where governance authority is deliberately designed to extend beyond the vendor's own platform boundary.

### ◑ Layer 1B: Context Management & Retrieval

*Low-latency retrieval for RAG — vector/hybrid search, context windows*  
**Status:** Open-Source Assembled

**OpenShift AI Model Serving (KServe + vLLM)** [DAPM: Retained]  
KServe for model serving orchestration. vLLM as primary inference runtime with support for NVIDIA, AMD, Intel Gaudi, and IBM Spyre accelerators. Serverless (Knative) and RawDeployment modes. Autoscaling based on request concurrency.

**InstructLab (Open-Source Model Customization)** [DAPM: Retained]  
IBM-led open-source project for enterprise model customization. Structured taxonomy-based knowledge contribution without full retraining. Reduces dependency on model provider for domain-specific retrieval quality. Community-driven knowledge curation.

**Vector Database Integration (External)** [DAPM: Delegated]  
OpenShift AI supports deployment of Milvus, Elasticsearch, pgvector, and other vector databases as containerized workloads. No IBM-owned vector database — enterprise selects and manages. Integration with watsonx.data for hybrid structured+unstructured queries.

**Gap Analysis:** Applying the Kubernetes-baseline test: IBM has zero defensible IP at Layer 1B. Every component — KServe (CNCF), vLLM (open-source), Milvus (open-source), InstructLab (Apache 2.0), Granite Guardian (Apache 2.0) — runs identically on VMware Tanzu, Amazon EKS, or bare Kubernetes without IBM involvement. A competent ML engineering team can deploy the same retrieval stack on any CNCF-compliant cluster without IBM licensing, IBM consulting, or IBM support. This is IBM's weakest layer from a defensibility standpoint.

The retrieval capability exists and works. The enterprise can build effective RAG pipelines on OpenShift AI. But nothing in the pipeline is IBM-specific. Compare:

• VAST: InsightEngine provides end-to-end embedding + vector search + retrieval pipeline as a single integrated system on the same Element Store. Embeddings trigger the moment data lands — vectors are always current with source data. One authority, zero integration seams. This is proprietary IP that cannot be replicated outside VAST.

• Dell: Data Search Engine (Elastic-powered) + MetadataIQ + NVIDIA cuVS. Three-party dependency, but MetadataIQ is Dell-proprietary metadata integration — a defensible asset. The Elastic partnership provides search intelligence Dell doesn't own but has engineered deep integration with.

• HPE: Data Fabric namespace + NVIDIA NeMo Retriever + Milvus/LangChain. HPE has proprietary storage infrastructure underneath but no proprietary retrieval intelligence. When Kamiwaza enters via Unleash AI, it adds governed context orchestration — a defensible Layer 1B/2C capability.

• IBM: Everything open-source. No proprietary vector database, no proprietary embedding pipeline, no proprietary search intelligence, no inline metadata enrichment at the storage layer. IBM provides the Kubernetes platform on which open-source retrieval components run. The platform is the value — but the platform is Layer 2A, not Layer 1B.

The structural seam Gemini correctly identifies: context management exists as a distinct software layer on top of storage, not inline with data writes. IBM's architecture requires explicit pipeline configuration for embeddings. VAST's architecture makes embeddings structural. Dell's MetadataIQ makes metadata indexing structural. IBM has no structural retrieval integration — it's all application-layer assembly.

InstructLab is IBM's most distinctive contribution — but it's a governance innovation (who controls what the model knows?) rather than a retrieval innovation. It's also Apache 2.0 and runs on any platform. The distinction matters: InstructLab is IBM-led community innovation, not IBM-owned defensible IP.

watsonx.data's Context layer (private preview) may change this assessment. If contextual metadata becomes natively queryable for RAG within the governed lakehouse, IBM would have a proprietary retrieval integration point. But private preview is not production.

**Borrowed Judgment:** High — the highest borrowed judgment of any IBM layer. IBM borrows retrieval intelligence entirely from open-source communities (Milvus, Elasticsearch, pgvector), embedding models from NVIDIA (NeMo Retriever) or open-source (sentence-transformers), and search acceleration from NVIDIA (cuVS). IBM provides no proprietary retrieval logic, no proprietary vector indexing, and no proprietary search intelligence.

This is not a criticism of the architecture — open-source retrieval works. It is a DAPM observation: the enterprise's retrieval pipeline at Layer 1B has no IBM authority in it. The judgment is borrowed entirely from open-source communities and NVIDIA. If Milvus changes its indexing heuristics, IBM inherits the change. If NVIDIA changes NeMo Retriever's embedding strategy, IBM inherits that too. IBM provides packaging, not judgment.

Compare to VAST (low — owns InsightEngine, DataBase, Catalog, vector search) or Dell (moderate — owns MetadataIQ, delegates search to Elastic, depends on NVIDIA for acceleration).

### ● Layer 1C: Data Movement & Pipelines

*Data lifecycle automation — ingestion, transformation, pipeline orchestration*  
**Status:** Confluent + Open-Source Pipeline

**IBM Confluent (Kafka + Flink + Tableflow)** [DAPM: Retained]  
IBM-defensible IP. Real-time data streaming platform. Kafka for event streaming, Flink for stream processing, Tableflow for zero-copy integration with watsonx.data Iceberg tables. $11B acquisition. Enables AI agents to reason over live event streams without ETL. No other infrastructure vendor owns a real-time streaming substrate.

**IBM DataStage (watsonx Edition)** [DAPM: Retained]  
IBM-defensible IP. Enterprise data integration engine with decades of maturity. Graphical and code-first pipeline building. Automated data cleansing, tokenization, formatting for LLM consumption. Comprehensive lineage tracking — trace which raw document fed into a specific fine-tuning or RAG dataset. Data sanitization (PII, hate speech, copyrighted content) reduces Layer 2C compliance burden.

**ML Pipeline Stack (Kubeflow + Ray + MLflow + Spark + Tekton)** [DAPM: Delegated]  
Kubernetes-baseline capability. Open-source ML lifecycle on OpenShift AI. Kubeflow for pipeline orchestration, Ray for distributed training, MLflow for experiment tracking, Spark for data processing, Tekton for CI/CD. All run identically on VMware Tanzu, EKS, or bare Kubernetes. IBM provides enterprise packaging, not proprietary capability.

**watsonx.data Query Federation** [DAPM: Retained]  
IBM-defensible IP. Zero-copy query federation to external data platforms: Confluent Tableflow, Databricks Unity Catalog, Snowflake Open Catalog, Salesforce Data Cloud. Presto and Spark engines query data where it resides without copying. The federation logic is IBM-specific integration.

**Gap Analysis:** Applying the Kubernetes-baseline test, Layer 1C splits cleanly into IBM-defensible IP and open-source commodity — and the defensible half is genuinely strong.

IBM-defensible IP (not replicable on Tanzu or bare Kubernetes):

(1) Confluent (Kafka + Flink + Tableflow): IBM-owned post-$11B acquisition. Real-time streaming as infrastructure, not batch ETL. Tableflow zero-copy integration with watsonx.data Iceberg tables is IBM-specific. Kafka itself is open-source but the governed integration with the IBM lakehouse is proprietary. This is the most significant data-layer acquisition from any vendor in this assessment — no other infrastructure vendor owns a real-time streaming substrate.

(2) DataStage (watsonx Edition): IBM proprietary enterprise data integration engine. Decades of maturity. Graphical and code-first pipeline building with automated data cleansing, tokenization, formatting for LLM consumption, and comprehensive lineage tracking. Enterprises can trace which raw document fed into a specific fine-tuning or RAG dataset. Compare to Dell's Dataloop (~$120M acquisition, less mature) or HPE's Airflow packaging (open-source, no proprietary lineage).

(3) watsonx.data query federation: Zero-copy federation to Confluent Tableflow, Databricks Unity Catalog, Snowflake Open Catalog, Salesforce Data Cloud. IBM-specific integration logic.

Kubernetes-baseline (replicable on any CNCF-compliant cluster):

• Kubeflow — CNCF, pipeline orchestration, runs on any Kubernetes
• Ray — open-source, distributed compute, runs anywhere
• MLflow — open-source, experiment tracking, runs anywhere
• Spark — open-source, data processing, runs anywhere
• Tekton — CNCF, CI/CD pipelines, runs on any Kubernetes

The 'Strong' classification is earned by the defensible half: Confluent + DataStage + watsonx.data federation. The open-source pipeline tools are commodity packaging — identical to HPE Ezmeral's approach, and replicable by any competent platform engineering team on any Kubernetes distribution.

The architectural gap: unlike VAST's DataEngine (where pipeline functions execute directly on storage with CRDs — compute moves to data), IBM's pipelines run on OpenShift as separate containerized workloads — data moves to compute. For large-scale AI training pipelines, this creates more data movement than VAST's architecture. For real-time inference pipelines consuming Confluent streams, the data velocity advantage compensates.

The resource overhead concern (correctly identified by Gemini's assessment): DataStage and Tekton are heavy enterprise platforms designed for complex corporate data architectures. For agile AI teams accustomed to Python scripts and LlamaIndex, IBM's data movement layer can feel over-engineered. This is a real practitioner concern — IBM's Layer 1C is enterprise-grade but not lightweight.

**Borrowed Judgment:** Low for defensible components. IBM now owns the streaming substrate (Confluent), the enterprise data integration engine (DataStage), and the lakehouse federation (watsonx.data). These are IBM IP with no external authority dependency.

Moderate for open-source components. Kubeflow, Ray, MLflow, Spark, and Tekton are community-governed. IBM packages and supports them but inherits community judgment on architecture, performance, and API design. This is the same pattern as HPE's Ezmeral — enterprise packaging of open-source pipelines.

NVIDIA provides GPU acceleration for Spark (RAPIDS) but the pipeline orchestration, streaming, data integration, and lifecycle are IBM-owned or community-governed. NVIDIA's authority at Layer 1C is limited to acceleration, not orchestration.

Compare to Dell: Dell owns Dataloop (Retained) but depends on Starburst, NVIDIA, and ISV partners for the broader pipeline. Four authority boundaries.

Compare to VAST: VAST owns everything at Layer 1C. One authority, total vendor dependency.

IBM's model is distinctive: own the streaming substrate and enterprise data integration (defensible IP), package the open-source pipeline tools (commodity), federate across external data platforms (defensible integration). The enterprise retains more substitutability than VAST offers (can swap Kubeflow for Airflow without touching Confluent) but less than pure open-source (Confluent streaming integration is IBM-specific).

### ● Layer 2A: Infrastructure Orchestration

*Lifecycle management, scheduling, multi-tenant isolation, capacity management*  
**Status:** OpenShift Strength

**Red Hat OpenShift (Container Platform)** [DAPM: Retained]  
Enterprise Kubernetes platform. Hybrid cloud consistency across on-prem, AWS (ROSA), Azure (ARO), GCP, IBM Cloud, edge. Lifecycle management, security (SELinux, FIPS), multi-tenant isolation. The universal substrate for IBM's AI stack.

**Red Hat OpenShift AI 3.4** [DAPM: Retained]  
MLOps + GenAIOps + AgentOps on OpenShift. Models-as-a-Service with token quotas, rate limiting, API key self-service, showback dashboards. AI gateway via Connectivity Link (Envoy/Kuadrant/Istio). Multi-accelerator model serving (NVIDIA, AMD, Intel Gaudi, IBM Spyre).

**IBM Concert Platform** [DAPM: Retained]  
Public preview (Think 2026). Agentic operations platform: Concert Observe (Instana), Concert Optimize (Turbonomic), Concert Protect (security/Secure Coder), Concert Operate (cross-domain incident response). Shared operational data layer across applications, infrastructure, networks, security. Graph-driven operations model.

**Red Hat Ansible Automation Platform** [DAPM: Retained]  
Infrastructure automation across hybrid environments. Ansible Lightspeed with IBM watsonx for AI-assisted automation content creation. Established enterprise automation authority — the bridge between AI platform operations and existing IT operations.

**Gap Analysis:** Layer 2A requires careful separation of Kubernetes-baseline capabilities from IBM-defensible IP.

Kubernetes-baseline (replicable on Tanzu, EKS, or bare K8s): Container orchestration, namespace isolation, multi-tenancy, RBAC, lifecycle management, GPU scheduling via NVIDIA GPU Operator, model serving via KServe, distributed compute via Ray, CI/CD via Tekton. These are CNCF-ecosystem capabilities that IBM packages with enterprise support but does not own. VMware Tanzu provides the same primitives through VCF 9.1. An enterprise could switch from OpenShift to Tanzu without losing these capabilities — the same way enterprises switch SAP BASIS support from IBM to Accenture without touching SAP.

IBM-defensible IP above the Kubernetes baseline:

• NVIDIA bracketing: IBM is the only vendor in this assessment that makes NVIDIA AI Enterprise optional at Layer 2A. OpenShift AI's Kueue integration provides Kubernetes-native multi-tenant GPU queue management, quota enforcement, and fair-share scheduling without Run:ai. Dell's Layer 2A is 'Gap — Ceded to NVIDIA Run:ai.' HPE has the same NVIDIA GPU scheduling dependency. VMware depends on NVIDIA GPU Operator. IBM's platform team can dictate exactly how GPUs are carved up, queued, and billed using native OpenShift primitives, rendering NVIDIA's commercial scheduling layer optional. The enterprise can still use Run:ai on OpenShift — but it doesn't have to. This is a structurally significant Layer 2A differentiator.

• Concert platform (Instana + Turbonomic + security modules): Cross-domain observability spanning applications, infrastructure, networks, and security with a graph-driven operations model. No CNCF equivalent. Datadog and Dynatrace compete at the product level but Concert's six-module integrated architecture (Observe, Operate, Optimize, Protect, Secure, Resilience) is IBM-specific.

• Ansible Automation Platform: Established enterprise automation authority with Ansible Lightspeed (AI-assisted automation). Red Hat-owned IP with no Kubernetes-native equivalent.

• OpenShift AI 3.4 Models-as-a-Service: Token quotas, rate limiting, self-service API keys, showback dashboards built as Kubernetes CRDs on Envoy/Kuadrant/Istio. The underlying components are open-source, but the composition and integration is IBM-specific packaging. An SI could replicate this on Tanzu with sufficient engineering — but IBM provides it out of the box.

• Hybrid consistency: Same OpenShift control plane across on-prem, AWS (ROSA), Azure (ARO), GCP, IBM Cloud, edge. No other assessed vendor provides the same AI platform management plane across all major clouds. This is genuine differentiation — but OpenShift-specific, not a capability the enterprise retains if they move to Tanzu.

The 'Strong' classification is justified by two structural differentiators that no other on-prem vendor matches: NVIDIA bracketing (making Run:ai optional through native Kueue scheduling) and hybrid consistency (same control plane everywhere). These are competitive advantages in the Kubernetes platform market. Concert and Ansible add IBM-specific observability and automation above the Kubernetes baseline. But the core orchestration primitives remain CNCF-baseline — maturity in Kubernetes packaging is a competitive advantage, not a structural moat.

**Borrowed Judgment:** Requires disaggregation:

For Kubernetes-baseline capabilities: the enterprise borrows Kubernetes community judgment (scheduling, networking, storage orchestration) and NVIDIA judgment (GPU Operator, Run:ai). This borrowed judgment is identical regardless of whether the enterprise runs OpenShift, Tanzu, or EKS. It is not IBM-specific.

For IBM-defensible IP: Low. Concert (Instana, Turbonomic), Ansible, and the OpenShift AI MaaS packaging are IBM-owned. The enterprise Cedes observability and automation authority to IBM when it adopts these — but can substitute with Datadog (observability) or Terraform (automation) without re-architecting the AI platform.

The structural comparison requires a new framing: Dell's 2A (OpenManage) manages Dell hardware only. HPE's 2A (GreenLake) manages HPE infrastructure. VAST's 2A (Polaris) manages VAST clusters. VMware's 2A (VCF) manages virtualized infrastructure. IBM's 2A (OpenShift) manages any hardware — but so does any Kubernetes distribution. The scope is broad; the defensibility is in the packaging maturity and hybrid consistency, not in the orchestration primitives themselves.

### ◑ Layer 2B: Application Runtime & Execution

*Model serving, agent execution, inference APIs, distributed inference*  
**Status:** Open-Source Runtime + NVIDIA

**Red Hat AI Inference (Model Serving)** [DAPM: Delegated]  
Kubernetes-baseline capability. vLLM-based inference serving with KServe orchestration. OpenAI-compatible APIs. Models-as-a-Service architecture with enterprise authentication, token management, and showback. Supports NVIDIA, AMD, Intel Gaudi, IBM Spyre accelerators. vLLM and KServe are open-source — run identically on Tanzu or bare Kubernetes. IBM provides packaging and integration, not proprietary runtime.

**OpenShell Integration (Agent Governance)** [DAPM: Delegated]  
IBM-shaped open-source. Red Hat co-engineering with NVIDIA on sandboxed agent runtime. Infrastructure-level policy enforcement for autonomous agents. Governs agent execution, tool access, and inference routing. Key Red Hat contribution to upstream open-source project. Feeds into Layer 2C vision.

**Confidential Containers + Agent Security** [DAPM: Retained]  
IBM-defensible IP. Technology Preview: NVIDIA Confidential Computing within OpenShift sandboxed containers. Hardware-enforced agent isolation — protects against runtime compromise even if another agent is breached. Zero-trust architecture: SELinux + FIPS + DOCA runtime protection. Most comprehensive agent security architecture in this assessment. Not replicable on vanilla Kubernetes or Tanzu without significant engineering.

**Agent Lifecycle Management (MLflow-based)** [DAPM: Delegated]  
Kubernetes-baseline capability. LLM call tracing, tool execution tracking, reasoning step auditability. MLflow is open-source — runs on any platform. IBM provides integration with OpenShift AI and the watsonx governance stack. The auditability is enterprise-critical; the tooling is commodity.

**Granite Model Family** [DAPM: Retained]  
IBM-defensible legal wrapper on open-source models. Granite 4.1 (3B, 8B, 30B dense models, Apache 2.0). ISO 42001 certified. Cryptographic model signing. Uncapped IP indemnity on watsonx.ai. Optimized for agentic workflows: tool calling, instruction following, function calling. Granite Guardian for safety guardrails. Models run anywhere (Hugging Face, Ollama, Dell Enterprise Hub, NVIDIA NIM). IP indemnity is IBM-specific — the only defensible element.

**Gap Analysis:** Applying the Kubernetes-baseline test at Layer 2B reveals the same pattern as Layer 1B: the execution runtime is entirely open-source commodity, and IBM's defensible value is the governance and security wrapper around it.

Kubernetes-baseline (replicable on Tanzu, EKS, or bare K8s):
• vLLM — open-source inference engine, runs on any Kubernetes with GPU Operator
• KServe — CNCF model serving orchestration, runs on any Kubernetes
• MLflow — open-source lifecycle management, runs anywhere
• Ray — open-source distributed compute, runs anywhere
• NVIDIA NIM — containerized model serving, runs on any Kubernetes with NVIDIA AI Enterprise

IBM-defensible IP above the baseline:
• Confidential containers + agent security: SELinux, FIPS, sandboxed containers with NVIDIA Confidential Computing (Technology Preview). Hardware-enforced agent isolation protecting against runtime compromise even if another agent is breached. Red Hat's security hardening is genuine IP that vanilla Kubernetes and Tanzu don't match out of the box. This is the most comprehensive agent security architecture in this assessment.
• OpenShell co-engineering: Red Hat contributing to upstream agent governance standards — infrastructure-level policy enforcement for autonomous agents. Not proprietary IP but IBM-shaped open-source that feeds into the 4+1 model's Layer 2C vision.
• Granite IP indemnity: The models are Apache 2.0 and run anywhere. The uncapped IP indemnity is IBM-specific legal protection available only through watsonx.ai. The model is portable; the legal wrapper is not.
• Granite Guardian: Safety guardrails, Apache 2.0. IBM-led but runs on any platform.

One observation Gemini makes correctly: IBM deliberately treats the model runtime as a portable commodity layer. By standardizing on vLLM + KServe, IBM eliminates the runtime fragmentation seen in Dell's stack (NemoClaw, OpenShell, NeMo Guardrails, Dynamo, NIMs — five NVIDIA components creating a tightly coupled runtime). IBM's runtime simplicity is the strategy: fewer components, fewer dependencies, more portability. The trade-off is that IBM cannot achieve the extreme custom-silicon optimization of Google's Pathways/TPU integration or AWS's Trainium-optimized stack.

The 4+1 model distinction: IBM's Layer 2B borrowed judgment is in execution (how models run — entirely from open-source and NVIDIA). IBM's Layer 2B authority is in governance (how model execution is constrained, audited, and secured — from Red Hat security hardening and confidential containers). This is the inverse of Dell's profile: Dell borrows governance at 2B, IBM borrows execution at 2B.

The vendor comparison at 2B:
• Dell: NVIDIA runtime + ISV blueprints (Cohere North, DataRobot, ClearML). Dell adds services, not runtime IP. Runtime is Ceded to NVIDIA.
• HPE: NVIDIA runtime + Kamiwaza agent coordination + CrewAI/ISV frameworks. Three sources, three authorities.
• VAST: AgentEngine provides a unified proprietary agent runtime. One authority. The strongest 2B defensibility in the assessment.
• IBM: Open-source runtime (vLLM/KServe) + NVIDIA acceleration + Red Hat security wrapper + IBM governance overlay (watsonx.governance). IBM's value is not the runtime itself but the governance and security wrapper around an open-source runtime. The runtime is commodity; the wrapper is defensible.

**Borrowed Judgment:** Requires disaggregation:

For execution runtime: High. vLLM, KServe, NVIDIA NIM, Triton are open-source or NVIDIA-controlled. IBM borrows all execution judgment from open-source communities and NVIDIA. This borrowed judgment is identical regardless of whether the runtime runs on OpenShift, Tanzu, or EKS.

For governance and security: Low. Confidential containers, SELinux/FIPS hardening, OpenShell co-engineering, agent lifecycle auditability, and the Granite IP indemnity are IBM/Red Hat IP or IBM-led open-source. The enterprise Cedes security architecture to Red Hat when adopting OpenShift's agent security stack — but Red Hat's security opinions are the product.

For model alignment: Variable. Granite models carry IBM's alignment choices (ISO 42001, rigorous data filtering, enterprise-focused tuning). If the enterprise swaps Granite for Llama or Mistral, it inherits those providers' alignment choices — but the execution fabric remains under the enterprise's authority regardless. The model is a Layer 3 choice; the runtime is a Layer 2B choice. IBM correctly separates them.

### ◑ Layer 2C: Agentic Infrastructure — The Reasoning Plane

*Policy-driven placement and resource coordination — the Autonomy Layer*  
**Status:** Most Explicit 2C Claim

**watsonx Orchestrate (Next-Gen Agentic Control Plane)** [DAPM: Ceded]  
Private preview (Think 2026). Multi-agent governance: manages agents from IBM native, LangFlow, LangGraph, and A2A protocol. Centralized identity/credential management, policy enforcement, audit logging. Agent catalog for discovery and lifecycle. AgentOps for real-time observability and cost tracking. Over 100 domain agents and 400+ prebuilt tools.

**IBM Bob (Multi-Model Orchestration)** [DAPM: Ceded]  
GA. Agentic developer assistant with multi-model routing: dynamically routes tasks to Claude, Mistral, Granite based on accuracy, latency, cost. Pass-through pricing. 80,000 internal IBM users, 45% average productivity gain. Demonstrates practical multi-variable placement decisions.

**IBM Sovereign Core (Runtime Sovereignty)** [DAPM: Retained]  
GA May 2026. Four sovereignty pillars: operational, data, technology, AI. AI sovereignty enforced at runtime — governing where inference happens, who controls models, how decisions are logged/traced/reviewed. Built on OpenShift + Red Hat AI. Mistral AI first certified model partner.

**watsonx.governance (Cross-Platform AI Assurance)** [DAPM: Retained]  
Governance Graph mapping AI assets through policies, risks, and regulatory requirements. Agentic monitoring and security capabilities. Cross-platform: governs IBM, OpenAI, AWS, Meta. Continuous compliance monitoring, not periodic audits. The governance query surface that a 2C control plane needs.

**Gap Analysis:** The Kubernetes-baseline test produces its most significant finding at Layer 2C: this is the only layer where IBM provides 100% defensible IP. There is no CNCF equivalent for cross-framework agent governance, no open-source multi-variable model routing, no community-driven runtime sovereignty enforcement, no Kubernetes-native cross-platform AI lifecycle assurance. Every component at Layer 2C is IBM proprietary. Nothing here runs on Tanzu without IBM licensing.

This finding validates IBM's entire strategic architecture. Layers 0 through 2B are progressively commodity — open-source packaging on delegated hardware. Layer 3 is consulting and models in a competitive services market. Layer 2C is the narrow band where IBM provides capabilities that cannot be replicated without IBM. The moat is here.

IBM is the only vendor in this assessment that explicitly names its agent orchestration layer a 'control plane.' watsonx Orchestrate's next generation (private preview, Think 2026) is positioned as an 'agentic control plane for scaling and governing your AI' — and the capabilities described map directly to what the 4+1 model defines as Layer 2C.

Applying the Intelligence 2C vs. Infrastructure 2C split established in the AWS assessment:

Intelligence 2C (productized and portable): watsonx.governance provides continuous model monitoring, bias detection, drift tracking, regulatory compliance enforcement, and the Governance Graph mapping AI assets through policies, risks, and regulatory requirements. watsonx Orchestrate provides cross-framework agent governance — managing agents from IBM native, LangFlow, LangGraph, and A2A protocol with centralized policy enforcement, identity/credential management, and audit logging. IBM Bob demonstrates practical multi-model routing: tasks dynamically routed to Claude, Mistral, or Granite based on accuracy, latency, and cost — a multi-variable placement decision, not single-variable optimization like NVIDIA Dynamo's KV-aware routing. Sovereign Core enforces sovereignty as a runtime requirement, governing where inference happens, who controls models, and how decisions are logged within sovereign boundaries.

IBM's Intelligence 2C is the strongest in this assessment for on-premises deployments. Four capabilities that no other on-prem vendor matches:
(1) Cross-framework agent governance (watsonx Orchestrate) — manages agents regardless of which framework built them. Dell has no equivalent. HPE delegates to Kamiwaza. VAST's AgentEngine governs VAST-native agents only.
(2) Cross-platform AI assurance (watsonx.governance) — governs models running on IBM, OpenAI, AWS, or Meta. No other governance solution spans vendor boundaries.
(3) Multi-variable model routing (IBM Bob) — 80,000 internal users, demonstrated accuracy/latency/cost optimization. Production evidence at scale.
(4) Runtime sovereignty (Sovereign Core) — sovereignty enforced at infrastructure runtime, not as a policy checkbox. No equivalent from any assessed vendor.

Infrastructure 2C (absent/manual): watsonx Orchestrate governs agent behavior but does not autonomously calculate: 'Based on real-time token cost, data residency tags in watsonx.data, and current GPU cluster queue times, route this inference to on-prem PowerEdge versus burst to Azure.' That infrastructure placement coordination remains a manual configuration task for the platform architect. No productized engine queries Layer 1A governance metadata to make multi-variable infrastructure placement decisions in real time.

This is the same split AWS exhibits: Intelligence 2C is productized (AgentCore Policy, Guardrails), Infrastructure 2C is implicit inside managed services. IBM's Intelligence 2C is more portable than AWS's (runs on-prem, multi-cloud). IBM's Infrastructure 2C is equally absent.

Six-vendor Layer 2C comparison:
• Dell: Absent. No productized control plane.
• HPE: Retained (IT infrastructure ops via GreenLake Intelligence) + Delegated (AI workloads via Kamiwaza).
• VAST: Retained/Emerging (PolicyEngine + Polaris — middle-out from data layer, GA end 2026).
• AWS: Intelligence 2C Delegated (AgentCore/Guardrails) + Infrastructure 2C Ceded/Implicit within managed services.
• Google: Full 2C — Agent Platform with Inference Gateway + DWS. Most production-proven. Entirely Ceded to Google.
• IBM: Intelligence 2C Retained/Ceded (watsonx.governance + Orchestrate — highly portable, productized, multi-cloud) + Infrastructure 2C Absent/Manual.

The production maturity gap: watsonx Orchestrate next-gen is in private preview. The capabilities are described, the architecture is sound, Bob provides production evidence of multi-model routing at scale (80,000 users). But the full agentic control plane is not GA. Compare to Google's Agent Platform (GA, production-deployed) and AWS's Bedrock AgentCore (GA). IBM's 2C is the most explicitly named, the most framework-agnostic, and the least production-proven as a complete system.

**Borrowed Judgment:** Low — the lowest borrowed judgment of any IBM layer, because every component is IBM proprietary IP. watsonx Orchestrate, watsonx.governance, Sovereign Core, and Bob are all IBM-owned. No open-source dependency, no NVIDIA dependency, no partner dependency at this layer.

The framework-agnostic approach means IBM borrows less agent-level judgment from any single framework vendor — but it also means IBM's orchestration authority depends on integration quality with frameworks it doesn't control (LangFlow, LangGraph, A2A). If LangGraph changes its execution model, IBM must update the integration. This is a different kind of dependency than NVIDIA runtime dependency — it's integration maintenance, not architectural dependency.

The DAPM classification requires the Retained/Ceded distinction established in the series:
• watsonx Orchestrate: Ceded to IBM. The enterprise consumes IBM's control plane — configures policies within it, but cannot replace it without re-architecture. Portable across clouds but not substitutable.
• watsonx.governance: Retained by the enterprise. The enterprise defines its own governance policies, ethical thresholds, and compliance constraints. IBM provides the framework; the enterprise provides the judgment. The closest to genuinely Retained authority in IBM's stack.
• Sovereign Core: Retained by the enterprise. The enterprise defines sovereignty boundaries; IBM enforces them at runtime.
• Bob: Ceded to IBM. Multi-model routing logic is IBM's — the enterprise configures preferences but IBM's software makes the placement decisions.

Compare to Google: Agent Platform provides 2C as a deeply integrated platform capability. More production-proven but less framework-agnostic. Entirely Ceded to Google — no on-prem option.

Compare to HPE/Kamiwaza: Kamiwaza provides similar agent coordination but as a partner (Delegated). IBM provides it as owned IP.

Compare to VAST: PolicyEngine provides data-layer governance with 2C ambitions. VAST builds 2C from data up; IBM builds 2C from platform out. Different architectural vectors toward the same Layer 2C function.

### ◇ Layer 3 (+1): AI Application Layer — The Value Plane

*AI-powered business capabilities — business logic, workflow automation*  
**Status:** Consulting-Led Ecosystem

**IBM Consulting (Competitive Services Market)** [DAPM: Retained]  
~160,000 consultants with AI practice. Vertical industry solutions: banking (Banco Bradesco on ARO), healthcare, government, manufacturing. Competitive advantage in implementation services — but substitutable. Enterprise retains authority to select any SI (Deloitte, Accenture, Wipro, boutique firms) for platform implementation without architectural impact. The SAP BASIS pattern: platform IP is the moat, implementation services are a market.

**Granite Model Ecosystem** [DAPM: Retained]  
Granite 4.1 (3B/8B/30B, Apache 2.0), Granite Guardian (safety), Granite Code, Granite Time Series. Available on watsonx.ai, Hugging Face, Dell Enterprise Hub, NVIDIA NIM, Docker Hub, Ollama, LM Studio. Multi-platform model family with strongest governance posture: ISO 42001, cryptographic signing, uncapped IP indemnity.

**Multi-Model / Multi-Framework Support** [DAPM: Delegated]  
watsonx.ai supports Granite, Llama, Mistral, GPT-OSS, Nemotron. OpenShift AI serves any model via vLLM/KServe. watsonx Orchestrate manages agents from IBM native, LangFlow, LangGraph, A2A. The platform is model-agnostic and framework-agnostic by design.

**Red Hat Partner Ecosystem** [DAPM: Delegated]  
OpenShift ISV ecosystem across industries. Microsoft (Platform Modernization Partner of the Year 2026), AWS (ROSA + Kiro integration), Salesforce (Agentforce reference architecture). Multi-cloud deployment: build on OpenShift, deploy across AWS/Azure/GCP/on-prem.

**IBM Z/Power Transactional AI (Application-Layer Advantage)** [DAPM: Retained]  
IBM Z16 Telum on-chip AI accelerator for real-time transactional inference co-located with enterprise ledgers — banking fraud detection, insurance claims, government transactions. This is a Layer 3 application advantage (AI adjacent to business data on proprietary hardware) not a Layer 0 infrastructure capability. Analogous to SAP HANA on dedicated hardware: the value is application adjacency, not compute fabric. watsonx Code Assistant for Z (IBM Bob Premium for Z) provides AI-assisted COBOL-to-Java modernization — 10x productivity gains in early users.

**Gap Analysis:** IBM's Layer 3 requires the same defensible-IP-vs-substitutable-services analysis applied throughout this assessment.

IBM Consulting (~160,000 consultants) is a competitive advantage in a substitutable services market, not a structural platform dependency. Enterprises switch AI platform implementation partners the same way they switch SAP BASIS support: IBM to Accenture, Accenture to Deloitte, Deloitte to Wipro. The platform doesn't notice. The open-source components (OpenShift, vLLM, KServe, Kubeflow) run identically regardless of which SI assembled them. IBM Consulting's advantage is scale and experience, not lock-in.

This is structurally different from every other vendor's services model:
• Dell's Accelerator Services are additive — the NVIDIA runtime works without Dell's humans.
• HPE's Kamiwaza partnership is structural — remove Kamiwaza and HPE loses Layer 2C orchestration.
• VAST requires minimal consulting because the platform makes architectural decisions for you.
• IBM's consulting is the primary go-to-market motion for a platform built from open-source components. The components are free. The assembly expertise is what IBM sells.

But any competent SI can provide the assembly expertise. IBM Consulting competes for the engagement; it doesn't own the engagement by virtue of platform architecture.

The Granite model family occupies a unique position: open-source (Apache 2.0), enterprise-grade, with the strongest governance posture of any model family (ISO 42001, cryptographic signing, uncapped IP indemnity). Granite is not competing with Claude or GPT-4 on raw capability — it's competing on trustworthiness, efficiency, and enterprise deployability. Critically, Granite runs on any platform — Dell Enterprise Hub, NVIDIA NIM, Hugging Face, Ollama. The model is portable; the IP indemnity is IBM-specific.

IBM Z/Power transactional AI (Telum on-chip inference for banking, insurance, government) is a genuine Layer 3 application advantage. AI inference co-located with enterprise ledgers is not replicable on Dell or HPE hardware because the value is in the application adjacency to mainframe data, not in the compute architecture. watsonx Code Assistant for Z (Bob Premium for Z) with 10x productivity for COBOL modernization reinforces this — it's an AI application that only makes sense on IBM Z hardware.

The ISV ecosystem comparison:
• Dell's ecosystem is broad and horizontal: 5,000+ customers, OpenAI, Palantir, Google, ServiceNow, SpaceXAI.
• HPE's ecosystem is curated and vertical: 26+ ISVs through Unleash AI.
• IBM's ecosystem is consulting-driven and multi-cloud: IBM Consulting partnerships with SAP, Salesforce, Adobe, ServiceNow, plus the OpenShift ISV ecosystem deployable across all major clouds.
• The multi-cloud deployment model (build on OpenShift, deploy across AWS/Azure/GCP/on-prem) is genuine differentiation at Layer 3 — ISVs building on OpenShift get portability that Dell and HPE can't match.

**Borrowed Judgment:** Distributed across ISV partners and model providers, which is architecturally correct at Layer 3.

The consulting question is critical for DAPM: IBM Consulting is NOT a borrowed-judgment dependency. The enterprise retains full authority to select any SI for platform implementation, customization, and ongoing support. Switching SIs does not change the platform architecture, does not require re-engineering, and does not break running workloads. This is the SAP BASIS pattern: the platform IP (watsonx.governance, Orchestrate) is the structural dependency; the implementation services are a competitive market.

The structural comparison:
• Dell's ecosystem is load-bearing: ISV partners provide infrastructure-level functions. Remove Cohere North and Dell loses agent orchestration.
• HPE's ecosystem is curated: partners provide domain applications. Remove Deloitte Zora AI and HPE loses a finance use case, not a platform function.
• IBM's consulting is competitive: remove IBM Consulting and the enterprise hires Accenture. The platform remains intact. The adoption motion may slow but the architecture doesn't change.
• VAST's ecosystem is additive: platform is self-sufficient. Partners add vertical use cases.

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