LLMSwaps

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

Sora 2: two menus and a closing door

One application still names this line on its public model list. One platform hosts versions of it with dated retirements of their own. Meanwhile the maker has announced that its own interface for it is discontinued, which is the tension this register was built to record. From 3 source pages, read 2026-09-12 to 2026-09-22; no maker pays to be listed.

Where this line is named, and what each of those pages says about its end. Recorded 2026-09-22.
EntryHow it appears thereAnnounced end for this line
Microsoft FoundryTwo dated versions on a retirement schedule15 July and 15 October 2026
invideo AINamed on the published model list, no version given24 September 2026

Inclusion rule. An entry appears when it names this line on a page a reader can reach without an account, or when it publishes a lifecycle date for a version of it. Order. Entries publishing their own dates first, then the reseller.

1Three companies, three different endings

The maker says its interface closes on one date. A hosting platform publishes two earlier dates for its own versions. An application still lists the line with no date at all. All three statements are current.

None of them contradicts the others, because they are about different surfaces. Reading them together is the only way to see that the same model is ending three times on three schedules.

The same model ending three times on three schedulesThe maker says its own interface closes on one date. A hosting platform publishes two earlier dates for versions it serves. An application still lists the line with no date at all. None of the three contradicts the others, because each is about a different surface.Three dates, three companies, one modelA hostedversionretires15 July 2026Set by theplatform, witha successornamed in therow.The maker'sinterfacecloses24 September2026Announced bythe maker,with nosuccessornamed.The secondhosted versionretires15 October2026Also theplatform'sdate, and noreplacementbeside it.An application still names the line with no date at all
Fig. 1 Reading them together is the only way to see that one model is ending on three schedules at once.

2A hosted version has its own lifecycle

The platform's two rows are versions it serves, with dates it set. So a production reaching this line through that platform is not on the maker's schedule at all, and the earlier of the platform's dates comes first.

That is the clearest example in the register of a hosting layer owning a retirement. The successor reading covers the one row here that names what follows it.

3A menu that lags an announcement

The application's list still names this line while the maker's interface is scheduled to close. Menus are marketing pages and they lag; the useful habit is checking the maker rather than the reseller.

The register keeps both statements side by side without resolving them, because resolving would mean predicting what the application does next. That prediction is exactly what sourcing rules out.

4A pipeline across model versions

Model end dates touch “Sora 2”; SceneMixer's guides describe how its pipeline treats the models it runs:

Recommended is the badge on the tier the site suggests for most character sheets; the default for new accounts stays the cheaper tier.

SceneMixer, Qwen-Image 3.0 Pro: the recommended tier — “Is Recommended the same as default?” (read 2026-10-13)

SceneMixer writes dialogue into the script analysis, assigns each line to a shot with a speaker and a short delivery note, and the video model performs it — picture and audio generated together, so the mouth forms that sentence in the language you chose.

SceneMixer, AI Dialogue Generator (read 2026-10-13)

5Sources

Each row is read from the page that entry publishes itself, 2026-09-22, and any date comes from whoever makes the model. Every announced date is on the calendar. Other models read this way: Single-carrier lines, Lines on several menus.