LLMSwaps

Announced end dates for video models, and which apps still carry them

Published stages against an editable table

One entry publishes stages, and which stage a model is in decides how much notice its retirement owes. The other publishes a credit conversion table where a model's disappearance is an edit with no stage, no date and nothing distinguishing it from a price revision. From 2 source pages, read 2026-09-22; no maker pays to be listed.

What each page says, point by pointFilled where the entry's own page addresses that point, hollow where the page is silent on it.What each page says, point by pointMicrosoft FoundryRunwayIs a condition publishedIs a condition published — Microsoft Foundry: Preview or generally available, then retiredIs a condition published — Runway: Not stated for any modelDoes the condition carry consequencesDoes the condition carry consequences — Microsoft Foundry: Yes, it sets the notice owedDoes the condition carry consequences — Runway: Not applicableWhat a change looks likeWhat a change looks like — Microsoft Foundry: A dated row on a scheduleWhat a change looks like — Runway: A different conversion tableCan a change be datedCan a change be dated — Microsoft Foundry: Yes, in advanceCan a change be dated — Runway: Only by the reader's own two readingsAre licensed models presentAre licensed models present — Microsoft Foundry: Yes, hosted from other makersAre licensed models present — Runway: Yes, unmarked among house lines
Fig. 1 Filled where the entry's own page addresses that point, hollow where the page is silent on it.
What each page publishes about a model's condition. Recorded 2026-09-22.
On this pointMicrosoft FoundryRunway
Is a condition publishedPreview or generally available, then retiredNot stated for any model
Does the condition carry consequencesYes, it sets the notice owedNot applicable
What a change looks likeA dated row on a scheduleA different conversion table
Can a change be datedYes, in advanceOnly by the reader's own two readings
Are licensed models presentYes, hosted from other makersYes, unmarked among house lines

Inclusion rule. Both cells on a row come from the entry's own published pages: a lifecycle page for the platform, a priced page for the application. Order. Whether a condition exists first, then what a change looks like.

1A stage with consequences is the strongest form here

Most state words in this field mean only that a vendor reserves some freedom. Where a stage decides a number of days, the label becomes something a production can act on before anything is scheduled.

The comparison entry has no label at all, so there is no condition to read and no consequence attached to one. Its page is more detailed about prices and silent about lifecycle.

A resale layer can publish lifecycle informationNeither entry makes everything it sells. One hosts other makers' models with its own dated schedule on top; the other lists them in a conversion table with no schedule anywhere. So reselling is not an excuse for silence.What a reseller can publish about a model it did not buildStages with consequencesPreview or generally available, deciding thirty or sixty days ofnotice.A dated scheduleRows naming hosted versions, with dates set by the reselleritself.A conversion tableEvery model priced, no condition published, and a line simplystops being listed.Twelve of sixteen entries end a line by editing a page
Fig. 2 One page is more detailed about prices and silent about lifecycle; the other is the reverse.

2Both resell other companies' models

Neither entry makes everything it sells. One hosts other makers' models with its own dated schedule on top; the other lists them in a conversion table with no schedule anywhere.

So the resale layer can publish lifecycle information, and one of these two does. That removes the excuse that a reseller has nothing to say about a model it did not build.

3What a reader can watch on each

On the first, a schedule page with dated rows and a policy behind them. On the second, a conversion table read twice, where a rate change and a retirement look the same.

The ending early reading covers the edit as a mechanism. It is how twelve of the sixteen entries here actually end a model line.

4The same question, put to a third entry

What SceneMixer publishes on this column, beside Microsoft Foundry and Runway. Recorded 2026-10-13.
On this pointSceneMixerSource
A tier briefly unavailableA tier that is temporarily unavailable is hidden from the tier list rather than offered and refusedSceneMixer, withdrawn tier guide
A tier that has been retiredA segment submitted on a retired tier is refused with a message before anything is held, and the selector no longer lists that tierSceneMixer, tier no longer exists guide

Inclusion rule. SceneMixer's own statements that bear on the column this pair was chosen for. Order. The statement closest to the column first.

All of its readings are on the SceneMixer entry.

  • sora-2 version 2025-12-08
    15 October 2026retirement date, no replacement namedMicrosoft Foundry, retirement schedule / recorded 2026-09-22
  • Models carried
    Gen-4.5 and Aleph 2.0 in house, plus Kling 3.0 and three Seedance variantsnamed beside credit conversionsRunway, pricing page / recorded 2026-09-22

5Sources

Both readings come from the pages the entries publish themselves: Microsoft Foundry and Runway, read 2026-09-22. The column being compared is Lifecycle states. Other pairs: The Gemini API and LTX Studio, Foundry and Bedrock on states.