01
VDN-H3 has two licensing layers
VDN-H3 has a licensing split that is easy to miss. OpenVDN's training and inference code is Apache-2.0, while the released VDN-H3 weights are a derivative of MiniMax H3 and remain governed by the MiniMax H3 Community License Agreement.
02
Code license: Apache 2.0
The OpenVDN repository licenses its training and inference code under Apache License 2.0. Its NOTICE explicitly separates that repository code from the model weights and says the Apache license does not replace the license governing MiniMax H3 or derivative weights.
The same distinction applies to wrappers and interfaces. An Apache-licensed launcher or ComfyUI custom node can be permissively licensed code while the model files loaded by it remain subject to a different agreement.
03
Weight license: MiniMax H3 Community License
The OpenVDN model card identifies VDN-H3 as a MiniMax H3 derivative and distributes the weights under the MiniMax H3 Community License Agreement. Download availability does not turn those weights into Apache-licensed artifacts.
The current agreement defines an Applicable Territory that excludes the European Union, United Kingdom, Republic of Korea and United States of America. The model materials direct users outside the applicable territory to contact MiniMax about licensing. Recheck this language because model licenses can change.
04
Redistribution and deployment need a separate review
The current release documents redistribution conditions, modification notices, NOTICE handling and an incorporated Acceptable Use Policy. A downloadable model bundle, desktop package, customer deployment and hosted backend can raise different obligations, so do not reduce the agreement to a blanket yes-or-no commercial-use answer.
Before deployment, record the exact checkpoint, repository revision, license version, deployment territory, whether weights are redistributed or only used on a hosted backend, and any modifications that trigger notice requirements.
05
So, is commercial use allowed?
A safer answer is that VDN-H3 is not an unrestricted Apache-licensed model. Commercial teams need to evaluate the MiniMax H3 Community License governing the weights and confirm that their territory, use and distribution model are authorized.
Technical access through Hugging Face does not override license terms. If your deployment is in an excluded territory or involves redistribution, use the current agreement rather than relying on a summary or an old model-card snapshot.
06
VDN-H3 license FAQ
- Is VDN-H3 Apache 2.0? The OpenVDN code is; the derivative model weights are not.
- Does an Apache-licensed ComfyUI node change the model license? No. Interface code and model weights are separate layers.
- Can download availability be treated as permission to use the weights anywhere? No; the agreement's territorial and use conditions still apply.
- Should commercial teams rely on this article alone? No. Check the live license and obtain legal guidance where appropriate.
Sources
Primary and supporting sources
Facts were rechecked against the linked sources immediately before publication. Pricing, product availability and rollout status can change.