Nightly Releases
Dynamo publishes nightly builds from main. Nightlies let you try the latest features and backend upgrades before they land in a stable release. This page covers what nightly publishes, how to install it, and which backend versions the current and recent nightlies ship.
Nightly builds are experimental and are not QA-validated. They are built from the tip of main and may contain bugs, breaking changes, or incomplete features. Use stable releases for production workloads.
Recent Nightlies
Nightly builds
Recent pinned wheel builds
Nightly wheels are pinned by date. Runtime containers use rolling NGC tags, so the container buttons always pull the latest nightly image.
Aug 31, 2026
Aug 30, 2026
Aug 29, 2026
What Gets Published
Every night, the Nightly CI pipeline builds main and publishes:
- Runtime container images (CUDA 13):
vllm-runtime-nightly,sglang-runtime-nightly, andtensorrtllm-runtime-nightlyto NGC, each with an Elastic Fabric Adapter (EFA) variant under a-efatag suffix. - Component container images:
kubernetes-operator-nightly,dynamo-planner-nightly, anddynamo-frontend-nightlyto NGC. - Python wheels:
ai-dynamo,ai-dynamo-runtime, andkvbmto the NVIDIA prerelease index at pypi.nvidia.com. - Helm chart:
dynamo-platform-nightlyto the NGC Helm registry, kept separate from the stabledynamo-platformchart.
The runtime images and the wheels gate the release: if any of them fails to build, that night publishes nothing. The component images, the EFA variants, and the Helm chart stage fail-soft, so a flake in one of them skips that artifact for the night without holding back the rest.
Nightly does not publish Rust crates — for those, use a stable or pre-release build.
Installing Nightly Containers
Nightly images live in their own -nightly NGC repositories so they cannot be pulled accidentally in place of a stable image. Every nightly build pushes an immutable YYYYMMDD-<shortsha> tag and moves the latest tag to that build.
Pin the dated tag for anything you need to reproduce later: latest moves every night, so the image behind it changes underneath you. The runtime repositories also carry a nightly tag, but it stopped tracking main in July 2026 — use latest or a dated tag instead. The component repositories publish the same dated tags and a latest float, without the nightly alias or the EFA variants.
Installing Nightly Wheels
Nightly wheels are published to the NVIDIA prerelease index at pypi.nvidia.com, not the public PyPI. They are Linux manylinux builds for the Python versions in Compatibility; install on a supported Linux host or inside a Linux container. Nightly versions follow PEP 440 dev versioning, X.Y.Z.devYYYYMMDD.
Backend extras such as ai-dynamo[vllm] and ai-dynamo[sglang] use the same flags. For TensorRT-LLM, use the nightly container rather than a PyPI extra.
Backend Versions
Nightlies track main, so the backend versions they ship change as main advances. To find which nightly or stable build ships a given backend version, and get the exact pull or install command, use the build selector in the Kubernetes Quickstart.
To confirm the exact versions a specific nightly shipped, read them from the pulled image:
See Also
- Release Artifacts — stable and pre-release artifact inventory
- Compatibility — hardware, platform, CUDA, and driver support
- Model Early Access Builds — model-specific pre-release container builds