NodeValid

Published video-model weights, licences and hardware notes

Apache against a licence written in-house

Mochi 1 is Apache 2.0, stated in the repository. HunyuanVideo carries tencent-hunyuan-community on its model card. Ten billion parameters against over thirteen, and two very different clearance costs. As of 2026-09-12.

Mochi 1 and HunyuanVideo on the same columnComparable model sizes under a standard licence and a bespoke one show the clearance cost separating from the technical one.Mochi 1HunyuanVideoLicence, as each vendor statesitApache 2.0tencent-hunyuan-communityThe detail published beside itStated in the repositoryA vendor-written licence, not a standardpermissive oneSize, from the same pages10 billion parametersOver 13 billion parametersSize held roughly constant, terms varied
Fig. 1 Similar weights, different paperwork, and the paperwork is the variable.
Mochi 1 and HunyuanVideo on the licence column, read from github.com/genmoai and github.com/Tencent-Hunyuan. Recorded 2026-09-12.
PointMochi 1HunyuanVideo
Licence, as each vendor states itApache 2.0tencent-hunyuan-community
The detail published beside itStated in the repositoryA vendor-written licence, not a standard permissive one
Size, from the same pages10 billion parametersOver 13 billion parameters

Inclusion rule. Two families whose published values in this column lead to opposite decisions. A pair that happens to agree is not listed, because agreement is already visible on the column summary. Order. The column itself first, then its detail, then the columns that qualify it.

1A near-controlled comparison of terms

Ten billion parameters and over thirteen billion are close enough that neither release is in a different category of use. The licence is the axis that separates them for anyone deciding what to build on.

Both also state high memory figures, about 60GB on one card for Mochi and 60GB peak for HunyuanVideo, so the hardware question does not distinguish them either.

2What Apache 2.0 settles here

Copying, modifying and redistributing the weights, subject to attribution and to carrying the licence along. For a team planning to publish a fine-tune, that is the paragraph they need and it is already known.

It does not settle what happens to generated output. Standard permissive licences generally do not address that, and the register does not read either document on anyone's behalf.

3Why the bespoke licence exists

A vendor writes its own terms because it wanted to say something a standard licence does not say. That addition is exactly the part worth reading, and its existence is the reason the row cannot be cleared by recognition.

The register records the tag, the page and the date. A paraphrase would be the sentence a reader relied on, and it is the one thing this register will not supply.

4Sources

Read from github.com/genmoai and github.com/Tencent-Hunyuan on 2026-09-12. Full entries: Mochi 1 and HunyuanVideo. What this column is quoting is on licence. Nearby pairs: Exact against a bound, Decomposed or round.