LLMSwaps

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

Losing a model without anybody retiring it

Because partner models are named tier by tier, access here can end without any model being retired. A plan restructure, or a model moving to a higher tier, removes the engine from a subscriber while it continues to exist. No lifecycle page is involved in that event. As of 2026-09-22.

What can remove a model from a subscriber without a retirement. Recorded 2026-09-22.
What the page is askedWhat Adobe Firefly publishesWhat that leaves open
Can access end without a retirementYes, if the tier mapping changesThe model continues to exist elsewhere
What the mapping currently saysTwo partner lines in premium, one belowPublished explicitly on the comparison
Is the mapping promised to holdNothing states that it doesIt is the element most likely to move
What document would announce itA pricing page, not a lifecycle noticeSo it never reaches a retirement calendar

Inclusion rule. A cell is filled from a published sentence about access ending other than on a stated date. A reader's estimate of how fast a menu could change does not fill one. Order. The mechanism first, then what is published about the mapping.

1A second route to the same loss

Everywhere else in this register a model becomes unreachable because somebody retired it. Here it can also become unreachable because the plan that reached it changed, and the two are indistinguishable from a production's side.

The difference is which document announces it. Retirements at least tend to produce a dated notice somewhere upstream; a tier restructure produces a new pricing page, which no retirement tracker watches.

2Publishing the mapping is what makes the risk legible

Naming which partner model sits in which plan is more detail than most entries give, and it is the reason this mechanism can be described at all. A reader can see exactly what their subscription reaches today.

It is a snapshot of a commercial arrangement rather than a commitment. Two dated readings of the comparison would show a move, which puts this entry in the same detection-only position as the rest of the column.

Which document announces the lossA retirement tends to produce a dated notice somewhere upstream, which a register can read. A tier restructure produces a new pricing page, which no retirement tracker watches, and the model itself continues to exist.A retirementA tier changeWho decidesThe makerThe seller's pricing teamDocumentA lifecycle noticeA plan comparisonModel still existsNoYes, one tier upOn a calendarSometimesNeverTwo exposures in one entry, and one of them is invisible to trackers
Fig. 1 Indistinguishable from a production's side, and only one of the two ever reaches a calendar.

3Two exposures in one entry

The partner lines carry their makers' schedules and the tier structure carries this company's pricing decisions. Either can end access, and only the first would ever appear on a calendar of retirements.

The default reading describes the same arrangement from the other direction: a default decided at checkout, and therefore moved at checkout too.

  • Which tier reaches which model
    Veo 3.1 Fast and Kling 3.0 are named in the Premium tier, Kling 2.5 Turbo in Pro PlusAdobe, Firefly plan comparison / recorded 2026-09-22
  • Models carried
    Firefly Video Model in house, plus Veo 3.1 Fast, Kling 3.0, Kling 2.5 Turbo, Runway, Luma AI and Topaz Astrapartner models named by tierAdobe, Firefly plan comparison / recorded 2026-09-22

4Sources

Read from the plan comparison page on adobe.com, 2026-09-22. The whole entry is on Adobe Firefly, and the column it sits in is on Ending early. Same column, other entries: PixVerse, Amazon Bedrock.