LLMSwaps

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

Files that were never held against files handed over

Neither entry has anything to say about deleting material and both have a structural reason. On one, generation happens on hardware the customer controls, so nothing was ever held. On the other, each output unit is delivered and billed, so the relationship ends at delivery. As of 2026-09-22.

Why neither entry holds material, and what follows. Recorded 2026-09-22.
On this pointWan-AIfal
Where generation happensOn hardware the customer runsOn the platform, per request
What the customer receivesOutput, on their own storageAn output unit, then billed
Is a library offeredNo; there is nothing to offerNot on the priced page
What a withdrawal reachesNothing already downloadedA purchasable line, not past output
Who keeps the filesThe production, from the startThe production, after delivery

Inclusion rule. Both cells on a row come from the entry's own published pages: a repository listing for the publisher, a priced page for the platform. Order. Where generation happens first, then who ends up holding the files.

1Two structurally empty cells, and one filled cell elsewhere

Most blanks in this column mean nobody was asked. These two mean nobody holds anything. That distinction matters because a reader comparing cells would otherwise treat the most settled arrangements here as the least informative.

The one filled cell in the column belongs to a shutdown that deleted material after an export window. Neither of these arrangements could produce that outcome.

Two structurally empty cells, and one filled cell elsewhereMost blanks in this column mean nobody was asked. These two mean nobody holds anything, which matters because a reader comparing cells would otherwise treat the most settled arrangements as the least informative.On your hardwareGeneration happens where theweights were downloadedNothing is heldBackups are a chore youtook on knowinglyPer output unitDelivered and billed, one unitat a timeEnds at deliveryThe invoice records whichengine produced itInside a productA library the vendor keeps foryouUntil a shutdownDeletion after an exportwindow, in the one case onrecordWhere material can liveRetention becomes the production's job in the first two
Fig. 1 The one filled cell in the column belongs to a shutdown that deleted material after an export window.

2Per-output billing records the engine as a side effect

Because each model carries its own price, the invoice already says which engine produced what. On the download arrangement the record has to be kept deliberately, because nothing bills anybody.

So one of the two produces the bookkeeping this register keeps recommending, and the other requires the discipline to do it unprompted.

3Retention becomes the production's job either way

Neither entry keeps a copy to fall back on. Backups, retention periods and storage costs belong to the customer from the first delivered second.

That is the correct arrangement and it is not free. The reading for the publisher sets out the chores that replace a retention policy.

  • 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 the meter works
    Video models are billed by output unit, per second or per video depending on the modelquoted from the pagefal, pricing page / recorded 2026-09-22

4Sources

Both readings come from the pages the entries publish themselves: Wan-AI and fal, read 2026-09-22. The column being compared is Stored work. Other pairs: Foundry and Bedrock, Foundry and the Gemini API.