LLMSwaps

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

Stored work: what a shutdown does to the files

The one shutdown documented in this register ended storage as well as service: data associated with the product is deleted after a final export window passes. Nobody else has announced an ending, so nobody else has had to say what happens to the material inside. As of 2026-09-12.

The two deadlines inside one noticeA shutdown notice carries a date for the service and, usually further down and in one line, a shorter one for the material kept inside it. The second is the deadline a team with an archive is actually working to.Shutdown announcedThe notice ends theservice and, in oneline, the storagewith it.A window opensExport windowMaterial can bedownloaded, on aperiod shared witheveryone elseleaving.Window closesDeletionData associated withthe product isdeleted. Nothingfurther is offered.
Fig. 1 One retirement here has run this course end to end, and the material was deleted at the end of it.
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 entryStored workWhat that leaves a production withWhat that leaves aproduction withSoraSora — Stored work: Deleted after any final export windowSora — What that leaves a production with: A download period comes first, then nothingSceneMixerSceneMixer — Stored work: Nothing publishedSceneMixer — What that leaves a production with: Storage terms sit apart from the tier listLTX StudioLTX Studio — Stored work: Nothing publishedLTX Studio — What that leaves a production with: The published clause covers models, not materialEvery other entryEvery other entry — Stored work: Nothing publishedEvery other entry — What that leaves a production with: No ending announced, so no disposal stated
Fig. 2 Filled where the vendor has announced something in that column, hollow where it has not.
What each entry has published about material stored inside the product. Recorded 2026-09-12.
EntryStored workWhat that leaves a production with
SoraDeleted after any final export windowA download period comes first, then nothing
SceneMixerNothing publishedStorage terms sit apart from the tier list
LTX StudioNothing publishedThe published clause covers models, not material
Every other entryNothing publishedNo ending announced, so no disposal stated

Inclusion rule. A cell is filled from a shutdown notice that says what becomes of stored material. Ordinary account-closure terms are not a shutdown notice and do not fill one. Order. The announced shutdown first, then the apps whose pages were read for this column.

1A shutdown ends the library as well as the tool

The announcement that ended a model here also ended the place its output lived. Data associated with the product is deleted once a final export window passes, which makes the storage deadline a second date, earlier in practice than the one everybody quoted and carried in a single line near the end of the notice.

A team that treated the product as a tool lost a tool. A team that treated it as an archive lost the archive. Those are different sizes of problem, the notice does not distinguish between them, and so this column does.

2Mostly empty, and still worth keeping

No other entry has announced an ending, so no other entry has been put in a position to say what happens to the material inside it. That leaves one filled cell and a run of blanks, and the blanks are not a promise that files stay where they are. They record that the question has not been asked of anyone in public.

The useful reading is comparative. The single documented case resolved as deletion after a window, which is the harshest outcome a reader would have guessed, and therefore the one worth assuming until some app publishes something kinder.

3Getting the files out is the part a register cannot do

Recording what a vendor published is the whole job here. Moving delivered files off a vendor's account and onto storage somebody else controls is work that has to happen before an announcement, because the export window in the documented case was measured in weeks and shared with everyone else in the same position.

So the column is better read as a prompt than as an inventory. If the cell for a product you depend on is blank, that is not a finding about the product. It is a question still open while there is time to act on the answer.

4This column, entry by entry

The stored work 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.

  • Sora — the register's one filled cell: deletion once a final export window passes
  • Microsoft Foundry — requests return 410 Gone after the date, and nothing is said about material
  • Amazon Bedrock — the model leaves every region and requests fail; material is the customer's own problem
  • Gemini API — output is returned per call, so a shutdown removes the capability and reaches no files
  • Wan-AI — the files were never on the publisher's disk, so a withdrawal cannot reach them
  • fal — a meter per output unit rather than a library, so delivery is the whole relationship
  • LTX Studio — the published clause covers models, not the material made with them
  • SceneMixer — the price list names models precisely and says nothing about what happens to the work
  • What happens to the work
    Data associated with Sora is deleted after any final export window passesOpenAI Help Center / recorded 2026-09-12
  • Sora web and app
    26 April 2026discontinuedOpenAI Help Center / recorded 2026-09-12
  • Sora API
    24 September 2026discontinuedOpenAI Help Center / 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: Notice period, Default tier. All of them: the field list.