> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nvidia.com/ai-enterprise/ai-factory/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/ai-enterprise/ai-factory/_mcp/server.

# Ecosystem Solution Catalog

> Ecosystem solutions for discovery and architecture planning across the NVIDIA Enterprise AI Factory Reference Design and Industry Profiles.

Explore software and data-platform offerings aligned to the NVIDIA Enterprise AI Factory Reference Design. Filter by architecture context or solution category, then use publisher-maintained technical resources to identify candidates for further evaluation.

#### [Looking for an OEM System?](/ai-enterprise/ai-factory/ecosystem-integrations/oem-ai-factory-offerings)

Explore publisher-owned, full-stack OEM AI Factory offerings, then confirm the applicable configuration, lifecycle, and support guidance with the OEM.

![](/ai-enterprise/ai-factory/_fern-files/enterprise-ai-factory-plans.docs.buildwithfern.com/f94ae679ab036440e24542fe922e42788a8f2065695dfec8edbf0c51f518d994/assets/oem-logos/cisco.svg)![](/ai-enterprise/ai-factory/_fern-files/enterprise-ai-factory-plans.docs.buildwithfern.com/4a14e6b845f62ff38095c0493772abf10f204ce0c38b5a5a9fef59a6d9e9a757/assets/oem-logos/dell.svg)![](/ai-enterprise/ai-factory/_fern-files/enterprise-ai-factory-plans.docs.buildwithfern.com/4f4084cb206f72fec8f28287b8dd75663b597573d6fba7caedd99a6b27183045/assets/oem-logos/hpe.svg)![](/ai-enterprise/ai-factory/_fern-files/enterprise-ai-factory-plans.docs.buildwithfern.com/125ee0d5270f5e06fad243b7520e517faa21e1cc385fb735119d8b8b845e0d63/assets/oem-logos/lenovo.svg)![](/ai-enterprise/ai-factory/_fern-files/enterprise-ai-factory-plans.docs.buildwithfern.com/a7ac2a7287f1281d5341d52b734e28204f237e1d83991d3241e5d9ebdb9b2b72/assets/oem-logos/supermicro.png)

> **Info**
>
> The catalog supports architecture planning and solution discovery. Entries identify where an offering may contribute to the reference design and link to publisher-maintained resources. Confirm product fit, interoperability, deployment requirements, security, and support directly with each publisher.

## Using the Catalog

* **Architecture context** narrows results to the Core design or Government Industry Profile.
* **Solution categories** map offerings to the responsibilities they can address across the reference-design stack.
* **Partner results** keep distinct products together and link to publisher-maintained technical resources.
* **Context badges** identify Core and Government applicability.

## Catalog Boundary

Use the Solution Catalog to identify candidate offerings during discovery and architecture planning. An entry indicates relevance to one or more reference-design responsibilities; it does not prescribe a product, establish interoperability, or define a supported bill of materials. Verify product versions, dependencies, deployment constraints, security requirements, and support status directly with each publisher.