LLMSwaps

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

Named replacement: the column that stays empty

A retirement announcement can name what to move to. The announcement in this register does not, so the column records an absence rather than a successor. An older generation left on sale by another app is a place to stand, not a named replacement. As of 2026-09-12.

Where a successor comes fromA replacement is recorded when the announcement that ended the model names it. A newer version from the same maker existing is not a statement about continuity and does not fill the cell.Does the notice that ends a model name what follows it?It names oneA destinationTesting can start before the date landsIt names nothingRecorded emptyFinding a successor is left to thecustomerFilled from the notice, never from the product line
Fig. 1 Guessing the successor would fill every cell on this page and make none of them checkable against anything.
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 entryNamed replacementWhat that leaves a production withWhat that leaves aproduction withSoraSora — Named replacement: None in the announcementSora — What that leaves a production with: Destination left to the customerLTX StudioLTX Studio — Named replacement: Not stated, older house generation still soldLTX Studio — What that leaves a production with: A version to stay on, not a successorKling AIKling AI — Named replacement: Not stated, both generations on one planKling AI — What that leaves a production with: The same shape, reached by the plan rather than a noticeEvery other entryEvery other entry — Named replacement: Nothing publishedEvery other entry — What that leaves a production with: No ending announced, so nothing to succeed
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 announcementNamed replacement1 of 4What that leaves a production wi…What that leaves a production with3 of 4
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 published about the model that would take over. Recorded 2026-09-12.
EntryNamed replacementWhat that leaves a production with
SoraNone in the announcementDestination left to the customer
LTX StudioNot stated, older house generation still soldA version to stay on, not a successor
Kling AINot stated, both generations on one planThe same shape, reached by the plan rather than a notice
Every other entryNothing publishedNo ending announced, so nothing to succeed

Inclusion rule. One row per entry whose vendor or app has published something about what follows the model it names. A newer version existing is not a published statement and does not fill a cell. Order. The announced retirement first, then apps keeping an older generation sold, then the rest.

1Why the successor is a separate fact from the date

A shutdown date tells a production when work has to stop. It says nothing about where that work goes next, and the two pieces of information arrive from different places or, far more often, only one of them arrives at all. Keeping them in separate columns is what lets this register say that an ending has been announced and, in the same breath, that no destination has been.

Collapsing the two would read as reassurance. A notice with a date and no successor ends something without starting anything, and a reader who sees the date alone will assume a replacement exists, because in most other industries a withdrawal arrives with one.

2An older generation still on sale is not a named replacement

Two apps tracked here keep a previous generation selectable beside the current one. That gives a production somewhere to stand and is worth recording, but it is a menu arrangement rather than a statement about continuity. Nobody has said the older version will still be there next quarter, and nobody has said the newer one is what it becomes.

The distinction bites when the older option disappears. A named replacement gives a reader something to plan against; a second line on a plan page gives them something to watch. This column records the first and leaves the second to the app pages, where menus belong.

3What this column will not be filled in with

It would be easy to write the obvious successor into every empty cell. A newer version from the same maker is usually what people move to, and guessing would make the register look finished. It would also make every cell unverifiable, which is the trade refused everywhere else on this site.

So the rule stays narrow. A value goes in when the notice that announced the ending also names what follows it. Everything else stays empty, and an empty cell here reads as a vendor who closed something without telling anyone where to go.

4This column, entry by entry

The named replacement 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 — one dated row names its successor, and it is a later version of the same model
  • Sora — the register's one real retirement, announced without naming anything to move to
  • Gemini API — three video identifiers shut down on one date, with no successor named beside any of them
  • Amazon Bedrock — states outright that migration will not happen automatically, and names no destination
  • LTX Studio — keeps a previous house generation on sale, which is a foothold rather than a successor
  • Kling AI — two generations on one plan, with neither marked as the route off the other
  • Luma — two house generations on one table, with the licensed half belonging to six other makers
  • Wan-AI — publishes the weights, so a withdrawal cannot reach a copy already downloaded
  • Pika — one house model on every plan, so there is no older line to fall back to
  • PixVerse — promotes one house version and says nothing at all about the versions before it
  • Vidu — a current generation and a real-time line on the page, with earlier generations unaddressed
  • Hailuo AI — one generation promoted on the home page, with no back catalogue mentioned
  • invideo AI — succession is decided by the six makers whose models it aggregates, not by the app
  • Adobe Firefly — partner models are gated by tier, so a replacement can arrive as a plan change
  • Named replacement model
    No date announced (as of 2026-09-12)none in the announcementOpenAI Help Center / recorded 2026-09-12
  • 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
  • Models carried
    Kling 3.0 and 3.0 Omni, with VIDEO 2.6 still listed as a plan benefittwo generations live at onceKling AI, membership plans / recorded 2026-09-12

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: Stored work, Notice period. All of them: the field list.