LLMSwaps

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

A policy written in advance against one interval

One of these entries published a rule about every future retirement before it scheduled any. The other announced two dates about five months apart and never presented the gap as a commitment. Both are facts about warning, and only one of them supports a plan for the next retirement. As of 2026-09-22.

What has been announced, entry by entryFilled where the vendor has announced something in that column, hollow where it has not.What has been announced, entry by entryMicrosoft FoundrySoraKind of statementKind of statement — Microsoft Foundry: A published policy, before any scheduleKind of statement — Sora: An interval observed after the factApplies toApplies to — Microsoft Foundry: Every model the platform retiresApplies to — Sora: One retirement, by one companyLengthLength — Microsoft Foundry: Thirty days at preview, sixty when liveLength — Sora: About five months between two closuresCan it be relied on next ti…Can it be relied on next timeCan it be relied on next time — Microsoft Foundry: Yes, it is a published ruleCan it be relied on next time — Sora: No, nothing calls it policyIs a successor namedIs a successor named — Microsoft Foundry: For one of two dated rowsIs a successor named — Sora: No replacement is named
Fig. 1 Filled where the vendor has announced something in that column, hollow where it has not.
What each entry established about warning before a model goes. Recorded 2026-09-22.
On this pointMicrosoft FoundrySora
Kind of statementA published policy, before any scheduleAn interval observed after the fact
Applies toEvery model the platform retiresOne retirement, by one company
LengthThirty days at preview, sixty when liveAbout five months between two closures
Can it be relied on next timeYes, it is a published ruleNo, nothing calls it policy
Is a successor namedFor one of two dated rowsNo replacement is named

Inclusion rule. Both cells on a row come from the entry's own published pages. An interval between two dated events is recorded as an observation and never as a commitment. Order. Kind of statement first, then length, then what follows.

1The longer interval is the weaker evidence

Five months against thirty days looks decisive until you ask what each number is. One is a rule that will apply to the next retirement; the other is a measurement of the only retirement that has happened.

A sample of one sets a floor on what is possible and says nothing about what is usual. The next announcement from that company will either match it or show that the number never meant anything.

2Why the register keeps them in separate columns

Collapsing an observation into a commitment is the most tempting error in this field, because it produces a tidier table. It also produces a table nobody can act on, since the figures in it would mean different things row by row.

So the interval lives in the detail column of the notice period table and the policy lives in the value column. A reader can see both and tell which is which.

A rule for next time against a measurement of last timeFive months against thirty days looks decisive until you ask what each number is. One is a rule that will apply to the next retirement; the other is a measurement of the only retirement that has happened.A published policyAn observed intervalWrittenBefore any schedule existedVisible only afterwardsCoversEvery future retirementOne retirement, onceLengthThirty days at preview stageAbout five monthsUsable next timeYesNoCollapsing the second into the first is the most tempting error in this field
Fig. 2 A sample of one sets a floor on what is possible and says nothing about what is usual.

3Neither entry names a successor

One names a later version of the same model for a single dated row. The other names nothing at all. So a runway of either length leads to a destination the customer has to choose.

That is the shared weakness and it matters more than the difference in length. A migration cannot begin until somebody picks a target, which the succession reading sets out.

4Sources

Both readings come from the pages the entries publish themselves: Microsoft Foundry and Sora, read 2026-09-22. The column being compared is Notice period. Other pairs: LTX Studio and SceneMixer, LTX Studio and Bedrock.