LLMSwaps

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

The same unmarked table, published twice

Two entries reached the same arrangement without coordinating: house models and licensed models on one table, in the same type, with nothing marking which is which. A reader has to already know which maker each name belongs to, and the two halves fail on different companies' decisions. As of 2026-09-22.

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 entryRunwayLumaWhat the table listsWhat the table lists — Runway: Credit conversions per modelWhat the table lists — Luma: Plan coverage per modelIs the licensed half mark…Is the licensed half markedIs the licensed half marked — Runway: No marking on any rowIs the licensed half marked — Luma: Only in the plan wordingOwn generations listedOwn generations listed — Runway: Two house lines, video and editingOwn generations listed — Luma: Two house generationsWho ends a licensed rowWho ends a licensed row — Runway: That model's makerWho ends a licensed row — Luma: That model's makerIs the news route describ…Is the news route describedIs the news route described — Runway: Nothing publishedIs the news route described — Luma: Nothing published
Fig. 1 Filled where the vendor has announced something in that column, hollow where it has not.
How each entry presents the mixture of its own models and other makers'. Recorded 2026-09-22.
On this pointRunwayLuma
What the table listsCredit conversions per modelPlan coverage per model
Is the licensed half markedNo marking on any rowOnly in the plan wording
Own generations listedTwo house lines, video and editingTwo house generations
Who ends a licensed rowThat model's makerThat model's maker
Is the news route describedNothing publishedNothing published

Inclusion rule. Both cells on a row come from the entry's own priced pages. Product announcements naming models that never reach a priced page are not counted. Order. What the table lists first, then how the mixture is presented.

1An arrangement reached twice is a habit, not a policy

Two companies of different sizes, selling in different units, ended up presenting the same mixture the same way. That suggests it follows from how pricing pages get written rather than from a decision anybody defended.

Habits are worth recording because they change without announcements. Nothing prevents either page from marking its licensed rows tomorrow, and nothing obliges it.

An arrangement reached twice is a habit, not a policyTwo companies of different sizes, selling in different units, ended up presenting the same mixture the same way. That suggests it follows from how pricing pages get written rather than from a decision anybody defended.A house rowA licensed rowEnds whenThis seller decidesAnother maker decidesArrives asA product decisionAn edit passed downstreamMarked on the pageNoNoWho to askThe sellerSomebody you never dealt withMarking the licensed rows would tell a reader which names to watch at the maker
Fig. 2 Nothing prevents either page from marking its licensed rows tomorrow, and nothing obliges it either.

2Two halves, two different endings

A house line goes when the company selling it decides. A licensed line goes when somebody else does, and arrives here as an edit rather than as news. Presenting them identically hides which kind of ending a reader is exposed to.

One of the two pages at least acknowledges the mixture in its plan wording, which is a sentence rather than a marking. The register records it as an acknowledgement.

3What a marked table would change

Nothing about the risk, and everything about whether a reader can see it. Marking licensed rows would let a production know which names to watch at the maker rather than at the reseller.

That is the habit both entries make harder, and it is the one the aggregation question recommends regardless.

  • Models carried
    Gen-4.5 and Aleph 2.0 in house, plus Kling 3.0 and three Seedance variantsnamed beside credit conversionsRunway, pricing page / recorded 2026-09-22
  • How the plan describes the menu it sells
    Plans are described as covering Luma models alongside models from other makersLuma, plans and pricing / recorded 2026-09-22

4Sources

Both readings come from the pages the entries publish themselves: Runway and Luma, read 2026-09-22. The column being compared is Named replacement. Other pairs: Firefly and Kling AI, The Gemini API and Sora.