LLMSwaps

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

What holding the weights changes about all this

It removes the retirement question and replaces it with an operations budget. One publisher in this register distributes weights with a licence and download commands on the model card. A copy already taken keeps working, so no date applies to it and nobody has to be told anything. As of 2026-09-12.

What the artefact is, on each kind of entry, and what a withdrawal reaches. Recorded 2026-09-12.
EntryWhat is publishedDetail
Wan-AIWeights, a licence and download commandsA withdrawal reaches the listing only
Microsoft FoundryA hosted version, with a dated retirementRequests return a named status after it
Amazon BedrockHosted models, with three statesRemoved from all regions at the end
Every application trackedAccess to a menu, with no datesNothing you hold, and nothing promised

Inclusion rule. An entry appears when its own pages describe what a customer ends up holding. A hosted service that serves published weights is recorded as a hosted service. Order. The publisher of weights first, then hosted arrangements.

1The trade is uncertainty for overhead

A held copy removes somebody else's schedule and adds hardware, storage, retention and the work of keeping an inference stack alive. Only the second of those can be budgeted in advance.

Neither side is safer in the abstract. For a long run of episodes, a cost that can be planned beats a date that cannot be predicted, which is the argument rather than a recommendation.

Uncertainty exchanged for overheadA held copy removes somebody else's schedule and adds hardware, storage, retention and the work of keeping an inference stack alive. Only the second of those can be budgeted in advance.HostedA menu, a price, and a date ifanybody published oneEnds on their dayNothing you hold, andnothing promisedDownloadedWeights, a licence and a commandon the model cardNothing reaches itRuns as long as you keepthe hardware aliveThe billEither a subscription or amachineBoth are realOne is a date you await,one is a line you budgetTwo ways to reach the same modelProcurement risk replaces schedule risk, and arrives without a date too
Fig. 1 Neither side is safer in the abstract, and only one of the two costs can be planned.

2Permission is the fact that gets published

What makes a held copy usable is the licence on the card, not a retention policy. That is a different kind of statement from a date and it is the reason this arrangement appears in a register about retirements at all.

It settles permission and not capability. Nothing guarantees the weights keep running on next year's tooling, and nothing obliges the publisher to keep publishing updates.

3Procurement risk does not disappear

If a listing comes down, nobody loses a running copy and anybody who has not fetched it yet loses the chance, including for new hardware later. That arrives without a date either.

The mitigation is keeping the weights rather than the address. No published state will remind a team to do it, which the published weights term sets out.

4Sources

Dates come from the vendor that makes the model; menus come from the app, and both are linked on the calendar. Read 2026-09-12. What counts as a date is on sourcing. Nearby: Tier and model, Who publishes a date, How much notice.