Skip to main content
Enterprise

Supported vendors

This page lists vendor support and device documentation for Dynamia’s commercial HAMi offering. Confirm specific models, driver versions and available features with the Dynamia delivery team.

HAMi

VendorDevice-plugin maintenance channelUsage documentation
NVIDIA (GPU)Dynamia · closed sourceLocal guide (coming soon)
ASCEND (NPU)Dynamia · closed sourceLocal guide (coming soon)
T-HEAD (PPU)Dynamia · closed sourceLocal guide (coming soon)
Cambricon (MLU)Accelerator vendor · open sourceOpen-source guide
Hygon (HCU)Accelerator vendor · open sourceOpen-source guide
MetaX (GPU)Accelerator vendor · closed source (provisional)Open-source guide
Kunlunxin (XPU)Accelerator vendor · closed sourceOpen-source guide
Enflame (GCU)Accelerator vendor · closed sourceOpen-source guide
Moore Threads (GPU)Accelerator vendor · closed source (provisional)Open-source guide
Iluvatar (GPU)Accelerator vendor · open sourceOpen-source guide
AWS (Trainium / Inferentia)Accelerator vendor · closed sourceOpen-source guide
Vastai (GPU)HAMi community · open sourceOpen-source guide
AMD (GPU)HAMi community · open sourceOpen-source guide
Biren (GPU)HAMi community · open sourceOpen-source guide
Teco (DPU)To be confirmedOpen-source matrix (under validation)

The maintenance channel refers to the device plugin used by the linked deployment option. An open-source usage guide does not imply that the plugin itself is open source. Entries with an unconfirmed maintainer or source license are marked “To be confirmed”.

AWS Neuron device-plugin images are publicly distributed, but the plugin itself is not open source; see the AWS Neuron project response.

The Moore Threads GPU Operator includes the device plugin and distributes it through deployment packages and public container images. No public source code or open-source license for the plugin has been identified; its closed-source classification is provisional.

The MetaX GPU Operator device plugin is distributed through container image packages. Software downloads require a developer account, and registry access must be obtained through commercial channels. No public source code or open-source license for the plugin has been identified; its closed-source classification is provisional.

The Kunlunxin device plugin can be obtained from the vendor, but no public documentation is available.

Refer to the delivery documentation for specific models, driver versions and deployment configuration.