LLMSwaps

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

Which models Adobe Firefly carries

Adobe Firefly (adobe.com) is the only entry here that ties named partner models to particular tiers: Veo 3.1 Fast and Kling 3.0 are named in the Premium plan, Kling 2.5 Turbo in Pro Plus, and some partners are named with no version at all. As of 2026-09-12.

What has been announced, entry by entryFilled where the vendor has announced something in that column, hollow where it has not.What has been announced, entry by entryWhose modelAnnounced endFirefly Video ModelFirefly Video Model — Whose model: In houseFirefly Video Model — Announced end: No date announcedVeo 3.1 FastVeo 3.1 Fast — Whose model: Another vendor, Premium tierVeo 3.1 Fast — Announced end: Earlier Veo versions shut down 30 June 2026Kling 3.0Kling 3.0 — Whose model: Another vendor, Premium tierKling 3.0 — Announced end: No date announcedKling 2.5 TurboKling 2.5 Turbo — Whose model: Another vendor, Pro Plus tierKling 2.5 Turbo — Announced end: No date announcedRunway, Luma AI, Topaz Ast…Runway, Luma AI, Topaz AstraRunway, Luma AI, Topaz Astra — Whose model: Another vendor, named without versionsRunway, Luma AI, Topaz Astra — Announced end: No date announced
Fig. 1 Filled where the vendor has announced something in that column, hollow where it has not.
Models named on Adobe Firefly's own pages, with any retirement date announced by the vendor that makes them. Recorded 2026-09-22.
ModelWhose modelAnnounced end
Firefly Video ModelIn houseNo date announced
Veo 3.1 FastAnother vendor, Premium tierEarlier Veo versions shut down 30 June 2026
Kling 3.0Another vendor, Premium tierNo date announced
Kling 2.5 TurboAnother vendor, Pro Plus tierNo date announced
Runway, Luma AI, Topaz AstraAnother vendor, named without versionsNo date announced

Inclusion rule. Models the app names on its own public pages. A model the app does not name is not listed, and an end date is recorded only when the vendor that makes the model has announced one. Order. As the app orders them on its own page.

1How many models each application names

Rows published per entryHow many rows each entry's own pages support, Adobe Firefly marked. Publishing more is not better; it is what makes a swap visible at all. Recorded 2026-09-22.Rows published per entryLuma6 rows6 rowsAdobe Firefly5 rows5 rowsGemini API5 rows5 rowsinvideo AI5 rows5 rowsRunway5 rows5 rowsSceneMixer5 rows5 rowsWan-AI5 rows5 rowsfal4 rows4 rowsLTX Studio4 rows4 rowsPixVerse4 rows4 rowsAmazon Bedrock3 rows3 rowsKling AI3 rows3 rowsMicrosoft Foundry2 rows2 rowsVidu2 rows2 rowsHailuo AI1 row1 rowPika1 row1 row
Fig. 2 How many rows each entry's own pages support, Adobe Firefly marked. Publishing more is not better; it is what makes a swap visible at all. Recorded 2026-09-22.
Models named per entry, with Adobe Firefly marked. Recorded 2026-09-22.
EntryRows it publishes
Adobe Firefly5 rows
Amazon Bedrock3 rows
fal4 rows
Gemini API5 rows
Hailuo AI1 row
invideo AI5 rows
Kling AI3 rows
LTX Studio4 rows
Luma6 rows
Microsoft Foundry2 rows
Pika1 row
PixVerse4 rows
Runway5 rows
SceneMixer5 rows
Vidu2 rows
Wan-AI5 rows

Inclusion rule. Entries whose own pages name a model, a version identifier or a lifecycle state. House tier names with no model behind them are not counted. Order. Alphabetical by entry name.

Rows carrying an announced end datePer entry, how many of its rows carry a date announced by the company that makes them, Adobe Firefly marked. Zero is the ordinary case here. Recorded 2026-09-22.Rows carrying an announced end dateGemini API5 announced5 announcedAmazon Bedrock3 announced3 announcedMicrosoft Foundry2 announced2 announcedAdobe Firefly1 announced1 announcedfal1 announced1 announcedinvideo AI1 announced1 announcedLuma1 announced1 announcedHailuo AI0 announced0 announcedKling AI0 announced0 announcedLTX Studio0 announced0 announcedPika0 announced0 announcedPixVerse0 announced0 announcedRunway0 announced0 announcedSceneMixer0 announced0 announcedVidu0 announced0 announcedWan-AI0 announced0 announced
Fig. 3 Per entry, how many of its rows carry a date announced by the company that makes them, Adobe Firefly marked. Zero is the ordinary case here. Recorded 2026-09-22.
Announced end dates behind each entry, with Adobe Firefly marked. Recorded 2026-09-22.
EntryRows with an announced end
Adobe Firefly1 announced
Amazon Bedrock3 announced
fal1 announced
Gemini API5 announced
Hailuo AI0 announced
invideo AI1 announced
Kling AI0 announced
LTX Studio0 announced
Luma1 announced
Microsoft Foundry2 announced
Pika0 announced
PixVerse0 announced
Runway0 announced
SceneMixer0 announced
Vidu0 announced
Wan-AI0 announced

Inclusion rule. Counted only where the vendor that makes the model has announced a date in public. A date reported by press coverage alone is not counted. Order. Alphabetical by entry name.

2Naming a model against a tier makes a withdrawal expensive to hide

Most plan tables name models once and leave a reader to guess which plan reaches which. Here the partner names sit inside the tier descriptions, so the page answers a sharper question: not what is available, but what this particular subscription buys. If one of those partner lines goes, the tier it was named in has visibly lost something, and the page has to be edited to say so.

That is a stronger position for a customer than an undifferentiated menu, and it is worth separating from the question of whether the models are good. A tier that names its engine can be held to the naming. A tier that promises premium video cannot.

What is lost when a partner is named without a versionA retirement notice is issued against a numbered version, never against a company. A row that records a partner's name therefore cannot be matched to any announcement, and will keep reading correctly after the engine behind it has been replaced.How is the partner model named on the plan?With a version numberMatchableThe string can be searched in the maker'sown deprecation table.Company name onlyUnmatchableSurvives a swap unchanged, so the pagestays true and stops being informative.Why version strings are copied verbatim here
Fig. 4 Both rows are accurate records of the page; only one of them can be checked against a maker's calendar.

3Partners named without a version are a different kind of row

Three partners appear on this page as company names rather than as model versions. A company name cannot be matched against a retirement notice, because retirement notices are issued against versions: a maker does not withdraw itself, it withdraws a numbered line. So those rows record what the page says and nothing more, and they are the rows most likely to keep reading correctly after the underlying model has been replaced.

One of those partners is itself an entry in this register with its own house lines and its own licensed half, which is worth reading side by side: see which models Runway carries. A model can therefore reach a customer through two resellers at once, each describing it at a different level of precision, which is exactly the situation where a dated reading beats a current claim.

4Read column by column

This register reads Adobe Firefly along named replacement, default tier and ending early. One page each.

  • Named replacement — partner models are gated by tier, so a replacement can arrive as a plan change
  • Default tier — the plan tier decides which models are reachable, so the default is whatever was bought
  • Ending early — a tier restructure ends access with nothing retired and no lifecycle page involved

5Sources

Menu taken from the plan comparison page on adobe.com, 2026-09-22. Any end date beside a model comes from whoever makes it, and is listed on the calendar.

  • 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
  • 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