LLMSwaps

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

An ending announced without a destination

The Sora discontinuation notice is precise about dates and silent about succession. Two closures are dated, stored material is covered, and no replacement model appears anywhere in it. The register records that as an absence rather than inferring the maker's newer video work as the route. 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 entryWhat Sora publishesWhat SorapublishesWhat that leaves openWhat that leavesopenIs a replacement model namedIs a replacement model named — What Sora publishes: No replacement is namedIs a replacement model named — What that leaves open: Not in the notice and not on the sunset pageIs a migration route describedIs a migration route described — What Sora publishes: None is describedIs a migration route described — What that leaves open: Export is covered; re-generation is notDoes an older version remainDoes an older version remain — What Sora publishes: No earlier generation is left reachableDoes an older version remain — What that leaves open: Both surfaces close, five months apartWhat a reader can act onWhat a reader can act on — What Sora publishes: The dates and the export windowWhat a reader can act on — What that leaves open: Which is bookkeeping rather than migration
Fig. 1 Filled where the vendor has announced something in that column, hollow where it has not.
What the notice settles about where the work goes next. Recorded 2026-09-22.
What the page is askedWhat Sora publishesWhat that leaves open
Is a replacement model namedNo replacement is namedNot in the notice and not on the sunset page
Is a migration route describedNone is describedExport is covered; re-generation is not
Does an older version remainNo earlier generation is left reachableBoth surfaces close, five months apart
What a reader can act onThe dates and the export windowWhich is bookkeeping rather than migration

Inclusion rule. Read from the vendor's own discontinuation article. A newer model from the same maker does not fill this cell unless the notice names it as the successor. Order. The absence first, then what the notice does provide.

1A date without a destination is half a plan

Five months of warning sounds generous until a team tries to use it. The work that warning is for is testing whatever comes next, and that work cannot start until somebody decides what next is.

So the notice hands its readers the easier half of the problem. Stopping on time is arithmetic; choosing a successor and re-establishing a look on it is the expensive part, and nothing in the announcement reduces it.

Warning without a destination halves its valueA runway is useful because it can be spent testing a successor. When the notice names none, the runway cannot be spent until somebody picks a candidate, and picking wrong spends it twice.Date and successorDate aloneWeek oneStart testing the named modelDecide what to testWhat you learnWhether prompts carry overWhether the guess was rightIf it goes badlyA known problem, with time leftStart again, with less timePublished hereNothingTwo dates and a deletion policyWhy succession is a separate column from the calendar
Fig. 2 Recorded as an absence rather than filled with the maker's newer work, which nobody published as the route.

2Why the obvious guess is still a guess

Every reader will assume the maker's newer video work is where this goes, and most will be right. Writing that into the register would make the cell look complete while resting on nobody's statement, which is the trade refused across every column here.

The cost of guessing is not abstract. A team that migrated to an assumed successor and found the pricing, the interface or the region coverage different has spent its runway on the wrong test.

3The absence is what the column exists to hold

This register has one retirement with published dates, and that retirement named no successor. That single data point is the whole argument for keeping succession in its own column rather than folding it into the calendar.

A calendar entry answers when. It cannot say that the ending arrived without a destination, and a reader who saw only the date would reasonably assume one existed.

  • Named replacement model
    No date announced (as of 2026-09-12)none in the announcementOpenAI Help Center / recorded 2026-09-12
  • Sora API
    24 September 2026discontinuedOpenAI Help Center / recorded 2026-09-12
  • What happens to the work
    Data associated with Sora is deleted after any final export window passesOpenAI Help Center / recorded 2026-09-12

4Sources

Read from the discontinuation article on help.openai.com, 2026-09-22. The whole entry is on Sora, and the column it sits in is on Named replacement. Same column, other entries: Gemini API, Amazon Bedrock.