How many entries publish any date at all
Six of the sixteen entries show an announced end date. All of those dates come from three companies: OpenAI closing its own product, Google running a deprecations table, and Microsoft publishing a retirement schedule for a model it hosts. None of the three is an application a production buys from. From 3 source pages, read 2026-09-12 to 2026-09-22; no maker pays to be listed.
| Entry | What is published | Detail |
|---|---|---|
| Gemini API | Five Veo identifiers with shutdown dates | Google's own, described as the earliest possible |
| Microsoft Foundry | Two dated rows for a hosted model | Microsoft's own, stated as non-extendable |
| Adobe Firefly | A Veo line on its plan table | Google's date for earlier Veo versions, not its own |
| fal | A Veo line on its price list | Google's date for earlier Veo versions, not its own |
| invideo AI | Sora 2 on its model list | OpenAI's 24 September 2026 API date, not its own |
| Luma | A Veo line on its plan table | Google's date for earlier Veo versions, not its own |
| Amazon Bedrock | A period, and a floor before end-of-life | Dates arrive on each model card |
| The other nine entries | Nothing published | No date of any kind |
Inclusion rule. A date counts when the company making or serving the model published it on a page a reader can open. A date reported in coverage alone does not count. Order. Entries publishing dates of their own first, most dated rows first; then entries showing a maker's date, alphabetically; then the rest.
1The dates live where software is written
Every entry with a published date of its own sells to people who put a model identifier into code. Every entry selling a creative tool publishes none of its own, which is a pattern rather than a coincidence.
A notice is only useful to somebody who can act on it, and editing a version string is an action. Stopping work is not, which is roughly what a production two layers down can do.
2Four of the six dates on the calendar have already passed
Google's preview identifiers reached their date in November 2025 and OpenAI closed its consumer app in April 2026. Over the summer, Google's generally available identifiers and one sora-2 version hosted by Microsoft reached theirs.
Only the Microsoft retirement named a successor, a later version of the same model, and OpenAI's notice deletes stored material after an export window. That is a small sample and it is the sample.
3Twelve applications end a model by editing a page
For most of this market a model becomes unavailable because a line disappears from a priced page. No date precedes it, no notice follows, and the event is visible only to somebody comparing two dated readings.
That is what the data file is for, and why every row in it carries the day the page was read.
- sora-2 version 2025-12-0815 October 2026retirement date, no replacement named
- veo-3.0-generate-00130 June 2026veo-3.0-fast-generate-001 and veo-2.0-generate-001, shutdown date
- Sora API24 September 2026discontinued
- veo-3.0-generate-preview and veo-3.0-fast-generate-preview12 November 2025shutdown date
- sora-2 version 2025-10-0615 July 2026retirement date, replaced by sora-2 version 2025-12-08
4Production that outlasts a model
Model end dates touch “Who publishes a date”; SceneMixer's guides describe how its pipeline treats the models it runs:
The Seedance 2.0 tiers render segments up to 15 seconds; use a Seedance 2.5 or Wan tier for 30-second takes.
SceneMixer, Seedance 2.0 Fast — “Does Fast render 30-second takes?” (read 2026-10-13)
In the editor this tier is greyed out for such a segment; pick a Seedance 2.5 or Wan tier.
SceneMixer, Seedance 2.0 (standard tier) — “Can a segment longer than 15 seconds use this tier?” (read 2026-10-13)
5Sources
Dates come from the company that makes the model or the platform that serves it; menus come from the app, and both are linked on the calendar. Read 2026-09-22. What counts as a date is on sourcing. Nearby: After a withdrawal, Finished work, How much notice.