6.5

Run vLLM on other accelerators

vLLM supports other accelerators through plugins, and each plugin follows its own release.

Your hardware is not an NVIDIA GPU. When you finish this section, you can find the plugin for your hardware and its version.

Know what is built in and what is a plugin

vLLM 0.31.0 has built-in support for NVIDIA GPUs, AMD GPUs through ROCm, Intel GPUs, and CPUs. Other hardware runs through a plugin. A plugin is a separate Python package that registers a platform with vLLM when it is installed. Install it next to vLLM, and vLLM finds it.

The plugin design came from an RFC in December 2024. Since then, several backends that lived inside vLLM moved out into plugins.

Find your plugin

HardwarePluginHow it follows vLLM
Google TPUtpu-inference, which is moving to the name vllm-jaxa release for each vLLM release, with its own image
Huawei Ascend NPUvllm-ascendrelease candidates for recent vLLM versions, and final releases about every three months
Intel Gaudivllm-gaudireleases based on a named vLLM version
AWS Trainium and Inferentiavllm-neuronreleases that name the vLLM version they build on
IBM Spyresendnn-inferenceits own version numbers
Apple silicon GPUvllm-metal, a community plugin on MLXits own releases

Check the version before you plan

A plugin often supports an older vLLM than the newest release. In October 2026, the newest final release of vllm-ascend targeted vLLM 0.23.0, while vLLM itself was at 0.32.0. The TPU plugin had a release for vLLM 0.31.0 within days of it.

Before you plan a feature on your hardware:

  1. Find the newest plugin release, and read the vLLM version it targets.
  2. Read that vLLM version's documentation, not the newest one.
  3. Check the feature table of the plugin. Some features of the CUDA path, such as some quantization formats and attention backends, have no version on other hardware.

Not measured on our hardware. We ran only NVIDIA GPUs.

vLLM 0.31.0 · db9527a · 2026-10-05 · Edition 2026.10