LLMSwaps

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

Which models fal carries

fal (fal.ai) sells access to other companies' video models one model at a time, with a price against each name and no subscription wrapping them, and states that video is billed by output unit rather than by time in the tool. 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 endWan 2.5Wan 2.5 — Whose model: Another vendorWan 2.5 — Announced end: No date announcedKling 2.5 Turbo ProKling 2.5 Turbo Pro — Whose model: Another vendorKling 2.5 Turbo Pro — Announced end: No date announcedVeo 3Veo 3 — Whose model: Another vendorVeo 3 — Announced end: Earlier Veo versions shut down 30 June 2026OviOvi — Whose model: Another vendorOvi — 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 fal's own pages, with any retirement date announced by the vendor that makes them. Recorded 2026-09-22.
ModelWhose modelAnnounced end
Wan 2.5Another vendorNo date announced
Kling 2.5 Turbo ProAnother vendorNo date announced
Veo 3Another vendorEarlier Veo versions shut down 30 June 2026
OviAnother vendorNo 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, fal 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, fal marked. Publishing more is not better; it is what makes a swap visible at all. Recorded 2026-09-22.
Models named per entry, with fal 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, fal 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, fal marked. Zero is the ordinary case here. Recorded 2026-09-22.
Announced end dates behind each entry, with fal 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.

2Per-model pricing makes the register's job easy and the customer's harder

An entry that prices each model individually publishes the cleanest menu in this register: there is no tier to hide behind, and a model that leaves has to leave the price list. That is the best case for anyone trying to match an announcement to an invoice.

It is also the arrangement with the least cushioning. A subscription can absorb a withdrawal by pointing the same plan at a different engine; a price list cannot, so the customer feels the change directly, in code, on the day. Neither arrangement comes with a stated notice period at this entry.

A per-model price list against a subscriptionCharging for each model separately means a withdrawal has to appear on the price list, which is the clearest possible signal. It also removes the cushioning a plan provides, because there is no tier that can be quietly pointed at a different engine.Priced per modelSold as a planWhere a swap shows upOn the price listNowhere, if the tier name holdsWho absorbs the changeThe customer, in codeThe seller, by re-pointing the tierHow soon it is noticedThe same dayWhen the output shiftsSchedules the seller ownsNone of themNone of themTwo billing shapes, two failure modes
Fig. 4 Neither arrangement comes with a stated notice period; they differ in how fast the customer finds out.

3An access layer holds none of the schedules it resells

Every line here was made by somebody else. One of them has already had sibling versions given dated shutdowns by their maker, which is recorded on the Gemini API entry, and that is the shape of how a date reaches a customer of this kind of service: not from the service, from three companies upstream.

The register keeps those two readings apart on purpose. What this page says it sells is one fact with one date. What the makers say about the life of each line is another, and the calendar is where the second kind is collected. A reader who only watches the access layer will see a menu that looks stable until the moment it is not. One more entry here works the same way at a much larger scale: Amazon Bedrock.

4Read column by column

This register reads fal along stored work and default tier. One page each.

  • Stored work — a meter per output unit rather than a library, so delivery is the whole relationship
  • Default tier — each call names a model and its own price, so there is no default to have

5Sources

Menu taken from the pricing page on fal.ai, 2026-09-22. Any end date beside a model comes from whoever makes it, and is listed on the calendar.

  • Models carried
    Wan 2.5, Kling 2.5 Turbo Pro, Veo 3 and Ovi, each priced individuallypriced per model rather than per planfal, pricing page / recorded 2026-09-22
  • How the meter works
    Video models are billed by output unit, per second or per video depending on the modelquoted from the pagefal, pricing page / recorded 2026-09-22