Skip to navigation

Enterprise Hardware Reference Architecture Foundation

View as Markdown
View the hardware foundation in the interactive architecture

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:

CapabilityInterface Assumption
Accelerated computeSufficient GPU, CPU, memory, local storage, interconnect, and isolation for the workload envelope. Refer to Enterprise Hardware Reference Architectures.
Scale-up and scale-out networkingBandwidth, latency, loss, topology, segmentation, and RDMA capabilities required by the selected workloads and services. Refer to NVIDIA networking documentation.
Separated infrastructure servicesSupported NIC or DPU resources for offloaded networking, storage, isolation, monitoring, and containment when the approved design requires a control domain independent of the host. Refer to NVIDIA DOCA Platform Framework.
Data infrastructureCapacity, throughput, metadata behavior, protection, locality, retention, and recovery required by datasets, models, indexes, checkpoints, and telemetry. Refer to Enterprise Hardware Reference Architectures.
Confidential computingSupported hardware and firmware roots of trust, measured execution, attestation evidence, protection in use, and separable infrastructure control domains required by the approved threat model. Refer to NVIDIA Trusted Computing Solutions.
FacilitiesPower, cooling, rack, cabling, environmental, physical-security, serviceability, and resilience envelope. Refer to Enterprise Hardware Reference Architectures.
LifecycleCurrent firmware, driver, platform support, diagnostics, replacement, upgrade, and escalation paths. Refer to NVIDIA AI Enterprise support matrix.

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:

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

1

Use the Workload Envelope

Carry demand, data, availability, security, growth, and facility constraints from the core design.
2

Select the Architecture Family

Evaluate the current Enterprise Reference Architecture patterns and their supported scale points.
3

Confirm Implementation Support

Check current system, platform, network, storage, and software support with authoritative owners.
4

Return the Infrastructure Contract

Record the capacity, topology, service, lifecycle, and availability assumptions consumed by the software layers.

Decision Inputs and Authoritative Owners

Use the following authorities to make and record infrastructure decisions:

Decision InputUse This AuthorityRequired Handoff Output
Workload type, service objectives, data paths, isolation, and growthWorkload requirements record and applied Capability Reference Designs or Industry ProfileApproved requirement set and unresolved risks
GPU, system, network, storage, topology, scale, and facilitiesNVIDIA Enterprise Reference Architecture portfolio and its linked technical publicationsSelected reference architecture family, scale assumptions, and infrastructure design owner
Operating system, hypervisor or cloud, Kubernetes, drivers, operators, and release compatibilityNVIDIA AI Enterprise Infrastructure Support MatrixRelease-specific compatibility evidence and exception list
OEM platform, configuration, lifecycle, and commercial supportOEM AI Factory Offerings and OEM configuration and support documentation aligned to the selected reference architectureNamed OEM offer, configuration owner, support path, and assumptions
Ecosystem software candidatesEcosystem Solution Catalog and publisher documentationCandidate list and publisher-owned support evidence

Handoff Milestones

Complete the following handoffs before you approve the deployment design:

  1. NVIDIA architecture guidance: Agree on the reference architecture family, capability envelope, and support-matrix constraints.
  2. OEM system configuration: Translate those constraints into an OEM orderable configuration and lifecycle plan.
  3. 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.