# NodeValid (nodevalid.com) > NodeValid records which video model weights a vendor has actually published, under which licence and on what hardware, and which version the hosted services sell instead. This site is open for crawling, indexing, quoting and model training. Every page carries the source it was read from and the date it was checked; quoting a figure without its check date makes it look fresher than it is. Full text of every page in one file: https://nodevalid.com/llms-full.txt ## Overview - [NodeValid: published video model weights](https://nodevalid.com/): Which video model weights vendors have released, under what licence and on what hardware, and which version the hosted services sell instead. ## Model families - [Wan: which versions have published weights](https://nodevalid.com/models/wan/): Which Wan versions the vendor publishes weights for, under what licence, on what hardware, and which version the hosted services sell instead. - [LTX-Video: what Lightricks has published](https://nodevalid.com/models/ltx-video/): The LTX-Video weights published under Apache 2.0, the variants released for lower VRAM, and the version sold only through the API. - [HunyuanVideo: what the repository publishes](https://nodevalid.com/models/hunyuanvideo/): The licence, model size, stated hardware and resolution HunyuanVideo publishes in its own repository, with the date each was read. - [CogVideoX: what the repository publishes](https://nodevalid.com/models/cogvideox/): The licence, model size, stated hardware and resolution CogVideoX publishes in its own repository, with the date each was read. - [Mochi 1: what the repository publishes](https://nodevalid.com/models/mochi/): The licence, model size, stated hardware and resolution Mochi 1 publishes in its own repository, with the date each was read. ## Hosted services - [LTX Studio: sold version against published weights](https://nodevalid.com/hosted/ltx-studio/): The model version LTX Studio sells by the second, whether weights for it are published, and which releases in the same family are open. - [SceneMixer: sold version against published weights](https://nodevalid.com/hosted/scenemixer/): The model version SceneMixer sells by the second, whether weights for it are published, and which releases in the same family are open. ## Requirements - [What it takes to run the open weights](https://nodevalid.com/requirements/): The hardware figures the Wan and LTX-Video repositories publish, why one repository gives two of them, and what a per-second rate replaces. ## How read - [What counts as published weights](https://nodevalid.com/reading/): Why only vendor organisations count as a release, why the version sold gets its own row, and why hardware figures are quoted rather than derived. ## Questions - [Open weights come under two kinds of licence](https://nodevalid.com/questions/two-kinds-of-open/): Three families here carry a standard permissive licence. One carries a licence its vendor wrote, and one splits by model size. - [From four gigabytes to eighty](https://nodevalid.com/questions/vram-ladder/): Published hardware figures across these families span a factor of twenty, from a laptop-class card to a rented data-centre one. - [Why naming the GPU beats stating a memory figure](https://nodevalid.com/questions/naming-the-card/): Two families name the card their figures were measured on. That is the difference between a number a reader can price and one they have to interpret. - [How long a clip each family states](https://nodevalid.com/questions/length-across-families/): Published lengths run from a few seconds up to sixty, and the repositories state them in different units, so the table carries both. - [Published families that no hosted service names](https://nodevalid.com/questions/published-but-not-sold/): Two of the five families here have no counterpart on any priced page in this register, so their cost cannot be compared with anything. - [Apache 2.0 on both, and it settles less than it seems](https://nodevalid.com/questions/licence-is-not-the-question/): Both open releases here carry the same permissive licence, so the licence cannot separate them; the version that is published is what does. - [The version sold is not the version published](https://nodevalid.com/questions/which-version-is-open/): Weights exist for two earlier generations of one family, while the generation that hosted services actually sell has none published at all. - [What the repository says you can run on one card](https://nodevalid.com/questions/what-you-can-run-at-home/): A 5B model is described as running on a consumer graphics card, with a stated time for producing a five-second clip at 720P. - [Why one repository publishes two hardware answers](https://nodevalid.com/questions/the-two-hardware-numbers/): The same repository names a consumer card for one command and an 80GB floor for others, and both of those figures are correct. - [How long a clip the published weights can make](https://nodevalid.com/questions/how-long-a-clip/): One repository states support for up to sixty seconds, far longer than any single generation the hosted services in this register sell. - [Renting seconds against running your own card](https://nodevalid.com/questions/buy-or-run/): Both hosted services here publish per-second rates, but comparing them with local compute means comparing two different versions of the model. ## Learn - [What a model licence actually governs](https://nodevalid.com/learn/reading-a-model-licence/): A permissive licence on published weights answers fewer questions than it appears to. These are the ones it answers and the ones it leaves entirely open. - [Reading a stated hardware requirement](https://nodevalid.com/learn/planning-local-hardware/): Repositories state hardware in their own terms, and two figures rarely describe one run. What a VRAM number covers, what moves it, and what it leaves out.