Enterprise Hardware Reference Architecture Foundation
The NVIDIA Enterprise AI Factory Reference Design is built on NVIDIA Enterprise Hardware Reference Architectures. Use that portfolio to identify the applicable architecture family. The linked technical publications remain the source of truth for its infrastructure design points.
After you select an architecture family, use OEM AI Factory Offerings to discover publisher-owned full-stack options. Confirm orderable configurations, lifecycle, compatibility, and support directly with the applicable OEM.
Explore storage and data infrastructure ecosystem solutions.
What the Software Design Consumes
The software design consumes the following infrastructure capabilities:
What Remains Outside This Site
Refer to authoritative hardware and OEM sources for the following details:
- Server, GPU, NIC, DPU, switch, and storage bills of materials.
- Physical and logical fabric topology.
- Scale-unit composition and maximum scale.
- Rack, power, cooling, cabling, and facility design.
- Infrastructure endorsement or certification criteria.
- Time-sensitive product compatibility and support matrices.
Confidential-Computing Boundary
The hardware foundation supplies trust capabilities and evidence. It does not decide which workloads require them or accept the resulting risk. Governance and Assurance defines the approved policy and evidence requirements. Platform Identity and Trust Services appraise evidence and condition access, credential, or key release. Use the NVIDIA Trusted Computing Solutions library to confirm supported hardware, firmware, attestation, and confidential-computing combinations.
For published confidential inference deployment patterns, refer to the following architectures:
- Deploying Proprietary Models Securely with NVIDIA Confidential Computing on Self-Hosted Virtual Machines.
- Deploying Proprietary Models Securely with NVIDIA Confidential Computing on Self-Hosted Kubernetes.
DPU and Separated-Control Boundary
The hardware foundation identifies supported DPU and network infrastructure. Isolation and Runtime Services defines when an implementation uses a separately managed enforcement, monitoring, or containment domain. Accelerator Operators manage supported platform software; they do not replace runtime policy or accept workload risk.
Use the NVIDIA BlueField platform and NVIDIA DOCA pages for current product capabilities. Use the selected Enterprise Hardware Reference Architecture and OEM guidance for supported system placement, topology, lifecycle, and configuration.
Selection Workflow
Use the Workload Envelope
Carry demand, data, availability, security, growth, and facility constraints from the core design.Select the Architecture Family
Evaluate the current Enterprise Reference Architecture patterns and their supported scale points.Decision Inputs and Authoritative Owners
Use the following authorities to make and record infrastructure decisions:
Handoff Milestones
Complete the following handoffs before you approve the deployment design:
- NVIDIA architecture guidance: Agree on the reference architecture family, capability envelope, and support-matrix constraints.
- OEM system configuration: Translate those constraints into an OEM orderable configuration and lifecycle plan.
- Customer design approval: Confirm facility fit, operational ownership, support paths, exceptions, and sign-off evidence in the deployment decision record.
This page intentionally does not restate hardware architecture details. Refer to the current Enterprise Reference Architecture publication for those decisions.