# Validating GPU Platforms with Runtime AI Inventory via the NVIDIA DSX AI Factory

DevFeed: [Validating GPU Platforms with Runtime AI Inventory via the NVIDIA DSX AI Factory](<https://devfeed.tech/articles/validating-gpu-platforms-with-runtime-ai-inventory-via-the-nvidia-dsx-ai-factory-129632.md>)

Original publisher: [Read original article](<https://developer.nvidia.com/blog/validating-gpu-platforms-with-runtime-ai-inventory-via-the-nvidia-dsx-ai-factory/>)

Author: Mark Chmarny

Published: 2026-11-11T17:00:00Z

Content type: tutorial

Language: en

Sources: [NVIDIA Developer](<https://devfeed.tech/sources/nvidia-developer.md>), [NVIDIA Technical Blog](<https://devfeed.tech/sources/nvidia-technical-blog.md>)

Topics: [NVIDIA DSX](<https://devfeed.tech/topics/nvidia-dsx.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Nvidia](<https://devfeed.tech/topics/nvidia.md>), [NVIDIA NIM](<https://devfeed.tech/topics/nvidia-nim.md>)

Tags: [agentic-ai-generative-ai](<https://devfeed.tech/tags/agentic-ai-generative-ai.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-factory](<https://devfeed.tech/tags/ai-factory.md>), [ai-inventory](<https://devfeed.tech/tags/ai-inventory.md>), [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [data-center-cloud](<https://devfeed.tech/tags/data-center-cloud.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [developer-tools-techniques](<https://devfeed.tech/tags/developer-tools-techniques.md>), [dsx](<https://devfeed.tech/tags/dsx.md>), [dsx-ai-factory-platform](<https://devfeed.tech/tags/dsx-ai-factory-platform.md>), [dynamo](<https://devfeed.tech/tags/dynamo.md>), [factory](<https://devfeed.tech/tags/factory.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [inventory](<https://devfeed.tech/tags/inventory.md>), [kubeflow](<https://devfeed.tech/tags/kubeflow.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [nvidia](<https://devfeed.tech/tags/nvidia.md>), [nvidia-dsx](<https://devfeed.tech/tags/nvidia-dsx.md>), [nvidia-dynamo](<https://devfeed.tech/tags/nvidia-dynamo.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [platform](<https://devfeed.tech/tags/platform.md>), [requires](<https://devfeed.tech/tags/requires.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [scale](<https://devfeed.tech/tags/scale.md>), [slurm](<https://devfeed.tech/tags/slurm.md>), [with](<https://devfeed.tech/tags/with.md>)

## AI overview

AICR creates reproducible, version-locked GPU platform recipes and validates them against a cluster; k8s-aibom adds runtime inventory of recognized AI workloads. On supported GKE recipes, k8s-aibom is selected in the recipe, then deployed and checked through an AICR bundle. Namespace labels enable AIBOM reporting, while the controller still reads workload and pod specs cluster-wide; no sink or secret access is configured by default. AIBOMs can identify models, runtimes, and related dependencies and include confidence tiers with evidence locators. Coverage is limited to supported workload kinds with recognized AI signals. Records can exist before pods run, so readiness does not establish successful scheduling or execution. The integration does not yet correlate AICR deployment intent with observed workloads, and runtime observations are unsigned by default. Reported controller overhead was measured on CPU-only nodes with workload pods pending, so it describes inventory overhead rather than GPU workload performance.

## Source excerpt

As teams deploy and scale AI workloads using NVIDIA Dynamo, Kubeflow, or Slurm, tracking what actually runs requires visibility beyond the platform...