LLMSwaps

Which model each app runs today, and when it last changed

The default is whichever copy you kept

Several repositories are published, covering different tasks and sizes, and a user chooses which to download. So the starting engine is whichever copy a production already holds, and it stays that way until somebody deliberately fetches another. No page decides it and no page can move it. As of 2026-09-22.

What publishing several repositories settles about a starting engine. Recorded 2026-09-22.
What the page is askedWhat Wan-AI publishesWhat that leaves open
Is a starting tier statedNot applicable, the user chooses a repositoryThe listing offers several, by task and size
Where the effective default sitsOn the production's own storageIt changes only when somebody downloads
Can the publisher move itNo, a listing change reaches no copyDownload commands are on the model card
What that costs insteadDeciding, fetching and keeping the weightsOperations work rather than a waiting game

Inclusion rule. Filled when the entry's own public page says which model a new project starts on, or when a single-model menu makes the answer follow from the list having one line. Order. What does not apply first, then where the choice actually lives.

1A default that cannot be changed from outside

On every hosted entry in this column the starting engine is somebody else's to move. Here it is a file on a disk, so the only way it changes is a deliberate act by the team using it.

That is the strongest form of stability in the register and it is not published as a commitment, because it does not need to be. It follows from where the weights live.

A default that cannot be moved from outsideOn every hosted entry the starting engine belongs to somebody else. Where the weights are on local storage the only way it changes is a deliberate download, so stability and isolation turn out to be the same property.A hosted defaultA copy you holdChanged byThe seller, on their dateA download you decide to runWarningWhatever they publishNone neededUpgradesArrive, sometimes unaskedNever arrive at allCostWaiting and watchingHardware and an inference stackStability and isolation are one property, priced as chores
Fig. 1 Nobody upgrades you, and nothing warns you that the copy you chose is no longer what the publisher would recommend.

2Choosing is real work, and it happens once

The listing covers several repositories with different tasks and sizes, so somebody has to decide which one the pipeline uses. That decision then persists silently, exactly like a hard-coded identifier in a request.

Persisting silently is usually a risk. Here it is the point: a production can finish a season on the same weights it started on, whatever the publisher does to the listing.

3What the arrangement costs in this column's terms

Nobody upgrades you, nobody tells you a better version exists, and nothing warns you that the weights you chose are no longer what the publisher would recommend. Stability and isolation are the same property.

The register records the other side of that trade in the succession reading: no schedule to fear, and an inference stack to keep alive.

  • Models published
    Wan2.2-T2V-A14B, Wan2.2-I2V-A14B, Wan2.2-TI2V-5B, Wan2.2-S2V-14B and the Animate variantsweights rather than an endpointWan-AI, repository listing / recorded 2026-09-22
  • How a copy is obtained
    Download commands for the weights are printed on the model cardWan-AI, Wan2.2-T2V-A14B model card / recorded 2026-09-22

4Sources

Read from the repository listing on huggingface.co, 2026-09-22. The whole entry is on Wan-AI, and the column it sits in is on Default tier. Same column, other entries: SceneMixer, Pika.