NodeValid

Published video-model weights, licences and hardware notes

Published families that no hosted service names

Two families here appear on a priced page: Wan, sold as 3.0 by the second, and LTX-Video, sold as LTX-2.5. The rest publish weights that no hosted service in this register names beside a rate, so hardware is the only cost their published material shows. As of 2026-09-22.

Families with published weights and no hosted counterpartTwo families publish weights and parameter counts but are named on no hosted service's priced page in this register, so neither has a per-second rate to be set against. A cost comparison needs two sides, and these have one. A family can gain a counterpart at any time.Published weightsParameter counts statedDownloadableOne side of a comparisonA hosted rateNothing here names themNothing to quoteThe other side is absentA cost comparisonRecorded as one-sided rather than estimated
Fig. 1 Parameter counts are the most quoted field on these pages and the least useful one. What is missing here is the other side of the division.
What the repositories actually stateFilled where the repository states something, hollow where it does not. A blank is not an inference.What the repositories actually stateWhat is publishedWanWan — What is published: Counterpart: Wan 3.0, by SceneMixerLTX-VideoLTX-Video — What is published: Counterpart: LTX-2.5, by LTX StudioThe other thirteenThe other thirteen — What is published: No hosted counterpart in this register
Fig. 2 Filled where the repository states something, hollow where it does not. A blank is not an inference.
Which published families have a commercial counterpart in this register and which do not. Recorded 2026-09-22.
ItemWhat is publishedDetail
WanCounterpart: Wan 3.0, by SceneMixerSold by the second; no weights published for 3.0
LTX-VideoCounterpart: LTX-2.5, by LTX StudioSold by the second; no weights published for 2.5
The other thirteenNo hosted counterpart in this registerNo per-second rate to set against the hardware figures

Inclusion rule. A counterpart exists when a hosted service names the family on a page carrying a price. A service that sells unnamed tiers cannot be matched to any family. Order. Families with a counterpart first.

1A cost comparison needs two sides and these have one

For the families with a hosted counterpart, a reader can weigh hardware against a per-second rate, with the caveat that the versions differ. For the thirteen without one there is no rate at all, so the only cost visible is the hardware one.

That is not a criticism of either family. It is a statement about what this register can compute, and stating it stops a reader looking for a break-even figure that does not exist.

2Parameter counts are the field most often quoted and least often useful

Thirteen billion against ten billion tells a reader almost nothing about output, cost or hardware, and two entries here publish around thirteen billion while stating memory figures ten times apart. It is recorded because repositories publish it and readers look for it, not because it predicts anything the other fields do not say better.

The memory figures and the named cards are the fields that decide whether a model can be run; the parameter count mostly decides how the model is described in headlines.

3A family can gain a counterpart at any time

The moment a service names one of these on a priced page, the row changes and a comparison becomes possible. That is the ordinary way this register moves: nothing about the weights changes, and what a buyer can work out does.

Until then the honest description is published, downloadable, and not for sale by the second anywhere this register reads.

4Sources

Repository statements and hosted rates are linked from the model pages and the method page, checked 2026-09-22. Hardware figures are set out on requirements. Nearby: Licence vs weights, Which version, Running it locally.