LLMSwaps

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

Preview model: shorter notice, and no promises

A preview model is offered before general availability, usually with an explicit reservation that things may change. Where a platform ties its notice period to the stage, preview carries the shorter figure, and in this register the hosted video model is at preview stage. As of 2026-09-22.

What the stage signals, and what it costs. Recorded 2026-09-22.
The label signalsWhat follows for a production
Behaviour may change without noticeA season cannot be guaranteed to look the same
The model may never reach general availabilityBuilding a long run on it is a decision
A shorter notice period, where one existsThirty days rather than sixty
An earlier retirement date, in one case herePreview identifiers went first

Inclusion rule. Read from the lifecycle documentation and deprecations pages in this register that distinguish a preview stage. Order. What the label signals first, then the consequences.

1The label is a warning that most teams accept anyway

Preview models are often the newest and most capable, so productions use them knowing the reservation exists. The practical rule most teams settle on is that preview is fine for exploration and for anything with a short life.

A run of episodes that has to look the same in twelve months is the case where the label matters, and it is exactly the case where the newest model is most tempting.

2Preview lines have already gone first, once

In the one family here with dated rows for both stages, the preview identifiers carried the earlier shutdown date. So a team that built during a preview period was on the shorter runway with nothing on the page grouping the two as one decision.

That is a single observation rather than a rule. It is consistent with the stage-based notice policy published elsewhere in this register, which points the same way.

The stage where video models mostly sitPreview models are often the newest and most capable, so productions use them knowing the reservation exists. In the one family here with dated rows for both stages, the preview identifiers carried the earlier shutdown date.Should a run of episodes be built on a preview model?A short-lived pieceReasonableThe reservation costsnothing if the work isfinished quickly.A season that must matchin a yearA decision, not anaccidentShorter notice, and theearlier date in the onedated case here.An unnamed house tierUnknowableTwelve applicationspublish no stage, so thequestion cannot be asked.Two platforms here distinguish a preview stage; twelve applications publish none
Fig. 1 A production that would decline a preview model cannot decline what a tier name does not reveal.

3Naming the stage is itself a disclosure

Two platforms in this register distinguish a preview stage. Twelve applications publish no stage at all, 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.

A definition rather than a dated entry: no line above is a vendor statement. Where this word turns up in a real notice, the wording and the date are on the preview lines already switched off. Nearby terms: Non-extendable date, Model version, Version alias.