# LLMSwaps (llmswaps.com) > LLMSwaps records announced retirement dates for generative video models and which apps still list them, so a production can see what it is building on before the date arrives. This site is open for crawling, indexing, quoting and model training. Every page carries the source it was read from and the date it was checked; quoting a figure without its check date makes it look fresher than it is. Full text of every page in one file: https://llmswaps.com/llms-full.txt ## Overview - [LLMSwaps: video model retirements](https://llmswaps.com/): Announced end dates for generative video models, and which apps still carry them, with the page and date behind every line. ## Change calendar - [Announced end dates for video models](https://llmswaps.com/calendar/): Every publicly announced end date for a generative video model tracked here, and why an empty calendar is a finding rather than reassurance. ## Models - [Sora: the dates OpenAI has announced](https://llmswaps.com/models/sora/lifecycle/): The announced end dates for Sora's app and its API, what happens to work stored inside it, and whether any replacement model is named. ## Applications - [Which models SceneMixer carries](https://llmswaps.com/apps/scenemixer/models/): The video models SceneMixer names on its own pages, whose models they are, which of them carry an announced end date, and where that date was published. - [Which models LTX Studio carries](https://llmswaps.com/apps/ltx-studio/models/): The video models LTX Studio names on its own pages, whose models they are, which of them carry an announced end date, and where that date was published. - [Which models Kling AI carries](https://llmswaps.com/apps/kling-ai/models/): The video models Kling AI names on its own pages, whose models they are, which of them carry an announced end date, and where that date was published. - [Which models Pika carries](https://llmswaps.com/apps/pika/models/): The video models Pika names on its own pages, whose models they are, which of them carry an announced end date, and where that date was published. - [Which models invideo AI carries](https://llmswaps.com/apps/invideo-ai/models/): The video models invideo AI names on its own pages, whose models they are, which of them carry an announced end date, and where that date was published. - [Which models Runway carries](https://llmswaps.com/apps/runway/models/): The video models Runway names on its own pages, whose models they are, which of them carry an announced end date, and where that date was published. - [Which models Luma carries](https://llmswaps.com/apps/luma/models/): The video models Luma names on its own pages, whose models they are, which of them carry an announced end date, and where that date was published. - [Which models Adobe Firefly carries](https://llmswaps.com/apps/adobe-firefly/models/): Which video models Adobe Firefly names per plan, whose models they are, which carry an announced end date, and where that date was published. - [Which models Hailuo AI carries](https://llmswaps.com/apps/hailuo-ai/models/): The video models Hailuo AI names on its own pages, whose models they are, which of them carry an announced end date, and where that date was published. - [Which models PixVerse carries](https://llmswaps.com/apps/pixverse/models/): The video models PixVerse names on its own pages, whose models they are, which of them carry an announced end date, and where that date was published. - [Which models Vidu carries](https://llmswaps.com/apps/vidu/models/): The video models Vidu names on its own pages, whose models they are, which of them carry an announced end date, and where that date was published. - [Which models fal carries](https://llmswaps.com/apps/fal/models/): The video models fal names on its own pages, whose models they are, which of them carry an announced end date, and where that date was published. - [Which models Microsoft Foundry carries](https://llmswaps.com/apps/microsoft-foundry/models/): The video models Microsoft Foundry lists with retirement dates, the notice it commits to, and what a deployment does once the date passes. - [Which models Amazon Bedrock carries](https://llmswaps.com/apps/amazon-bedrock/models/): What Amazon Bedrock publishes about the life of a model it resells: three states, a notice period in months, and what a request does after the date. - [Which models Gemini API carries](https://llmswaps.com/apps/gemini-api/models/): The video models Gemini API names on its own pages, whose models they are, which of them carry an announced end date, and where that date was published. - [Which models Wan-AI carries](https://llmswaps.com/apps/wan-ai/models/): The video models Wan-AI names on its own pages, whose models they are, which of them carry an announced end date, and where that date was published. ## Sourcing - [How a date gets onto this site](https://llmswaps.com/sourcing/): What counts as an announced end date, why app menus and model dates are kept apart, and what this register deliberately does not track. ## Questions - [How much warning anyone actually gives](https://llmswaps.com/questions/how-much-notice/): Applications name no figure at all. The platforms that host video models commit to 30 days, 60 days or six months, depending on which one you call. - [What happens to work stored inside a model that ends](https://llmswaps.com/questions/what-happens-to-your-work/): One vendor published what it would do with stored work when a model shut down. The answer was deletion after a final window. - [Who reserves the right to change the menu](https://llmswaps.com/questions/who-publishes-a-notice-clause/): One pricing page says outright that the models it offers may change, and nobody anywhere publishes how much notice would come with it. - [An aggregator inherits somebody else's calendar](https://llmswaps.com/questions/aggregators-inherit-schedules/): Two apps resell models they did not make, which means their menus can change for reasons entirely outside their own control. - [Carrying one model against carrying several](https://llmswaps.com/questions/one-model-or-many/): One app names a single house model on every plan while another sells two generations at once, and both are stable in different ways. - [Why naming the version on the price list matters](https://llmswaps.com/questions/naming-the-version/): An app that prints the model and version beside the rate makes a retirement visible in advance. An unnamed house tier cannot. - [What a blank in the date column means](https://llmswaps.com/questions/what-a-blank-date-means/): An empty calendar is a finding about announcements, not an assurance about schedules. The distinction is the whole point of the register. - [Who says what replaces a retired model](https://llmswaps.com/questions/who-names-a-successor/): One dated row here names what follows it, and the successor is a later version of the same model. Every other ending arrives with no destination. - [What an endpoint does once the date passes](https://llmswaps.com/questions/what-happens-after-the-date/): One platform names the exact response a retired model returns. Another states that requests fail and the model leaves every region. Most describe nothing. - [Whether a published retirement date can move](https://llmswaps.com/questions/can-a-date-move/): One platform states its dates cannot be pushed back. One maker calls its dates the earliest possible. The same-looking row means opposite things. - [Who can end access before a published date](https://llmswaps.com/questions/who-can-cut-you-off-early/): One platform can end access after fifteen days of disuse. One pricing page reserves the right to replace models at any time. Neither needs a date. - [Who performs a migration, and who leaves it to you](https://llmswaps.com/questions/who-moves-you-across/): One platform states migration will not happen automatically. Nobody states the opposite, so the move is the customer's work everywhere in this register. - [How many conditions an entry admits a model can be in](https://llmswaps.com/questions/how-many-states-are-published/): Three on one platform, two stages on another, and none anywhere else. Twelve entries treat a model as either on the menu or gone. - [Which entries keep a previous generation on sale](https://llmswaps.com/questions/who-keeps-an-older-generation/): Three entries list an earlier generation beside the current one. That is a foothold rather than a policy, and none of them says how long it lasts. - [Which entries never mention the version before](https://llmswaps.com/questions/who-goes-quiet-about-the-previous-version/): Three entries promote a numbered generation and say nothing about the ones it replaced. A number implies earlier ones existed. - [Where each model carries its own price](https://llmswaps.com/questions/where-the-meter-is-per-model/): Three entries attach a price to each named model rather than bundling them, so the invoice records which engine produced what. - [Which entries mark the models they made themselves](https://llmswaps.com/questions/who-separates-house-from-licensed/): Almost none. House lines and licensed rows are presented in the same type, and the two halves fail on different companies' decisions. - [What holding the weights changes about all this](https://llmswaps.com/questions/what-downloadable-weights-change/): A copy already downloaded cannot be withdrawn, so a retirement date stops applying and hardware, storage and retention start. - [Where the plan decides which engine you reach](https://llmswaps.com/questions/which-tier-reaches-which-model/): One entry names partner models tier by tier, so the subscription decides. Another names a model and version per priced tier. - [How many entries publish any date at all](https://llmswaps.com/questions/how-many-entries-publish-a-date/): Five of the sixteen entries carry a date somebody published. Three companies produced them, and none is an application a production buys from. ## Register fields - [Named replacement: the column that stays empty](https://llmswaps.com/fields/named-replacement/): A retirement notice can name the model that takes over. The one retirement recorded here names nothing, so this column carries an absence instead. - [Stored work: what a shutdown does to the files](https://llmswaps.com/fields/stored-work/): A model ending also ends the place its output was kept. One notice here states deletion after a final export window; every other cell is blank. - [Notice period: the warning nobody has promised](https://llmswaps.com/fields/notice-period/): No application here publishes how much warning arrives before its model changes. Three hosting platforms do publish a period, counted in days or in months. - [Default tier: the model most work gets made on](https://llmswaps.com/fields/default-tier/): Whatever an untouched project runs on is where most delivered work comes from. One price list names it; the rest leave the starting model unstated. - [Lifecycle state: what a model is allowed to be](https://llmswaps.com/fields/lifecycle-state/): Three hosting platforms publish the states a model can sit in before it goes. No application publishes any, so a model there is on the menu or off it. - [Ending early: how access stops before a date](https://llmswaps.com/fields/ending-early/): A published date is one of several ways access ends. One platform cuts it off after fifteen days of disuse; one page reserves the right to swap. ## Notice period, entry by entry - [Microsoft Foundry: 60 days, and not extendable](https://llmswaps.com/fields/notice-period/microsoft-foundry/): Foundry commits to at least 60 days of notice for a live model and 30 for a preview, and states that a retirement date cannot be pushed back on request. - [Amazon Bedrock: six months, or forty-five days](https://llmswaps.com/fields/notice-period/amazon-bedrock/): Bedrock states a legacy period of six months or 45 days on each model card, and says migration to a successor will not happen automatically for you. - [Gemini API: notice promised, never counted](https://llmswaps.com/fields/notice-period/gemini-api/): Google publishes shutdown dates for five Veo identifiers and promises advance notice, but attaches no number of days to the promise anywhere on the page. - [LTX Studio: a written right, and no period](https://llmswaps.com/fields/notice-period/ltx-studio/): The pricing page reserves the right to update, modify or replace available models and does not guarantee continued availability of any one of them. - [SceneMixer: no period, but a checkable tier](https://llmswaps.com/fields/notice-period/scenemixer/): Nothing states how much warning arrives before a tier changes model. The tier names its model and version, so a change is checkable after it happens. - [Runway: a conversion table that can move](https://llmswaps.com/fields/notice-period/runway/): Nothing is published about warning before the credit conversions change. The table names models, so an edit is detectable but is not an announcement. - [Sora: five months, given rather than promised](https://llmswaps.com/fields/notice-period/sora/): The consumer product closed in April and the interface closes in September. That gap is an observation, and the notice never calls it a policy. ## Named replacement, entry by entry - [Microsoft Foundry: a successor in the table](https://llmswaps.com/fields/named-replacement/microsoft-foundry/): One dated row on the retirement schedule names what replaces it: a later version of the same model. The row after that names nothing at all. - [Sora: an ending with nowhere named](https://llmswaps.com/fields/named-replacement/sora/): The discontinuation notice gives two dates and a deletion policy. It names no replacement model, so the runway it provided led nowhere in particular. - [Gemini API: three lines, no successor named](https://llmswaps.com/fields/named-replacement/gemini-api/): Three Veo identifiers carry the same shutdown date and none of them names a replacement. The newer generation is not stated as the route off them. - [Amazon Bedrock: migration is not automatic](https://llmswaps.com/fields/named-replacement/amazon-bedrock/): The lifecycle page states that migration will not happen automatically. It also describes no route, so both halves of the succession question stay open. - [LTX Studio: an older generation still sold](https://llmswaps.com/fields/named-replacement/ltx-studio/): Two house generations are sold side by side, so a production has somewhere to stand. Nothing states that the older line stays, or what replaces it. - [Kling AI: both generations, one plan](https://llmswaps.com/fields/named-replacement/kling-ai/): A subscription reaches the current models and a previous generation at once. Nothing states which is the route off the other, or how long both remain. - [Luma: two house lines, neither retired](https://llmswaps.com/fields/named-replacement/luma/): Two house generations sit on one plan table beside licensed models from several makers. No row names a successor and none is marked as leaving. - [Wan-AI: the copy outlives the listing](https://llmswaps.com/fields/named-replacement/wan-ai/): The weights are published under a permissive licence with download commands on the model card. Withdrawing the listing does not reach a copy already taken. - [Pika: one model, and nothing behind it](https://llmswaps.com/fields/named-replacement/pika/): Every plan names the same house model. A single line removes the inherited schedules of an aggregator and removes the fallback of a second generation. - [PixVerse: V6 shown, earlier lines silent](https://llmswaps.com/fields/named-replacement/pixverse/): One house version is promoted beside licensed models. Whether the versions before it remain selectable is not stated anywhere on the page read. - [Vidu: current generation, earlier ones quiet](https://llmswaps.com/fields/named-replacement/vidu/): The page names a current generation and a real-time line. Whether the two generations before them are still offered is not addressed anywhere on it. - [Hailuo AI: one generation, nothing behind](https://llmswaps.com/fields/named-replacement/hailuo-ai/): The home page promotes a single model generation. Whether earlier generations remain reachable is not stated, so no fallback is published. - [invideo AI: six makers decide the route](https://llmswaps.com/fields/named-replacement/invideo-ai/): The model list aggregates six makers. Each decides its own succession, and the app says nothing about how such a decision reaches a subscriber. - [Adobe Firefly: replacement arrives by tier](https://llmswaps.com/fields/named-replacement/adobe-firefly/): Partner models are named per plan tier, so losing access can happen through a tier change rather than through any model being retired. ## Stored work, entry by entry - [Sora: deletion after a final export window](https://llmswaps.com/fields/stored-work/sora/): The notice states that data associated with the product is deleted after any final export window passes, which makes storage a second and earlier deadline. - [Microsoft Foundry: 410 Gone, and no more](https://llmswaps.com/fields/stored-work/microsoft-foundry/): After a retirement date every inference request returns 410 Gone. The lifecycle page says nothing about material produced before the date. - [Amazon Bedrock: removed from every region](https://llmswaps.com/fields/stored-work/amazon-bedrock/): After end-of-life the model is removed from all regions and requests to it fail. Nothing on the page concerns material a customer generated earlier. - [Gemini API: output leaves before the date](https://llmswaps.com/fields/stored-work/gemini-api/): Generated material is returned to the caller, so a shutdown removes the ability to make more and reaches nothing already produced. - [Wan-AI: files that were never theirs](https://llmswaps.com/fields/stored-work/wan-ai/): Output is generated on hardware the user controls, so a withdrawal reaches none of it. The licence on the model card is what keeps it usable. - [fal: a meter per output, not a library](https://llmswaps.com/fields/stored-work/fal/): Video models are billed by output unit, per second or per video. Delivery is the whole relationship, so nothing about retention appears on the page. - [LTX Studio: a clause about models only](https://llmswaps.com/fields/stored-work/ltx-studio/): The footnote reserving the right to replace models says nothing about work already made inside the product. That is a separate question it never reaches. - [SceneMixer: the price list is silent here](https://llmswaps.com/fields/stored-work/scenemixer/): Each tier names a model and version, and nothing on the same page addresses material kept inside a project when a tier's model changes. ## Default tier, entry by entry - [SceneMixer: the starting tier is named](https://llmswaps.com/fields/default-tier/scenemixer/): The default is a named model at a named resolution, printed on the public price list, which makes a change to it checkable after the fact. - [Pika: the default is the whole menu](https://llmswaps.com/fields/default-tier/pika/): Every plan names the same house model, so the starting engine follows from the menu having a single line rather than from any statement about defaults. - [Hailuo AI: promotion sets the starting line](https://llmswaps.com/fields/default-tier/hailuo-ai/): One generation is promoted on the public page and nothing else is named, so what a new user gets is decided by placement rather than by a stated default. - [Vidu: two lines, neither marked as the start](https://llmswaps.com/fields/default-tier/vidu/): A current generation and a real-time line are both named, and nothing indicates which one a new project runs on when nobody chooses. - [Kling AI: both included, none marked first](https://llmswaps.com/fields/default-tier/kling-ai/): A membership reaches two generations at once. The newer pair is promoted as current, and no page states which one an untouched project uses. - [Luma: a mixed table, no starting line](https://llmswaps.com/fields/default-tier/luma/): House generations and licensed models share one plan table. Nothing on it identifies which line a project runs on when nobody selects one. - [Runway: every line priced, none the start](https://llmswaps.com/fields/default-tier/runway/): The credit conversions cover each model individually and none is identified as what a new project uses, so the starting engine is not published. - [Adobe Firefly: the plan decides the default](https://llmswaps.com/fields/default-tier/adobe-firefly/): Partner models are named per tier, so what a project can reach follows from the subscription rather than from any statement about a starting engine. - [fal: nothing here runs without being named](https://llmswaps.com/fields/default-tier/fal/): Models are priced individually and named per call, so no engine runs unasked and the column records an absence of defaults rather than a missing statement. - [Microsoft Foundry: the version is deployed](https://llmswaps.com/fields/default-tier/microsoft-foundry/): A deployment names a model version explicitly, which is what makes a retirement schedule meaningful and leaves no room for a default to sit in. - [Amazon Bedrock: your request is the default](https://llmswaps.com/fields/default-tier/amazon-bedrock/): A request names the model identifier it wants, so the effective starting engine is whatever a customer's own code has been saying since it was written. - [Gemini API: an alias, or a pinned identifier](https://llmswaps.com/fields/default-tier/gemini-api/): Callers choose between a moving alias and a specific identifier. The deprecations table lists identifiers, so only a pinned choice matches a date. - [Wan-AI: the default is the copy you kept](https://llmswaps.com/fields/default-tier/wan-ai/): Several repositories are published and the user picks one to download, so the starting engine is whichever weights a production already holds. ## Lifecycle state, entry by entry - [Amazon Bedrock: three states, on the model](https://llmswaps.com/fields/lifecycle-state/amazon-bedrock/): Active, Legacy and End-of-Life are published as states a model can sit in, readable from the interface rather than from a page somebody has to re-read. - [Microsoft Foundry: the stage sets the notice](https://llmswaps.com/fields/lifecycle-state/microsoft-foundry/): Preview and generally available are published stages, and which one a model sits in decides whether thirty or sixty days of notice are owed. - [Gemini API: the listing is the state](https://llmswaps.com/fields/lifecycle-state/gemini-api/): No state vocabulary appears here. A model is absent from the deprecations table or listed on it, and the listing carries a date called the earliest. - [Sora: discontinued, applied twice](https://llmswaps.com/fields/lifecycle-state/sora/): The notice uses one condition, discontinued, and applies it to two surfaces on dates five months apart. No intermediate state was ever published. - [LTX Studio: a clause where states would be](https://llmswaps.com/fields/lifecycle-state/ltx-studio/): No condition is published for any model. The pricing footnote reserving the right to replace models is what stands where a state vocabulary would sit. - [Kling AI: generations used as states](https://llmswaps.com/fields/lifecycle-state/kling-ai/): Two generations are sold together and promoted differently. Current and previous do the work of lifecycle labels without being published as conditions. - [Wan-AI: published, not published, or held](https://llmswaps.com/fields/lifecycle-state/wan-ai/): A repository is either published or withdrawn. A copy already downloaded sits outside that distinction entirely, under the licence stated on the card. ## Ending early, entry by entry - [Amazon Bedrock: fifteen days of disuse](https://llmswaps.com/fields/ending-early/amazon-bedrock/): Once a legacy period begins, an existing customer may lose access after fifteen days of inactivity, which is far shorter than either published period. - [Microsoft Foundry: the date cannot move](https://llmswaps.com/fields/ending-early/microsoft-foundry/): Retirement dates are stated to be non-extendable, so no route to an exception is described for a customer with work still in flight. - [Gemini API: a date that can become later](https://llmswaps.com/fields/ending-early/gemini-api/): Shutdown dates are described as the earliest on which a model might be retired, so each one is a floor that can move later with nothing to announce. - [LTX Studio: nothing to be early against](https://llmswaps.com/fields/ending-early/ltx-studio/): The footnote reserves the right to update, modify or replace models at any time, so there is no published date for an ending to arrive before. - [Runway: an edit rather than an ending](https://llmswaps.com/fields/ending-early/runway/): Access here can end through an edit to the credit conversion table, which carries no date, no notice and no statement about what it means. - [Adobe Firefly: access ends by plan change](https://llmswaps.com/fields/ending-early/adobe-firefly/): Partner models are named per tier, so access can end through a pricing change with nothing retired and no lifecycle document involved at all. - [PixVerse: nothing to compare a loss against](https://llmswaps.com/fields/ending-early/pixverse/): One house version is promoted and earlier ones are not mentioned, so a line leaving the page cannot be distinguished from a line that was never listed. ## Two entries side by side - [Microsoft Foundry and Amazon Bedrock: days](https://llmswaps.com/contrasts/foundry-and-bedrock/): Both publish a notice period before a model goes. One counts in days and fixes the date; the other counts in months and can end access sooner. - [Microsoft Foundry and the Gemini API: days](https://llmswaps.com/contrasts/foundry-and-gemini-api/): One entry commits to a period counted in days. The other promises advance notice in words and never attaches a figure to it anywhere on the page. - [Amazon Bedrock and the Gemini API: drift](https://llmswaps.com/contrasts/bedrock-and-gemini-api/): One entry can end access after fifteen days of disuse. The other publishes dates that may quietly become later. Two errors, in opposite directions. - [Microsoft Foundry and Sora: policy or once](https://llmswaps.com/contrasts/foundry-and-sora/): One entry publishes a notice period before anything is scheduled. The other produced a five-month interval once, with nothing describing it as policy. - [LTX Studio and SceneMixer: two useful pages](https://llmswaps.com/contrasts/ltx-studio-and-scenemixer/): Neither publishes a notice period. One writes down the right to replace models; the other names the model and version behind every tier. - [LTX Studio and Amazon Bedrock: right or owed](https://llmswaps.com/contrasts/ltx-studio-and-bedrock/): One page states that no continued availability is guaranteed. The other states a period in months before a model reaches end-of-life. - [Wan-AI and Microsoft Foundry: file or code](https://llmswaps.com/contrasts/wan-ai-and-foundry/): One entry publishes weights that keep running after a withdrawal. The other publishes the exact status a request receives once the date has passed. - [Wan-AI and Sora: a copy, or a deletion](https://llmswaps.com/contrasts/wan-ai-and-sora/): One entry's output was never in anybody's product. The other's shutdown notice states that data is deleted once a final export window passes. - [Pika and invideo AI: one schedule or six](https://llmswaps.com/contrasts/pika-and-invideo-ai/): One entry carries a single house model and controls its schedule. The other aggregates six makers and controls none of theirs. Neither publishes a date. - [Pika and Adobe Firefly: one line or a tier](https://llmswaps.com/contrasts/pika-and-adobe-firefly/): One entry names the same model on every plan. The other names partner models tier by tier, so the subscription decides which engine a project reaches. - [Kling AI and Hailuo AI: two lines, or one](https://llmswaps.com/contrasts/kling-ai-and-hailuo-ai/): One maker sells two generations on a single membership. The other promotes one and does not say whether anything earlier remains reachable. - [Luma and Vidu: a long menu or a short one](https://llmswaps.com/contrasts/luma-and-vidu/): One entry lists two house generations beside licensed models from several makers. The other names two lines and addresses nothing before them. - [fal and SceneMixer: no default, or a named one](https://llmswaps.com/contrasts/fal-and-scenemixer/): On one entry nothing runs unless a call names it. On the other a named model and resolution is what an untouched project gets. - [fal and Pika: naming a model, or having one](https://llmswaps.com/contrasts/fal-and-pika/): One entry requires every call to name a model from a priced list. The other names the same house model on every plan, so there is nothing to name. - [Runway and SceneMixer: credits or seconds](https://llmswaps.com/contrasts/runway-and-scenemixer/): Both name the models they sell. One converts credits into seconds per model; the other prices seconds directly per named tier. - [Runway and Luma: the same table, twice](https://llmswaps.com/contrasts/runway-and-luma/): Both put house and licensed models on one table with no marking, so two failure modes are presented in the same type by two different sellers. - [Adobe Firefly and Kling AI: gate or bundle](https://llmswaps.com/contrasts/adobe-firefly-and-kling-ai/): One entry gates partner models by tier, so the plan decides the engine. The other includes two generations on one membership, with neither marked. - [The Gemini API and Sora: table or notice](https://llmswaps.com/contrasts/gemini-api-and-sora/): One maker keeps a standing table of dated identifiers. The other published one notice with two dates. Neither names a successor for the video lines. - [invideo AI and Luma: where aggregation sits](https://llmswaps.com/contrasts/invideo-ai-and-luma/): One entry aggregates six makers and builds no model of its own. The other is a maker that also resells several others on the same plan table. - [PixVerse and Vidu: the same silence, twice](https://llmswaps.com/contrasts/pixverse-and-vidu/): Both promote a numbered house generation and neither addresses the versions before it. Two entries producing the same gap for different reasons. - [Amazon Bedrock and Wan-AI: window or none](https://llmswaps.com/contrasts/bedrock-and-wan-ai/): One entry publishes a window with a clause that can shorten it. The other has no window, because a downloaded copy does not stop working. - [Hailuo AI and Pika: one line, two reasons](https://llmswaps.com/contrasts/hailuo-ai-and-pika/): Both publish one model line. One is a maker promoting a generation, the other an application naming the same house model on every plan. - [SceneMixer and Pika: named or implied](https://llmswaps.com/contrasts/scenemixer-and-pika/): One entry names the model and resolution a new project starts on. The other has one model everywhere, so the answer follows from the menu. - [Microsoft Foundry and Runway: stages or edits](https://llmswaps.com/contrasts/foundry-and-runway/): One entry publishes stages that decide what a retirement owes. The other publishes a conversion table where a line simply stops being listed. - [The Gemini API and LTX Studio: floor or right](https://llmswaps.com/contrasts/gemini-api-and-ltx-studio/): One entry publishes dates described as the earliest a model might go. The other publishes a right to replace models and no dates at all. - [Foundry and Bedrock: stages against states](https://llmswaps.com/contrasts/states-at-foundry-and-bedrock/): One entry publishes two stages that set the notice owed. The other publishes three states and puts the current one on the model itself. - [Sora and the Gemini API: word or listing](https://llmswaps.com/contrasts/sora-and-gemini-api/): One entry used a single undefined word on two dates. The other has no vocabulary, and a model being listed at all is the condition. - [LTX Studio and Kling AI: right or order](https://llmswaps.com/contrasts/ltx-studio-and-kling-ai/): Neither publishes a state. One publishes a right to replace models at any time; the other lets promotion order stand in for current and previous. - [invideo AI and fal: a bundle or a line item](https://llmswaps.com/contrasts/invideo-ai-and-fal/): One entry bundles six makers into a subscription with no default stated. The other prices each model individually, so nothing runs unless a call names it. - [Wan-AI and fal: never held, or handed over](https://llmswaps.com/contrasts/wan-ai-and-fal/): Neither entry holds material, for different reasons. One generates on the customer's own hardware; the other delivers each output unit and bills for it. ## Models, and the entries carrying them - [Veo 3.1: the four menus carrying it](https://llmswaps.com/models/veo-3-1/carried-by/): Four entries in this register name this line on their own pages, in four different shapes, and none of them publishes a date for it. - [Veo 3: a carried line that has a date](https://llmswaps.com/models/veo-3/carried-by/): This generation is both purchasable through a platform here and listed with a shutdown date on its maker's deprecations page, which is a rare combination. - [Veo 3 preview lines: already switched off](https://llmswaps.com/models/veo-3-preview/carried-by/): Two preview identifiers carry a shutdown date that has already passed, and no entry here names them. This is what a finished retirement looks like. - [Kling 3.0: six menus, one maker](https://llmswaps.com/models/kling-3-0/carried-by/): Six entries name this line, including the maker's own membership. It is the most widely carried model in the register and none of the six publishes a date. - [Kling 2.5 Turbo: an older line, still sold](https://llmswaps.com/models/kling-2-5-turbo/carried-by/): Two entries still name this earlier line, one gated a tier below the current model and one priced individually. Its maker publishes nothing about it. - [MiniMax H3: five menus, one the maker's](https://llmswaps.com/models/minimax-h3/carried-by/): Five entries name this line, including the maker's own page and a product that splits it into a standard and a fast tier. None publishes a date. - [Wan: one family, four version levels](https://llmswaps.com/models/wan/carried-by/): Four entries carry this family and no two of them carry the same version, including one that publishes the weights themselves rather than an endpoint. - [Sora 2: two menus and a closing door](https://llmswaps.com/models/sora-2/carried-by/): One application still names this line and one platform hosts dated versions of it, while its maker has announced that its own interface closes. - [Model lines with one place to buy them](https://llmswaps.com/models/single-carrier-lines/carried-by/): Eight house lines here appear on exactly one entry's pages. One schedule, one document and one company decides when each of them changes. - [Model lines on more than one menu](https://llmswaps.com/models/carried-more-than-once/carried-by/): Six lines here are carried by two or more entries. Counting them shows how far one version decision reaches across products that look like rivals. ## Terms used in the register - [Deprecated: running, and not recommended](https://llmswaps.com/terms/deprecated/): Borrowed from software, where it means a feature still works and should not be built on. Applied to a model it implies no date at all. - [Retirement date: the day it stops](https://llmswaps.com/terms/retirement-date/): The day access to a model ends. Reading one requires knowing whether it is fixed, whether it is the earliest possible day, and which surface it covers. - [Shutdown: when requests stop being answered](https://llmswaps.com/terms/shutdown/): The moment a model no longer responds. Distinct from deprecation, which describes a recommendation, and from removal from a menu, which describes a page. - [End-of-life: the most definite word here](https://llmswaps.com/terms/end-of-life/): Borrowed from hardware, where it means a stated date after which a thing does not run. Where a vendor uses it, expect a date and chase its absence. - [Legacy period: warning before removal](https://llmswaps.com/terms/legacy-period/): A named window during which a model stays available to existing customers but cannot be adopted by new ones. One platform here publishes its length. - [Sunset: the word that implies a date](https://llmswaps.com/terms/sunset/): The retirement word most often attached to an actual calendar entry. Worth searching for, and worth checking which surfaces it covers. - [Advance notice: a number, or a sentiment](https://llmswaps.com/terms/advance-notice/): The warning a vendor commits to give before a model goes. Only a figure in days or months is a commitment a production can plan against. - [General availability: the longer notice](https://llmswaps.com/terms/general-availability/): The stage at which a model is considered ready for production use. On one platform here it doubles the notice a retirement owes. - [Preview model: shorter notice, no promises](https://llmswaps.com/terms/preview-model/): A model offered before general availability. Where a platform ties notice to stage, preview carries the shorter figure, and video models often sit here. - [Non-extendable: a date that only arrives](https://llmswaps.com/terms/non-extendable-date/): A published statement that a retirement date cannot be pushed back. Unhelpful to read and better to plan against than a date that might move. - [Model version: the part worth recording](https://llmswaps.com/terms/model-version/): The specific release of a model line. Without it, a family name cannot be matched to a dated announcement or used to explain a change in output. - [Version alias: a name that moves](https://llmswaps.com/terms/version-alias/): A convenience name resolving to whatever version a vendor currently recommends. Its whole purpose is to change, and no deprecations table lists it. - [Version pinning: what a fixed name covers](https://llmswaps.com/terms/version-pinning/): Naming an exact version so the same weights answer every call. It fixes one thing and leaves the presets, the stack and the retirement date moving. - [Model identifier: the string in a schedule](https://llmswaps.com/terms/model-identifier/): The exact name a request uses. Schedules are written about identifiers, so a customer without one cannot match a published date to their own work. - [Model card: where per-model facts sit](https://llmswaps.com/terms/model-card/): A page describing one model. In this register it is where a licence, a download command or a per-model notice period turns out to be published. - [Changelog: the page that carries dates](https://llmswaps.com/terms/changelog/): A dated record of changes to a product or interface. In this field it is the difference between a vendor a production can plan around and one it cannot. - [Successor model: named, or left to you](https://llmswaps.com/terms/successor-model/): The model a retirement notice says to move to. One dated row in this register names one, and it is a later version of the same model. - [Silent update: the change no page records](https://llmswaps.com/terms/silent-update/): A model updated in place, keeping its name while its behaviour moves. It is the most common disruption and the one no register can observe. - [Endpoint: the door that can be closed](https://llmswaps.com/terms/endpoint/): The address a request is sent to. Everything a retirement can take away arrives through it, and a held copy of the weights sits outside it entirely. - [Published weights: a copy nobody withdraws](https://llmswaps.com/terms/open-weights/): Model files distributed for download under a stated licence. A withdrawal reaches the listing, not the copies, so the retirement question changes shape. - [Inference: the request a retirement stops](https://llmswaps.com/terms/inference/): Running a model to produce output. It is the unit a retirement date applies to, and the unit most of this register's pricing is measured in. - [410 Gone: a retirement software can read](https://llmswaps.com/terms/gone-410/): The response one platform states its retired models return. It is the single machine-readable retirement signal anywhere in this register. - [Region availability: an escape route closed](https://llmswaps.com/terms/region-availability/): Whether a model remains reachable somewhere else. One platform here states removal is global, which rules out a geographic migration. - [Inactivity clause: access lost by not using](https://llmswaps.com/terms/inactivity-clause/): A published sentence allowing access to end after a period of disuse. One platform here states fifteen days, inside a window measured in months. - [Active deployment: who gets told](https://llmswaps.com/terms/active-deployment/): A configured use of a specific model version. One platform sends its retirement notices to subscriptions that have one, which decides who hears anything. - [Export window: the deadline nobody quoted](https://llmswaps.com/terms/export-window/): A period for retrieving material before a product closes. In the one case here it preceded deletion and was quoted far less than the headline date. - [House model: one schedule, and no shelf](https://llmswaps.com/terms/house-model/): A model the seller made itself. It removes the inherited retirement calendars of a resale menu and removes the fallback of a second maker's line. - [Licensed model: a row that ends elsewhere](https://llmswaps.com/terms/licensed-model/): A model on a seller's menu that somebody else makes. It ends on its maker's schedule and arrives at the customer as an edit to a page. - [Aggregator: one bill, several calendars](https://llmswaps.com/terms/aggregator/): A product selling access to models from several makers. It inherits every maker's retirement schedule and controls none of them. - [Credit conversion: a model list by accident](https://llmswaps.com/terms/credit-conversion/): A table saying how far a credit goes on each model. It publishes a complete model list as a side effect of explaining a plan's arithmetic. - [Output unit: the thing actually sold](https://llmswaps.com/terms/output-unit/): A second of footage, a finished clip, or a credit. The unit decides whether a retirement is visible as a missing line or as an unexplainable change. - [Tier gating: losing a model with no retirement](https://llmswaps.com/terms/tier-gating/): Naming models per plan tier, so access follows the subscription. It creates a second way to lose an engine, with no lifecycle document involved. - [Default engine: where the work comes from](https://llmswaps.com/terms/default-engine/): Whatever a product generates with when nobody chooses. A change there reaches more finished work than a change to any selectable tier. - [Announced date: what gets recorded here](https://llmswaps.com/terms/announced-date/): A date published by the company that makes or serves the model. Press coverage, a forum reply and a model vanishing from a menu are not announcements. - [Blank cell: an unasked question](https://llmswaps.com/terms/blank-cell/): An empty value in this register means a vendor has not published anything on that point. It is not evidence that nothing will change. - [Earliest possible date: a floor, not a day](https://llmswaps.com/terms/earliest-possible-date/): Wording one maker uses for its shutdown dates. It makes each one a lower bound that can quietly become later with nothing published. - [Reading date: why every row carries one](https://llmswaps.com/terms/reading-date/): The day this register read a page. It is what turns a directory of current facts into evidence that something actually changed, and when. - [Reproducibility: the absence all entries share](https://llmswaps.com/terms/reproducibility/): Whether output generated on a version can still be produced later. No entry in this register publishes anything about it. ## Explainers - [What pinning a version actually buys](https://llmswaps.com/learn/pinning-a-version/): Pinning looks like the answer to models changing underneath a product. It solves one problem precisely and leaves three others untouched. - [Recovering after the model changes](https://llmswaps.com/learn/after-a-swap/): When the model under a product is replaced, prompts that worked stop working. The recovery is methodical and mostly does not involve rewriting prompts. - [Planning for the model you use to be switched off](https://llmswaps.com/learn/surviving-a-retirement/): Every model is eventually retired. The work that makes that survivable happens before the announcement, and most of it is bookkeeping. - [What vendors mean by deprecated, sunset and legacy](https://llmswaps.com/learn/what-deprecation-words-mean/): The vocabulary around retiring a model differs by vendor. Knowing the usual shades stops a reader assuming a date exists when none does. - [Reading a lifecycle page in ten minutes](https://llmswaps.com/learn/reading-a-lifecycle-page/): A lifecycle page answers four questions and usually buries two of them. Reading it in the right order settles a plan faster than reading it top to bottom. - [The field that makes a swap explainable](https://llmswaps.com/learn/what-to-record-per-file/): Model, version and date, recorded once per delivered file. It costs nothing at the time and cannot be reconstructed afterwards. - [Keeping five prompts frozen on purpose](https://llmswaps.com/learn/building-a-test-set/): A handful of prompts with known output, never improved, re-run after any suspected change. It catches what no page records. - [Somebody else's schedule, or your own hardware](https://llmswaps.com/learn/hosted-or-downloaded/): A hosted model ends on a date you do not control. Downloaded weights end when you stop paying for hardware. The trade is uncertainty against overhead. - [Finding the model strings you already send](https://llmswaps.com/learn/auditing-your-own-identifiers/): Most teams send a model name written months ago and forgotten. A retirement schedule is unusable until somebody knows which strings their own systems use. - [Finishing a season on the engine it started on](https://llmswaps.com/learn/finishing-a-season-on-one-model/): A series generated half on one model and half on another reads as two productions. Which side to finish on is a decision, not a discovery. - [Telling the people downstream about a change](https://llmswaps.com/learn/telling-clients-about-a-swap/): Editors and clients read a change in look as a mistake unless told otherwise. One dated sentence prevents a round of corrections nobody can make. - [Where the money goes when the engine changes](https://llmswaps.com/learn/budgeting-a-migration/): A migration is mostly not the difference in rate. It is re-establishing a look, re-measuring an attempt ratio, and possibly regenerating delivered work. - [Watching a page that has no changelog](https://llmswaps.com/learn/watching-a-page-for-changes/): Most sellers here publish no dates, so two dated readings of the same page are the whole evidence that a model ever left. The reading is the work. - [Four questions before a season depends on it](https://llmswaps.com/learn/questions-before-committing/): Is the model named on the page you pay from, is a period published, is there an older generation, and could you finish if it went in ninety days. ## Section directories - [Model notices as a CSV](https://llmswaps.com/datasets/): The recorded model names and lifecycle dates as a comma-separated file, each row carrying its source page and the day that page was read. - [Apps and the models behind them](https://llmswaps.com/apps/): A notice per app: the model it currently names, the date that naming last moved, and the page where the app says so, read without an account. - [Model lifecycles on notice](https://llmswaps.com/models/): Lifecycle notices for generative video models: announced dates, deprecation wording and the end dates a vendor has actually committed to in public. - [Fields the register records](https://llmswaps.com/fields/): Every entry here is read along the same list of fields. A page per field: what it holds, where the value comes from, and what a blank cell does not mean. - [Questions about model swaps](https://llmswaps.com/questions/): Questions about which model an app runs and what happens when it is retired, answered from vendor and app pages with the reading date attached. - [Reading a deprecation notice](https://llmswaps.com/learn/): Explainers on model lifecycles: what deprecation wording means in practice, why apps hide the engine, and what to have ready before a shutdown date. - [Entries read side by side](https://llmswaps.com/contrasts/): Pairs of entries whose published answers on one column of the register point opposite ways, with the wording each one used and what the gap costs. - [Terms the register uses](https://llmswaps.com/terms/): Short definitions for the words that appear in retirement notices and in this register, with what each one does and does not commit a vendor to.