How many conditions an entry admits a model can be in

Three on one platform, two stages on another, and none on the twelve applications. Where no condition is published, a model has only two states from outside: it answers, or it does not. Everything a production would want to plan around sits in between those two. As of 2026-09-12.

Fig. 1 Filled where the vendor has announced something in that column, hollow where it has not.

How many conditions each entry publishes for a model on its way out. Recorded 2026-09-12.
Entry	What is published	Detail
Amazon Bedrock	Three, named and readable through the interface	A period attached to the middle one
Microsoft Foundry	Two stages, plus retired	The stage decides the notice owed
Gemini API	None in words; a listing serves instead	Being on the table is the condition
Sora	One word, applied to two surfaces	No intermediate state was published
Every application tracked	None	On the menu, or off it

Inclusion rule. A condition counts when the entry publishes the label itself. A marketing word such as new or classic is not a lifecycle state. Order. Most conditions first, then the rest.

1A middle condition is what makes a removal plannable

Available and gone are the two conditions any model has from outside unless somebody names a third. Naming one with a period attached turns a removal into something with a beginning, which is where every useful action happens.

It also concentrates the sharp clauses. The one window published here contains the sentence allowing access to end after a fortnight of disuse.

Fig. 2 Promotion order is not a state: it says which lines are being sold hardest, not what happens to the oldest.

2Promotion order is not a state

Readers translate promoted and still listed into current and legacy, because those are the words the rest of the software industry uses. No application here performs that translation, and the register declines to do it either.

The difference bites when a third generation ships. A published state would say what happens to the oldest line; a promotion order says which two are being sold hardest.

3Both real vocabularies belong to platforms

The two entries with a lifecycle vocabulary sell to developers. Twelve applications publish none, so a customer cannot tell whether the engine behind a tier is a released model or an early one.

A production that would decline a preview model cannot decline what it cannot see. The lifecycle states column records which entries publish a stage at all.

The three states a model can be in
Active, Legacy or End-of-Life, readable from the modelLifecycle fieldAmazon Bedrock, model lifecycle / recorded 2026-09-22
Notice for a preview model
At least 30 days before retirementwhich is the stage sora-2 sits inMicrosoft Foundry, lifecycle and support policy / recorded 2026-09-22
What a date in that table commits to
The shutdown dates listed indicate the earliest possible dates on which a model might be retiredGoogle, Gemini deprecations / recorded 2026-09-22
Sora web and app
26 April 2026discontinuedOpenAI Help Center / recorded 2026-09-12
Models carried
Kling 3.0 and 3.0 Omni, with VIDEO 2.6 still listed as a plan benefittwo generations live at onceKling AI, membership plans / recorded 2026-09-12

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: Older generations, Quiet about the last version, Per-model metering.