LLMSwaps

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

A file you hold against a request that fails

Both entries have nothing to say about deleting material, for opposite reasons. One publishes weights, so the capability is a file the customer already holds and a withdrawal cannot reach it. The other serves an interface, and states precisely what a request receives after the retirement date. As of 2026-09-22.

What each entry says happens once access ends. Recorded 2026-09-22.
On this pointWan-AIMicrosoft Foundry
What endsNew downloads from the listingEvery inference request
What the customer keepsThe weights, under the stated licenceOutput already returned to them
Can the capability continueYes, on hardware they already runNo, and the date cannot be moved
What is published about itA licence and download commandsA specific status code
What replaces the riskHardware, storage and operationsA migration to another version

Inclusion rule. Both cells on a row come from the entry's own published pages: a model card and repository listing for the publisher, a lifecycle policy for the platform. Order. What ends first, then what survives it.

1Two clean answers, and both are unusual

Most entries in this register leave the question open. These two close it in opposite directions: one because the artefact was never theirs to remove, the other because the page names the exact failure a caller will see.

Precision of either kind is rare here. Eleven entries publish neither a licence for a held copy nor a described behaviour after a date.

Two clean answers about what survives a retirementOne entry publishes weights, so the capability is a file the customer already holds and a withdrawal cannot reach it. The other serves an interface and states the exact status a request receives once the date has passed.The arrangement ends. What does the customer still have?You hold the weightsThe capabilityRunning under the licence printed on themodel card.You called an interfaceOnly the outputRequests return a named status, and thedate cannot move.A status code is the only automated warning available anywhere in this register
Fig. 1 Precision of either kind is rare here: eleven entries publish neither a licence for a held copy nor a described behaviour after a date.

2A status code is a planning instrument

Naming the response lets software tell a retirement apart from a transient fault, so a production learns about the date from its own logs. That is the only automated warning available anywhere in this register.

It arrives on the day rather than before it. Which is why the platform's notice period matters separately, and why the two publishing platforms are worth reading against each other.

3Holding the weights moves the work rather than removing it

A copy that cannot be withdrawn still has to be stored, backed up and served on hardware somebody pays for. The uncertainty becomes overhead, which is a cost a production can budget in advance.

Neither arrangement is safer in the abstract. The reading for the publisher sets out what the licence does and does not settle about a held copy.

4Sources

Both readings come from the pages the entries publish themselves: Wan-AI and Microsoft Foundry, read 2026-09-22. The column being compared is Stored work. Other pairs: Wan-AI and Sora, Pika and invideo AI.