LLMSwaps

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

Which models Vidu carries

Vidu (vidu.com) names a current generation, Q3, and a separate real-time model, and prices the first in credits per five seconds. Earlier Q generations are not mentioned on the page. As of 2026-09-12.

Models named on Vidu's own pages, with any retirement date announced by the vendor that makes them. Recorded 2026-09-22.
ModelWhose modelAnnounced end
Vidu Q3In house, priced per five-second clipNo date announced
Vidu SIn house, presented as real-timeNo 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, Vidu 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. 1 How many rows each entry's own pages support, Vidu marked. Publishing more is not better; it is what makes a swap visible at all. Recorded 2026-09-22.
Models named per entry, with Vidu 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, Vidu 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. 2 Per entry, how many of its rows carry a date announced by the company that makes them, Vidu marked. Zero is the ordinary case here. Recorded 2026-09-22.
Announced end dates behind each entry, with Vidu 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.

2Two models doing different things is not two generations

It would be easy to read a two-row menu as a current model plus a fallback. It is not: one row is the general generation and the other is an interactive line built for latency rather than for fidelity. They are alternatives for different work, not a migration path, and a production that loses the first cannot continue on the second.

That distinction matters for how this register counts. Two named models here buy a reader less protection than two named generations elsewhere, and a count of models per entry is therefore a weak proxy for resilience. The register publishes the count because it is checkable, and says here why it should not be over-read.

Two models for different work is not a fallbackA general generation model and a real-time interactive one are alternatives for different jobs. Losing the first does not leave the second as a substitute, so a count of named models overstates how much protection a two-row menu provides.What does a second named model give a production?Two generations of one lineA place to standWork started on the older version cancontinue on it if it is kept.Two models for different jobsNo continuityDifferent output entirely, so the seriescannot simply move across.Why model counts are a weak proxy
Fig. 3 The register publishes the count because it is checkable, and says on this page why it should not be read as resilience.

3Pricing per clip length pins the model to the invoice

Quoting a credit price against a five-second clip has the same side effect as a per-second rate: it makes the model a billable unit rather than a background implementation detail. When a vendor charges by the model, a swap has to be reflected somewhere a customer can see, because the price list is the place the swap shows up first.

The opposite arrangement is visible at fal, which prices each model separately with no plan at all, and at the plan-based entries where one subscription covers everything and no line item moves when the menu does.

4Read column by column

This register reads Vidu along named replacement and default tier. One page each.

  • Named replacement — a current generation and a real-time line on the page, with earlier generations unaddressed
  • Default tier — a current generation and a real-time line, with neither marked as the starting one

5Sources

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

  • Models carried
    Vidu Q3, with Vidu S presented as a real-time modelcurrent generation onlyVidu, home page / recorded 2026-09-22
  • Whether Q1 and Q2 are still offered
    No date announced (as of 2026-09-12)not statedVidu, home page / recorded 2026-09-22