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. From 3 source pages, read 2026-09-22; no maker pays to be listed.
| Entry | What is published | Detail |
|---|---|---|
| Wan-AI | Weights, a licence and download commands | A withdrawal reaches the listing only |
| Microsoft Foundry | A hosted version, with a dated retirement | Requests return a named status after it |
| Amazon Bedrock | Hosted models, with three states | Removed from all regions at the end |
| Every application tracked | Access to a menu, with no dates | Nothing 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.
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.
- Models publishedWan2.2-T2V-A14B, Wan2.2-I2V-A14B, Wan2.2-TI2V-5B, Wan2.2-S2V-14B and the Animate variantsweights rather than an endpoint
- Licence stated on the weightsApache 2.0
- How a copy is obtainedDownload commands for the weights are printed on the model card
- What the endpoint does after the retirement dateAll inference requests return 410 Gone
4A pipeline across model versions
Model end dates touch “Downloadable weights”; SceneMixer's guides describe how its pipeline treats the models it runs:
Doubao Seed 2.1 Pro is the family’s full-size tier at 100% of the base text rate, twice the default. Same three jobs — reading, writing, storyboards — with more headroom on long, crowded episodes: it holds the storyboard’s strict format more reliably and keeps track of many characters and locations in one pass.
SceneMixer, Doubao Seed 2.1 Pro (read 2026-10-13)
Qwen-Image 3.0 is the tier every account starts on for character sheets, location images and prop images.
SceneMixer, Qwen-Image 3.0: the default image tier (read 2026-10-13)
5Sources
Dates come from the company that makes the model or the platform that serves it; menus come from the app, and both are linked on the calendar. Read 2026-09-22. What counts as a date is on sourcing. Nearby: Tier and model, Who publishes a date, After a withdrawal.