LLMSwaps

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

A right to replace against a period owed

These two entries publish opposite sentences about the same question. One reserves the right to replace models and guarantees nothing about any of them. The other publishes a period before end-of-life, on the model itself, before anything is scheduled. Both sell access to models they mostly did not make. From 2 source pages, read 2026-09-12 to 2026-09-22; no maker pays to be listed.

What each entry commits to about a model leaving. Recorded 2026-09-22.
On this pointLTX StudioAmazon Bedrock
What is committedNothing about continued availabilityA period of six months or 45 days
Where it is statedA footnote under the plan tableOn the model card, in advance
Who the page is written forA buyer choosing a subscriptionA developer choosing an identifier
Does it name a successorNo, and an older house line is soldNo, and migration is stated as yours
What happens at the endNot describedRemoved from all regions, requests fail

Inclusion rule. Both cells on a row come from the entry's own published pages: a priced page for the application, a lifecycle page for the platform. Order. What is committed first, then who it is written for.

1The audience explains the difference

One page is selling a subscription to people who will judge it on features. The other is documenting an identifier for people who will hard-code it into software. The second audience asks for a period and the first does not.

That pattern holds across the whole register. Every entry that publishes a figure sells to developers, and every entry that sells a creative tool publishes none.

2A clause is not the opposite of nothing

Read against a page that commits to months, the clause looks like the worst possible disclosure. Read against the eleven applications that say nothing at all, it is the best in its class: it tells a buyer exactly what they are not getting.

So the comparison has three positions rather than two, and the clause sits in the middle rather than at the bottom. The reading for that entry sets out why a written right beats a silence.

Three positions, not twoRead against a page committing to months, a clause reserving the right to replace models looks like the worst disclosure here. Read against the eleven applications that say nothing at all, it is the best in its class.What a page can say about a model leavingA period owedSix months or 45 days, on the model card, before anything isscheduled.A right reservedNo period owed, and the buyer is told so in writing on thepriced page.SilenceEleven applications. A reader assumes a stability nobodyoffered.The audience explains the difference: developers ask for a figure, buyers do not
Fig. 1 The clause sits in the middle rather than at the bottom, which is why the register records it as a statement.

3Neither names where to go

The platform states plainly that migration will not happen automatically and names no successor. The application keeps an older house generation on sale without describing it as one.

A period is worth more than a foothold and neither is worth as much as a destination. Two columns of this register exist because those are three separate commitments, and almost nobody makes all three.

4The same question, put to a third entry

What SceneMixer publishes on this column, beside LTX Studio and Amazon Bedrock. 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.

  • Models carried
    LTX-2.5 and LTX-2.3 in house, plus Veo 3.1 in three variants and Kling 2.6 Pro and 3.0 Prolicensed models includedLTX Studio, pricing / recorded 2026-09-12
  • What happens at end-of-life
    After the end-of-life date the model is removed from all AWS Regions and requests made to it failAmazon Bedrock, model lifecycle / recorded 2026-09-22

5Sources

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