How many entries publish any date at all
Five of the sixteen entries carry a date. They come from three companies: a maker closing its own product, a maker running a deprecations table, and a platform publishing a retirement schedule for models it hosts. None of the three is an application a production buys from. As of 2026-09-12.
| Entry | What is published | Detail |
|---|---|---|
| Gemini API | Five video identifiers with shutdown dates | Described as the earliest possible |
| Microsoft Foundry | Two dated rows for a hosted model | Fixed, and stated as non-extendable |
| Sora | Two dates and a deletion policy | The only completed closure here |
| Amazon Bedrock | A period, and a floor before end-of-life | Dates arrive on the model card |
| Every application tracked | Nothing published | Eleven entries, 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 with the most dated rows first, then the rest.
1The dates live where software is written
Every entry with a published date sells to people who put a model identifier into code. Every entry selling a creative tool publishes none, 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.
2Two of the five dates have already passed
One maker's preview identifiers and one consumer product have both reached their dates. Between them they are the only evidence anybody has about how these endings actually finish.
Both resolved without a named successor, and one of them deleted stored material after an export window. That is a small sample and it is the sample.
3Eleven entries 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
4Sources
Dates come from the vendor that makes the model; menus come from the app, and both are linked on the calendar. Read 2026-09-12. What counts as a date is on sourcing. Nearby: How much notice, Your stored work, Notice clauses.