What happens when the model you built on goes away

LLMSwaps records announced end dates for generative video models and which products still carry them. Sixteen entries are tracked. Three companies have published a date for a video model: OpenAI, Google and Microsoft. Not one of them is an application a production buys from. As of 2026-09-22.

Inclusion rule. Products, platforms and publishers whose own pages name a model. Anything that publishes only house tier names is recorded as naming none and does not get a row. Order. Alphabetical by entry.

1What is recorded here

Two kinds of page, kept apart on purpose. A model page records what the vendor that makes the model has said about its life. An app page records the models an app names on its own pages. They go out of step, and the gap between them is the thing worth knowing: an app can still be advertising a model whose maker has already announced the end.

Only vendor announcements count as dates. Press coverage does not, and a model vanishing from a reseller's menu does not. A blank in the date column means the vendor has not said anything, which is a different thing from a commitment to keep it running.

2Start here

• The calendar — every announced end date, in one chronological list.
• Sora — app ended in April, API ends 24 September, stored work deleted after.
• SceneMixer — five tiers, each naming its model and version.
• LTX Studio — the one vendor that writes the replacement risk into its pricing page.
• invideo AI — six vendors aggregated, Sora 2 still on the list.
• Kling AI — two generations live at once on one plan.
• Pika — one house model named across every plan.
• Microsoft Foundry — dated sora-2 rows, and the first notice period in this register counted in days.
• Amazon Bedrock — three lifecycle states, months of notice, and no automatic migration.
• Gemini API — five Veo identifiers with shutdown dates that mean not before rather than on.
• Wan-AI — published weights, where a withdrawal cannot reach the copy you hold.
• All entries — the other seven products read this round, from Runway to Vidu.
• Sourcing — what counts as a date, and what is out of scope.

3Questions the register answers

4Explainers

How to live with models that get switched off: the vocabulary, the bookkeeping, and the decisions that have to be made before an announcement rather than after. Dates themselves live on the calendar.

• Pinning a version — what pinning a model version protects you from, and what it does not.
• After a swap — what to do when the model under a product changes and the look moves with it.
• Surviving a retirement — what to do before a model you build on is switched off.
• Deprecation words — sunset, deprecated, legacy, end-of-life: what each usually signals.

• How much warning anyone gives — about five months, from a sample of one.
• What happens to stored work — a download window, then deletion.
• Who reserves the right to change the menu — one clause, no notice period.
• An aggregator inherits another company’s calendar — six makers, six schedules.
• One model against several — both stable, in different ways.
• Why naming the version matters — it is what makes a retirement visible.
• What a blank in the date column means — about announcements, not schedules.

5Why this matters for a series

A single clip does not care which model made it. A forty-episode series does: the cast, the look and the pacing were all established under one model, and a swap partway through is a continuity problem that no amount of prompt work fixes cleanly. The question is not whether a model is good but whether it will still be there in six months. Three companies tracked here have published something a production could plan against, and none of them sells to productions.

It is also why the app pages here list models rather than features. A feature list tells a reader what an app can do this month; a model list tells them whose roadmap they have quietly signed up to. An app that carries one model of its own has one schedule to manage, and an app that aggregates six vendors has six, none of which it controls.

LLMSwaps records dates announced by vendors. It does not predict retirements and it does not recommend migrations.

6What the notices cover

Apps record which engine is named today, models record the dates a vendor has committed to, the field pages say what each column of the register holds, and the data page is the notices as a file.

• Data — The recorded model names and lifecycle dates as a comma-separated file, each row…
• Apps — A notice per app…
• Models — Lifecycle notices for generative video models…
• Fields — Every entry here is read along the same list of fields…
• Questions — Questions about which model an app runs and what happens when it is retired, answered…
• Learn — Explainers on model lifecycles…
• Side by side — Pairs of entries whose published answers on one column of the register point opposite…
• Terms — Short definitions for the words that appear in retirement notices and in this register,…