LLMSwaps

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

Model lifecycles, from announcement to withdrawal

A lifecycle notice collects the dates a vendor has published about one model: when it arrived, when it was marked for retirement, and when access actually ends. As of 2026-09-12.

The four dates a model lifecycle can have, and the one usually missingA lifecycle has an announcement, a successor, a deprecation wording and a shutdown date. Vendors reliably publish the first three. The shutdown date is the one a customer needs in order to plan, and it is the one most often left open.AnnouncedThe modelappears,usually with alaunch post anda versionstring.Months laterSuccessor namedA newer modelis launched.The older oneis still fullyavailable.Then wordingchangesDeprecatedLegacy,deprecated orno longerrecommended.Access usuallycontinues.And thenShutdownThe date accessactually ends.Frequentlyneverpublished.
Fig. 1 A deprecation without a shutdown date is a strong hint and no planning information, and the notices say so in those terms.

Retirement announcements are written to be defensible rather than clear. A model may be legacy on one page, deprecated on another, and still fully available through an interface for months afterwards. A notice records each wording separately with the date it appeared.

The end date is the part that matters commercially and the part most often absent. A vendor that announces a successor without announcing a shutdown has given the industry a strong hint and no planning information at all, and the notice says exactly that.

Only one model carries a full lifecycle notice today. The calendar collects every announced date across the register, which is the faster way in when the question is when rather than which.

1The notices

  • Sora — The announced end dates for Sora's app and its API, what happens to work stored inside it, and whether any replacement model is named.

2One model, and every entry carrying it

  • Veo 3.1 — Four entries in this register name this line on their own pages, in four different shapes, and none of them publishes a date for it.
  • Veo 3 — This generation is both purchasable through a platform here and listed with a shutdown date on its maker's deprecations page, which is a rare combination.
  • Veo 3 preview lines — Two preview identifiers carry a shutdown date that has already passed, and no entry here names them.
  • Kling 3.0 — Six entries name this line, including the maker's own membership.
  • Kling 2.5 Turbo — Two entries still name this earlier line, one gated a tier below the current model and one priced individually.
  • MiniMax H3 — Five entries name this line, including the maker's own page and a product that splits it into a standard and a fast tier.
  • Wan — Four entries carry this family and no two of them carry the same version, including one that publishes the weights themselves rather than an endpoint.
  • Sora 2 — One application still names this line and one platform hosts dated versions of it, while its maker has announced that its own interface closes.
  • Single-carrier lines — Eight house lines here appear on exactly one entry's pages.
  • Lines on several menus — Six lines here are carried by two or more entries.

A model earns a lifecycle notice when a vendor has published at least two dates about it.

Other notices: Apps, Fields, Side by side, Questions, Terms, Learn, Data. Where each line comes from is set out on the sourcing page.