Lenovo has one of the most credible on-prem AI infrastructure foundations in the market. Among the on-prem anchors on this instrument, each builds from what it owns: Dell from servers and storage, HPE from sovereign compute and three owned fabrics, Cisco from network silicon and security. Lenovo's anchor is manufacturing scale and thermal engineering — server breadth, Neptune sixth-generation liquid cooling, eight of the top ten public clouds as customers — and it is the only one of the four that owns neither a network fabric nor, until the April 2026 Infinidat close, any opinion-bearing storage software. Above the rack, capability arrives predominantly as other vendors' IP validated and SKU'd on Lenovo paper: ONTAP, Cloudian, WEKA, Red Hat, Nutanix, NVIDIA.
The row's signature is what the validated-solutions model doesn't do: capture opinions. The enterprise's storage, retrieval, and runtime opinions lift off Lenovo paper to wherever the partner software runs — the most Delegated-heavy authority profile among the OEM rows. One contract with Lenovo is a procurement fact, not an authority fact.
Where Lenovo does capture, three surfaces matter, two of them new in 2026: InfiniBox and InfiniGuard (the Infinidat close gave Lenovo its first owned, opinion-bearing storage software), XClarity One fleet management, and — the inversion worth naming — the AI Library's first-party agents at Layer 3. Lenovo's strongest software capture surface is its applications, not its infrastructure software. The buyer who feels safely un-captured at the infrastructure layers is accumulating workflow opinions in Lenovo-built agents at the top.
Everything GPU-aware above the rack is NVIDIA's judgment — Run:ai and NVIDIA AI Enterprise ride Lenovo paper as five-year subscription SKUs, which changes the invoice, not the authority. Same boundary as Dell and HPE.
Two layers are unclaimed: no pipeline layer (1C) and no reasoning plane (2C) — no owned product, no packaged open-source alternative, and, unlike HPE's Kamiwaza designation or Dell's briefing-confirmed ecosystem strategy, no designated partner and no stated position. Whether those gaps are strategy or omission is this row's open briefing question. The buyer's trade: the broadest menu and the lowest OEM lock-in above the rack, in exchange for owning more of the assembly — and both missing planes — themselves.
Layer-by-layer status: Layer 0 (Lenovo Strength), Layer 1A (Owned High-End + Partner Portfolio), Layer 1B (Validated Retrieval — Partner Stack), Layer 1C (Enterprise Responsibility), Layer 2A (Fleet Management + Consumption Orchestration), Layer 2B (Validated Runtimes + Services), Layer 2C (Enterprise Responsibility), Layer 3 (+1) (First-Party Agents + ISV Ecosystem).
Assessment framework: 4+1 Layer AI Infrastructure Model. Scoring model: Decision Authority Placement Model (DAPM) — Retained, Delegated, or Ceded. Published by The CTO Advisor LLC. Author: Keith Townsend. Date assessed: July 11, 2026. Version: v1.0 - Initial Assessment.
Raw compute, networking, and acceleration fabric
Deskside to rack-scale on commodity x86/NVIDIA substrate — workloads move to Dell or HPE equivalents without rebuilding. 8x lower cost-per-token vs. cloud IaaS and sub-six-month ROI are Lenovo's claims for the inference platforms.
Lenovo-owned liquid-cooling IP; ~40-50% energy reduction claims; supports 100% liquid-cooled high-density Blackwell deployments. Physical plant accumulates no portable opinions — no lock-in surface.
Turnkey rack-scale for AI cloud providers: pre-integrated Lenovo infrastructure, NVIDIA accelerated computing (B300, GB300 NVL72), Lenovo manufacturing, and Hybrid AI Factory lifecycle services. Integrated-system rule: the deployment's integration opinions cannot be lifted to another vendor as built.
The factory's deployed fabric, sold and integrated by Lenovo as NVIDIA-branded product. Fabric opinions are embedded in the Spectrum-X stack with no abstraction layer that would make them portable to alternative switching — same customer-seat result as Dell's PowerSwitch.
~1 petaflop personal AI, models to 200B parameters. Commodity deskside substrate, substitutable across OEMs.
Blackwell and Blackwell Ultra (B300, GB300 NVL72) now; Vera Rubin on the roadmap. The compute engines Lenovo builds around.
Intra-node high-bandwidth interconnect defining memory and compute topology.
Consumed as NVIDIA-branded product — Lenovo holds no mechanical or brand authority over its fabric, a thinner position than Dell's branded PowerSwitch.
Lenovo's Layer 0 credibility is physical: ThinkSystem server breadth from deskside to NVL72-class racks, Neptune sixth-generation direct-water cooling (genuine Lenovo IP with a decade of heritage and ~40-50% energy-reduction claims), and manufacturing scale that powers eight of the top ten public clouds. The AI Cloud Gigafactory packages that manufacturing muscle for AI cloud providers — pre-integrated infrastructure, Lenovo manufacturing, and full-lifecycle Hybrid AI Factory services. What Lenovo does not own is networking. Dell at least brands NVIDIA silicon as PowerSwitch; HPE owns three fabrics. Lenovo resells NVIDIA Spectrum-X switches as NVIDIA-branded product, with a Cisco 800GbE Silicon One option in the Hybrid AI Factory's second phase — the one vendor whose networking aisle stocks two other vendors' captive fabrics. Either way the customer's fabric opinions are ceded to someone else's stack.
From the buyer's seat the fabric ratings are unaffected by whose logo is on the switch: fabric opinions are captive to the Spectrum-X (or Cisco Silicon One) stack regardless of whether the OEM brands, integrates, or merely resells it. What the resale posture does change is Lenovo's own leverage — Lenovo holds less mechanical authority over its networking story than Dell holds over PowerSwitch, and none of HPE's owned-fabric depth. Silicon roadmap authority is NVIDIA's throughout.
Watch-list (checked July 11, 2026, not scored): Vera Rubin NVL72 systems on Lenovo paper — NVIDIA states partner availability H2 2026; the AI Cloud Gigafactory names future Vera Rubin support. Scores when Lenovo documentation confirms GA. Confidence flag: GB300-class ThinkSystem GA is scored from CES/GTC 2026 launch language and Gigafactory support claims (B300/GB300), not from a per-model Lenovo Press product guide — doc inference, not confirmed fact. Fact question: is the Cisco Silicon One fabric option orderable in the Hybrid AI Factory today, or second-phase roadmap? Scored conservatively as menu context, not a component, pending confirmation.
Durable, governed data foundation — the Governance Catalog that Layer 2C queries
High-end enterprise storage, owned Lenovo IP as of April 9, 2026. InfuzeOS opinions — Neural Cache behavior, provisioning, replication topologies — are captive to the platform, the same litmus result as Dell PowerScale and HPE Alletra.
Backup appliance with built-in cyber resilience. Recovery policies and immutability configurations do not lift to another vendor's platform — matches Dell's built-in cyber-resilience Ceded.
Unified and capacity-flash arrays running NetApp ONTAP. The enterprise's ONTAP opinions (SVMs, SnapMirror policies, tiering) lift off Lenovo paper to NetApp AFF, FSx for ONTAP, ANF, or CVO — the enterprise can leave Lenovo without rebuilding. The capture is to the NetApp ecosystem, scored Ceded on NetApp's own row: the ecosystem owner cedes, the OEM channel delegates (Dell/Elastic precedent).
E-Series-based SAN arrays; same structure — NetApp IP on Lenovo paper, opinions portable within the SANtricity ecosystem.
S3-compatible object storage sold under Lenovo part numbers (7S0R-series license and support bundles). S3 multi-vendor standard keeps object opinions portable; the March 2026 Lenovo Validated Design adds GPUDirect/RDMA paths for AI workloads.
WEKA under a global Lenovo reseller agreement (2023, 160+ markets), plus certified designs with DDN and VAST. Substitutable partners on Lenovo paper — opinions move with the partner, not Lenovo.
GPU-direct data paths in the Cloudian and partner reference architectures (20GB/s per node claimed). The only NVIDIA surface at this layer — the near-empty column is itself a finding: Lenovo's storage acceleration story arrives through partner reference architectures, not first-party engineering.
Lenovo's 1A is two authority regimes in one portfolio. The high-end tier is now first-party: the Infinidat acquisition closed April 9, 2026, giving Lenovo InfiniBox G4 (hybrid), InfiniBox SSA G4 (all-flash), and InfiniGuard G4 (cyber-resilient backup) — its first owned, opinion-bearing storage software (InfuzeOS, Neural Cache, InfiniSafe), operating as a business unit in the Infrastructure Solutions Group. The mainstream and AI-data tiers remain partner IP on Lenovo paper: ONTAP-based DM/DG arrays and SANtricity-based DE arrays from the NetApp partnership, Cloudian HyperStore under Lenovo part numbers, WEKA as ThinkSystem SDS Ready Nodes under a global reseller agreement. What is missing at every tier is a governance catalog — no MetadataIQ equivalent, no Data Fabric/Polaris equivalent, no metadata layer a Layer 2C could query. The governed-data-foundation function this layer is named for is partner-provided or absent. Calibration: below Dell's strong (owned platforms plus governance catalog), at HPE's moderate on platform ownership but below it on governance.
Moderate — split by tier. Buy InfiniBox and the enterprise cedes storage opinions to Lenovo (low borrowed judgment; Lenovo owns the IP). Buy DM/DG, Cloudian, or WEKA and the data-management opinions are a partner's, delegated through Lenovo paper — the buyer's authority position depends on which line item they pick, which is itself a finding. Nothing at this layer inherits NVIDIA judgment beyond partner-RA acceleration.
InfiniBox components added in grading review — the April 2026 Infinidat close was initially missed and caught by human review; it is Lenovo's Dataloop moment, the first owned software asset in the data layer. Fact question: has a customer migrated a Lenovo DM estate to NetApp arrays without a rebuild? The Delegated call rests on shared-ONTAP portability (SnapMirror interop, config portability); support and licensing boundaries could complicate it in practice. Confidence flag: DE series currency scored from inference. Fact question for a briefing: is there any Lenovo-owned data-governance or metadata product not visible in documentation?
Low-latency retrieval for RAG — vector/hybrid search, context windows
Validated retrieval pipelines — NeMo Retriever embedding, open-source vector store, LangChain-class chaining — deployed on the documented Hybrid AI Software Platform (Kubernetes/OpenShift + NIM). Indices and pipelines lift to any deployment of the same open stack.
Object-native data services for AI pipelines over GPUDirect/RDMA, per the March 2026 LVD. Partner data services behind the S3 standard — opinions move with Cloudian, not Lenovo.
Embedding and reranking intelligence for the validated RAG pipelines. The retrieval judgment is NVIDIA's end to end — this is the load-bearing column at this layer.
Pipeline patterns deployed through the AI Library on the documented Hybrid AI Software Platform stack. Identical blueprints ship on Dell AI Factory and HPE Private Cloud AI — non-differentiating.
Layer 1B is where the HPE row's observation lands on its named example: the NVIDIA RAG reference stack is one 'any NVIDIA partner (Dell, Lenovo, Supermicro) could deploy identically.' Lenovo owns no retrieval intelligence — no vector database, no embedding engine, no search partnership of Dell's Elastic kind, no owned namespace of HPE's Data Fabric kind. What Lenovo provides is a working retrieval capability in one procurement: AI Library validated RAG use cases on the documented Kubernetes/NIM platform, and the Cloudian AI Data Platform's object-native data services in the March 2026 LVD. This is the weakest moderate among the OEM rows — real deployable capability on Lenovo paper keeps it above gap; zero owned retrieval IP and the all-Delegated component mix carry the ownership finding.
High — structurally like HPE's 1B (the highest borrowed judgment in that row) but without even an owned storage substrate underneath it. Embedding intelligence is NVIDIA's, vector storage is open-source, data services are Cloudian's. The mitigation is the same as everywhere on this row: the opinions lift, so the borrowed judgment is at least not captive judgment.
One-contract procurement confirmed by SKU evidence (Cloudian part numbers, WEKA reseller agreement) — a procurement fact, not an authority fact. The AI Library appears at 1B, 2B, and Layer 3 by design; each cell scores a distinct facet (retrieval infrastructure here; deployment/runtime path at 2B; business capability at Layer 3). Confidence flag: the specific vector store in AI Library RAG deployments is inferred from the NVIDIA reference pattern (Milvus); Lenovo Press deployment guides would confirm. No retrieval-quality observability (recall@k, latency percentiles) that a Layer 2C could consume — same universal finding as the Dell row.
Move/transform data — ETL/ELT, lineage, cost-aware movement, KV cache tiering
Pre-built pipeline patterns arriving through the AI Library — templates, not pipeline infrastructure. The thin column is the finding.
The 4+1 model defines Layer 1C as a required function — ETL/ELT, transformation, lineage, cost-aware orchestrated movement. Lenovo does not provide it. There is no owned pipeline product (no Dataloop equivalent), no packaged open-source pipeline stack (no Ezmeral equivalent), and no SKU'd marquee pipeline partner. What Lenovo's portfolio does move is data at the storage layer: ONTAP SnapMirror and FlexCache on DM/DG paper, InfiniBox replication, WEKA tiering, Cloudian AIDP ingest — all storage-platform features scored where the platforms are scored, at 1A. Storage replication is not ETL, and use-case-embedded data preparation inside AI Library agents is not pipeline infrastructure. Calibration: Dell's moderate rests on owned Dataloop orchestration; HPE's moderate rests on Data Fabric policy movement plus the Ezmeral packaging of Airflow/Kubeflow/Spark. Crediting Lenovo's nothing as moderate would make the score mean different things across rows. The enterprise brings its own pipeline tooling and owns the function.
There is no judgment to borrow — the enterprise retains full responsibility for pipeline logic on Lenovo infrastructure. Like the reasoning-plane gap, this responsibility is mostly implicit: it becomes visible when production data volumes expose it.
Sub-threshold signals, named in prose per the gap-cell rule: storage-native movement (SnapMirror/FlexCache, InfiniBox replication, WEKA tiering, Cloudian AIDP ingest) scored at 1A; NVIDIA blueprint pipeline templates via the AI Library; Veeam Kasten partnership (GTC 2026) for Kubernetes data protection. Fact questions for a briefing: is there any Lenovo-SKU'd pipeline or orchestration product not visible in documentation, and does the AI Library ship standalone data-prep/pipeline use cases (as opposed to prep embedded inside application agents)? Either fact would promote the cell.
GPU scheduling, quotas, RBAC, fair-share scheduling, utilization optimization
Unified management platform — fleet lifecycle, zero-trust management, monitoring, automation; hybrid SaaS or on-prem local VM. Fleet templates, policies, and firmware baselines are captive to Lenovo's management plane — the OpenManage precedent.
Lenovo-operated consumption model: metered NVIDIA GPU resources, workload scheduling and fair-share across tenant organizations. The scheduling substrate is Slurm/Kubernetes — genuine multi-vendor standards, so job definitions and manifests port to any Slurm/K8s environment (managed-service-behind-a-standard-interface rule). The captive surfaces (LiCO portal templates, TruScale metering) are thin convenience layers, not a proprietary placement engine — which is what separates this from Run:ai's Ceded.
GPU scheduling, quotas, fair-share — the Layer 2A function itself. Rides on Lenovo paper as a five-year subscription SKU (7S020050WW), which changes the invoice, not the authority: scheduling judgment is NVIDIA's regardless of whose paper the license rides on.
AI factory at-scale cluster management for the NVL-class deployments.
The documented Hybrid AI Software Platform's provisioning and orchestration substrate is NVIDIA's operator stack end to end.
Lenovo clears Dell's 2A bar and stays well under HPE's. The documented, orderable baseline: XClarity One (the go-forward unified management platform — fleet lifecycle, zero-trust management, hybrid SaaS or on-prem), TruScale GPUaaS (metered GPU consumption with workload scheduling and fair-share across tenant organizations via LiCO), and Run:ai/NVAIE riding Lenovo paper. TruScale GPUaaS is genuine workload-aware orchestration that Dell's rack-level-management cell explicitly lacks; nothing here approaches HPE's GreenLake Intelligence agentic mesh. The same OEM boundary applies throughout: Lenovo manages the fleet and the consumption model; NVIDIA manages everything GPU-aware inside the cluster.
High for GPU-aware orchestration — NVIDIA's judgment inside the cluster, Lenovo's around it, the same boundary as Dell and HPE. The distinctly Lenovo wrinkle: Lenovo has first-party scheduling judgment (LiCO), but its standalone SKUs are withdrawn, so the enterprise can now only consume that judgment by delegating operations to Lenovo through TruScale — an owned scheduler receding into a managed-service ingredient.
Watch-list (announced January 6, 2026; checked July 11, 2026, not scored): xIQ Hybrid Cloud Platform (AIOps + FinOps + DevOps across hybrid/multi-cloud) — production customers exist (DMEGC, possibly on the China-side xIQ Cloud predecessor) but no product documentation or part numbers confirm orderability; scores at doc-confirmed GA. Watch-list (June 2026, not scored): NVIDIA NemoClaw skills for AIOps — pre-GA, consistent with NemoClaw's alpha treatment on the Dell and NVIDIA rows. Fact questions: LiCO's status (standalone product guide and K8s part numbers withdrawn, yet lenovo.com still markets it and TruScale documents it as the orchestration engine); who operates TruScale GPUaaS day-2, and can a customer self-operate LiCO under a TruScale contract?
Model serving, agent execution, inference APIs, distributed inference
Production-ready agents deployed onto the documented open substrate — Kubernetes/OpenShift with NIM microservices. The runtime path is standard and swappable; content is curated catalog, matching Dell's marketplace Delegated.
Human-delivered strategy, deployment, and operation — proof-of-concept to production in as little as three months. Services, not software: expertise transfers to the customer, no captive opinion layer. Dell Accelerator Services precedent.
Red Hat AI Enterprise on Xeon 6 (documented in the Hybrid AI 221 platform guide) — ~2x concurrent request claims for CPU inference. The Red Hat substrate is the instrument's portability benchmark: OpenShift AI/vLLM opinions lift to any OpenShift deployment.
Partner inference runtime on Lenovo paper. Nutanix runs identically on Dell, HPE, or self-built infrastructure — the OEM-channel rule: opinions move with the partner ecosystem, not with Lenovo.
The model-serving runtime the primary path executes on, pre-validated on the Hybrid AI Platform configs and SKU'd on Lenovo paper (7S02001HWW). Inherited judgment, same as the Dell and HPE rows.
Distributed inference with KV-aware routing on the NVL-class racks — single-variable cache-locality optimization, not placement policy.
Agent runtimes named in Lenovo's GTC 2026 materials. Alpha — not GA, watch-listed, consistent with their treatment on the Dell and NVIDIA rows.
Lenovo's 2B menu is broader than either peer's primary SKU — four runtime paths ship today. The NVIDIA path (AI Enterprise + NIMs on validated Hybrid AI Platform inference configs, RTX PRO 6000/4500 Blackwell). A CPU-only inference platform with Red Hat AI Enterprise on Xeon 6 (June 2026) — a non-NVIDIA lane Dell's AI Factory doesn't lead with. Nutanix Enterprise AI on ThinkAgile HX650a. And Lenovo's own agentic lane: the AI Library's production-ready agents (one-click deployment of autonomous and long-running agents, one-week-to-production claims, independently validated results). Lenovo owns no runtime software on any path — the AI Library's agents deploy onto the documented Kubernetes/NIM stack, and 'Lenovo Agentic AI' is a lifecycle program (services + library + platforms), not a discrete runtime product. Path diversity is the differentiator; ownership is not.
High on the primary path — model execution, serving optimization, and guardrail defaults are NVIDIA's, inherited through the dependency column. Genuinely lower than Dell's overall: the Red Hat and Nutanix lanes are real substitutable alternatives on Lenovo paper, and services expertise (AI Discover, AI Fast Start) transfers to the customer.
Watch-list (announced January 6, 2026; checked July 11, 2026, not scored): xIQ Agent Platform — no-code agent creation and deployment with built-in governance. No product documentation, part numbers, or non-China customers confirm orderability; scores at doc-confirmed GA. At GA the no-code capture question becomes live: agents authored in a proprietary no-code builder are opinions with nothing to export. Watch-list: 'limited-access co-development programs' (June 2026) are pre-GA by definition. The Knowledge Super Agent's runtime substrate is the documented platform stack (K8s pods on NIM/NVAIE per lp2311) — doc-supported inference. The AI Library facet scored here is the deployment/runtime path; its business capability is scored at Layer 3.
Policy-driven placement and resource coordination — the Autonomy Layer
Multi-agent workflow scaffolding. Does not make placement decisions.
Performance-aware routing (single variable). Not multi-variable policy optimization.
Runtime security sandboxing — Layer 2B constraint enforcement, not 2C placement reasoning. Alpha — not GA.
The 4+1 model defines Layer 2C as a required function — policy-driven decisions about where compute runs relative to data, which model serves which request, and how cost, compliance, and latency are arbitrated in real time. Lenovo does not provide this function, and applying the 'routing is not reasoning' test disposes of every candidate: TruScale GPUaaS schedules (a 2A function); Dynamo routes on cache locality (single variable); AI-Q is workflow scaffolding; the AI Library's governance is human-in-the-loop services configured around individual agents — governance-as-a-service, not a policy engine. Unlike HPE, Lenovo has designated no 2C partner: there is no Kamiwaza-equivalent in the Hybrid AI Advantage ecosystem. And unlike Dell — whose gap is briefing-confirmed deliberate ecosystem strategy — Lenovo has no stated position on the reasoning plane at all, so the gap reads as an omission rather than a decision. The enterprise must build custom 2C logic, bring a partner, or operate without it; most will choose the third and discover the gap when production agentic workloads expose it.
There is no judgment to borrow — the enterprise retains full responsibility for this function, mostly without recognizing Layer 2C as a distinct function it needs to provide.
The one first-party claimant — the xIQ Agent Platform's 'built-in governance' — is watch-listed with its platform (announced January 6, 2026, no product documentation as of July 11, 2026), and even at GA it would be Intelligence-2C (which agent may act, under what policy), not Infrastructure-2C placement. The FinOps placement language in the watch-listed xIQ Hybrid Cloud Platform is ops management, not request-time inference placement. The live-placement gap is universal across the OEM rows — noted as an instrument-wide finding, not a Lenovo-specific defect. Briefing question: does Lenovo see the reasoning plane as ecosystem territory, xIQ roadmap territory, or not at all? The answer moves the summary's read of the vendor, not the cell.
AI-powered business capabilities — business logic, workflow automation
Lenovo-built, production-validated agents for enterprise workflows: knowledge management (30% time reduction, independently validated), predictive maintenance, quality inspection, customer engagement. First-party application IP — workflow opinions accumulate in Lenovo's agent builds and do not lift to a competing framework. Owned-IP rule, same logic as InfiniBox at 1A.
50+ ISVs, 165+ validated solutions across vision AI, GenAI, and vertical use cases. Substitutable partners on Lenovo paper — matches Dell's AI Ecosystem Program and HPE's Unleash AI.
Documented Lenovo Validated Design (lp2180) for multimodal agentic AI solutions. Partner IP, substitutable.
The execution substrate under the AI Library agents. Identical blueprints are available on every NVIDIA partner — the differentiation is the Lenovo-built agent layer above them, not the substrate.
Two lanes, and that is the story of this cell. Lane one is the standard OEM play: the AI Innovators ecosystem (50+ ISVs, 165+ validated solutions across vision AI, GenAI, and verticals) plus documented validated designs like the Centific multimodal agentic LVD. Lane two is what Dell and HPE do not have: first-party application content. The AI Library's agents — the Knowledge Super Agent above all — are Lenovo-built business capabilities with independently validated production outcomes (30% reduction in knowledge-task time, up to 120 hours per employee annually), deployable in one to two weeks across manufacturing, retail, and healthcare workflows. That first-party lane is why this cell breaks from the peer rows' partner status: the methodology reserves partner for a layer addressed entirely through an ISV ecosystem, and Lenovo's is not. It is also the capture lane — a workflow built into a Lenovo agent keeps running on the open substrate without Lenovo, but only evolves with Lenovo, and its opinions do not lift to another vendor's agent framework. Self-deployable is not Retained. The ISV lane carries the same finding as every peer row: each partner governs within its own domain, and nothing governs across domains — which points back at the 2C gap.
Distributed across ISV partners, architecturally correct at Layer 3 — except in the first-party lane, where the enterprise inherits Lenovo's workflow judgment and cannot take it elsewhere. That inversion is the row's signature finding: the OEM whose infrastructure software captures least captures most through its own applications.
The AI Library facet scored here is the business capability; its runtime path is scored at 2B and its retrieval pipelines at 1B. Soft spot, low stakes: whether AI Library agents are cleanly products or services-configured deliverables per engagement — the May 2026 release and independent validation support product-grade repeatability; a briefing would firm the boundary. Instrument follow-up (logged, not this row's edit): re-test Dell's and HPE's Layer 3 partner status against the 'entirely ISV' boundary under this cell's lens — read here as both staying partner, since ISV frameworks and deployment services are not vendor-built business applications.
Lenovo has one of the most credible on-prem AI infrastructure foundations in the market. Among the on-prem anchors on this instrument, each builds from what it owns: Dell from servers and storage, HPE from sovereign compute and three owned fabrics, Cisco from network silicon and security. Lenovo's anchor is manufacturing scale and thermal engineering — server breadth, Neptune sixth-generation liquid cooling, eight of the top ten public clouds as customers — and it is the only one of the four that owns neither a network fabric nor, until the April 2026 Infinidat close, any opinion-bearing storage software. Above the rack, capability arrives predominantly as other vendors' IP validated and SKU'd on Lenovo paper: ONTAP, Cloudian, WEKA, Red Hat, Nutanix, NVIDIA.
The row's signature is what the validated-solutions model doesn't do: capture opinions. The enterprise's storage, retrieval, and runtime opinions lift off Lenovo paper to wherever the partner software runs — the most Delegated-heavy authority profile among the OEM rows. One contract with Lenovo is a procurement fact, not an authority fact.
Where Lenovo does capture, three surfaces matter, two of them new in 2026: InfiniBox and InfiniGuard (the Infinidat close gave Lenovo its first owned, opinion-bearing storage software), XClarity One fleet management, and — the inversion worth naming — the AI Library's first-party agents at Layer 3. Lenovo's strongest software capture surface is its applications, not its infrastructure software. The buyer who feels safely un-captured at the infrastructure layers is accumulating workflow opinions in Lenovo-built agents at the top.
Everything GPU-aware above the rack is NVIDIA's judgment — Run:ai and NVIDIA AI Enterprise ride Lenovo paper as five-year subscription SKUs, which changes the invoice, not the authority. Same boundary as Dell and HPE.
Two layers are unclaimed: no pipeline layer (1C) and no reasoning plane (2C) — no owned product, no packaged open-source alternative, and, unlike HPE's Kamiwaza designation or Dell's briefing-confirmed ecosystem strategy, no designated partner and no stated position. Whether those gaps are strategy or omission is this row's open briefing question. The buyer's trade: the broadest menu and the lowest OEM lock-in above the rack, in exchange for owning more of the assembly — and both missing planes — themselves.