LLMSwaps

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

Notice period: the warning nobody has promised

No application in this register has published a notice period. Three platforms that host other companies models have: one commits to at least 60 days for a generally available model and 30 for a preview, one to six months or 45 days depending on the model, and one promises advance notice without attaching a number to it. As of 2026-09-12.

Warning owed beside warning givenThe left column is what a vendor has committed in advance to publish. The right column is what has actually happened, once, in the single retirement this register has been able to watch from announcement to close.PromisedHappenedBefore any announcementNothing published by anyone here—Between the two closures—About five months, onceRight to replace modelsStated on one pricing pageNo period attached to itEverywhere elseNo commitment madeNo observation yetWhat is owed, beside what has happened
Fig. 1 A right to replace models is written down on one page; a period before it is used is written down nowhere.
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 entryNotice periodWhat that leaves a production withWhat that leaves aproduction withAmazon BedrockAmazon Bedrock — Notice period: Six months or 45 days, stated per model in advanceAmazon Bedrock — What that leaves a production with: Plus a date before which end-of-life cannot arriveMicrosoft FoundryMicrosoft Foundry — Notice period: At least 60 days, or at least 30 for a preview modelMicrosoft Foundry — What that leaves a production with: Dates stated to be non-extendableGemini APIGemini API — Notice period: Advance notice promised, no number attachedGemini API — What that leaves a production with: The published date is the earliest a model might goSoraSora — Notice period: Nothing promised in advanceSora — What that leaves a production with: About five months elapsed between the two closuresLTX StudioLTX Studio — Notice period: No period, but the right to replace models is written downLTX Studio — What that leaves a production with: A statement that no period is owedSceneMixerSceneMixer — Notice period: Nothing published about notice before a tier changesSceneMixer — What that leaves a production with: Named tiers make a change visible afterwardsEvery other entryEvery other entry — Notice period: Nothing publishedEvery other entry — What that leaves a production with: No commitment in either direction
Fig. 2 Filled where the vendor has announced something in that column, hollow where it has not.
Entries with an announcementHow many entries carry an announcement in each column. Silence is the common case and is recorded as such.Entries with an announcementNotice period6 of 7What that leaves a production wi…What that leaves a production with5 of 7
Fig. 3 How many entries carry an announcement in each column. Silence is the common case and is recorded as such.
What each entry has committed to publish before the model behind it changes. Recorded 2026-09-12.
EntryNotice periodWhat that leaves a production with
Amazon BedrockSix months or 45 days, stated per model in advancePlus a date before which end-of-life cannot arrive
Microsoft FoundryAt least 60 days, or at least 30 for a preview modelDates stated to be non-extendable
Gemini APIAdvance notice promised, no number attachedThe published date is the earliest a model might go
SoraNothing promised in advanceAbout five months elapsed between the two closures
LTX StudioNo period, but the right to replace models is written downA statement that no period is owed
SceneMixerNothing published about notice before a tier changesNamed tiers make a change visible afterwards
Every other entryNothing publishedNo commitment in either direction

Inclusion rule. A cell is filled from a page where the seller or the maker states what warning it will give. An interval observed after the fact is recorded in the detail column, never as a commitment. Order. Entries publishing a period in time units first, then the rest.

1Given is not the same as promised

One vendor left roughly five months between closing a consumer product and closing the interface behind it. That is a fact about a single retirement, recorded with the announcement it came from. It is not a commitment, and nothing in that notice suggests the interval was policy rather than a schedule that happened to land that way. A platform policy is the opposite: a number published before anything is scheduled, which is why the two are kept in different columns here.

Reading it as a norm is the error this column exists to prevent. One observation sets a floor on what is possible and says nothing about what is usual. The next retirement will either match it or show that it never meant anything.

2A clause about replacing models is a different kind of statement

One pricing page states that the models on offer may be updated, modified or replaced, and that continued availability of any particular model is not guaranteed. That is not a notice period; it is the reverse, an advance statement that no period is owed. It is recorded anyway, because a written statement can be designed around and a silence cannot.

A reader who knows the right exists will plan for a swap. A reader looking at a page that says nothing assumes a stability that was never on offer, and that is the more expensive of the two mistakes.

3Where this column does get filled, and by whom

Three entries state a period in time units, and all three sell to developers rather than to productions. Amazon Bedrock publishes a legacy window of six months or 45 days per model, plus a date before which end-of-life cannot happen at all. Microsoft Foundry publishes 60 days for a generally available model and 30 for a preview, and adds that dates are not extendable. The Gemini API promises advance notice and never counts it, which this register treats as unfilled.

That pattern is the finding rather than the numbers. A notice period appears wherever the buyer is expected to have written code against a named version, and disappears wherever the product is sold as a creative tool. A production reaching a model through an application is therefore two layers away from the only party that has committed to warn anybody, and the commitment does not travel down the chain.

4This column, entry by entry

The notice period column read one entry at a time, wherever that entry has published something here or falls silent in a way the others do not. Ordinary blanks stay on the table above.

  • Microsoft Foundry — 60 days for a live model, 30 for a preview, and dates that cannot be moved
  • Amazon Bedrock — a legacy window of six months or 45 days, stated on the model card in advance
  • Gemini API — notice promised in words and never converted into a number of days
  • LTX Studio — a written right to replace models, which is a statement that no period is owed
  • SceneMixer — nothing published about warning, but a tier named precisely enough to audit afterwards
  • Runway — a credit conversion table that can be edited, with nothing published about warning
  • Sora — about five months between two closures, which is an interval given rather than promised
  • Notice before a tier changes
    No date announced (as of 2026-09-12)nothing publishedSceneMixer, price list / recorded 2026-09-12
  • Published notice
    The pricing page reserves the right to update, modify or replace available models and does not guarantee continued availability of any specific modelthe only one of its kind hereLTX Studio, pricing / recorded 2026-09-12
  • Sora API
    24 September 2026discontinuedOpenAI Help Center / recorded 2026-09-12
  • Notice for a generally available model
    At least 60 days before retirementsent to subscriptions with active deploymentsMicrosoft Foundry, lifecycle and support policy / recorded 2026-09-22
  • Notice for a preview model
    At least 30 days before retirementwhich is the stage sora-2 sits inMicrosoft Foundry, lifecycle and support policy / recorded 2026-09-22
  • Legacy period
    Six months or 45 days, stated on each model cardwhich is the notice given before end-of-lifeAmazon Bedrock, model lifecycle / recorded 2026-09-22
  • How many days of advance notice
    No date announced (as of 2026-09-12)promised but never countedGoogle, Gemini deprecations / recorded 2026-09-22

5Sources

Values come from the page the entry is read on: vendor announcements for endings, app pages for menus, both linked from the calendar. What counts as a value is on sourcing. Read 2026-09-12. Other fields: Default tier, Lifecycle states. All of them: the field list.