LLMSwaps

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

Default tier: the model most work gets made on

The tier a project gets without anyone choosing reaches more delivered work than any tier on the selector. One app in this register names its starting model and version on the price list. An app selling a single house model defaults by having no alternative. As of 2026-09-12.

Three shapes a starting tier comes inAn app either names the model a new project starts on, sells a single model so the question never arises, or lists tiers without saying which one an untouched project uses. Only the first can be watched from outside.How the starting model is publishedNamed defaultModel and version printed beside the rate, so a move showsMenu of one lineA single house model, defaulting by having no alternativeUnstatedTiers listed without saying which one a new project getsOnly the first is checkable from a public page
Fig. 1 The shape decides whether a customer can notice the day the starting model changes.
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 entryDefault tierWhat that leaves a production withWhat that leaves aproduction withSceneMixerSceneMixer — Default tier: Wan 3.0 at 480PSceneMixer — What that leaves a production with: Named on the price list, so a change is checkablePikaPika — Default tier: One house model across every planPika — What that leaves a production with: Defaults by having no alternativeKling AIKling AI — Default tier: Not statedKling AI — What that leaves a production with: Two generations sold together, neither marked as the startLTX StudioLTX Studio — Default tier: Not statedLTX Studio — What that leaves a production with: House and licensed models listed side by sideinvideo AIinvideo AI — Default tier: Not statedinvideo AI — What that leaves a production with: Several makers aggregated under one subscription
Fig. 2 Filled where the vendor has announced something in that column, hollow where it has not.
Entries with an announcementHow many entries carry an announcement in each column. Silence is the common case and is recorded as such.Entries with an announcementDefault tier2 of 5What that leaves a production wi…What that leaves a production with4 of 5
Fig. 3 How many entries carry an announcement in each column. Silence is the common case and is recorded as such.
Which model an entry runs when nobody touches the selector. Recorded 2026-09-12.
EntryDefault tierWhat that leaves a production with
SceneMixerWan 3.0 at 480PNamed on the price list, so a change is checkable
PikaOne house model across every planDefaults by having no alternative
Kling AINot statedTwo generations sold together, neither marked as the start
LTX StudioNot statedHouse and licensed models listed side by side
invideo AINot statedSeveral makers aggregated under one subscription

Inclusion rule. A cell is filled when the app's own public page says which model a new project starts on, or when the app sells one model and the answer follows from the menu having a single line. Order. Entries that state a starting model first, then those that do not.

1The default is where most of the work is made

A tier selector is something a user touches once and then forgets. Whatever the product generates without being asked is what most projects run on, so a change to that one setting reaches more delivered work than a change to anything else on the list. That is why the starting model is kept apart from the menu.

It is also why a default has to be named to be worth anything. A product that lists every tier but not the starting one has published a menu without publishing the thing most of its output actually came from.

2Naming it is what makes a swap checkable

One price list here prints a model and version beside each rate, which turns the starting tier into a specific named thing rather than a house label. When that name moves, a reader comparing two readings of the same page can see it, and the change carries the date of the reading rather than being inferred from output that started looking different.

Where a product presents house tiers instead, the starting model is doing exactly the same job with no way to watch it. The cell records that as unstated, which is a fact about the page and not a judgement about the product.

3A menu of one line defaults by accident

An app selling a single house model has no selector and therefore nothing to default to, so every plan runs on the same engine. It is recorded as a default because it behaves like one from the customer's side: the work arrives from a model nobody chose.

The difference shows at replacement time. An app with several tiers can move its starting one and leave the old model selectable, while an app with a single line can only replace it, and the whole customer base moves on the same day.

4This column, entry by entry

The default tier column read one entry at a time, wherever that entry has published something here or falls silent in a way the others do not. Ordinary blanks stay on the table above.

  • SceneMixer — the starting tier is named on the price list, so a change there is checkable
  • Pika — one house model on every plan, so the default is the whole menu
  • Hailuo AI — one generation promoted on the home page, which makes promotion the default mechanism
  • Vidu — a current generation and a real-time line, with neither marked as the starting one
  • Kling AI — two generations on one plan, with the newer pair promoted but nothing marked as default
  • Luma — a plan table of house and licensed lines with no starting one identified
  • Runway — a credit table that prices every line and names none of them as the starting one
  • Adobe Firefly — the plan tier decides which models are reachable, so the default is whatever was bought
  • fal — each call names a model and its own price, so there is no default to have
  • Microsoft Foundry — a deployment names a version, so a default would defeat the point of the schedule
  • Amazon Bedrock — a request names a model identifier, so the default lives in the customer's own code
  • Gemini API — an alias moves and a pinned identifier does not, and the choice is the caller's
  • Wan-AI — you choose which repository to download, so the default is whichever copy you kept
  • Default tier
    Wan 3.0 at 480Pwhat a new project getsSceneMixer, price list / recorded 2026-09-12
  • Models carried
    Wan 3.0 at 480P, 720P and 1080P, plus MiniMax H3 and H3 Fastnamed per tierSceneMixer, price list / recorded 2026-09-12
  • Models carried
    Pika 2.5 onlyin house onlyPika, pricing / recorded 2026-09-12

5Sources

Values come from the page the entry is read on: vendor announcements for endings, app pages for menus, both linked from the calendar. What counts as a value is on sourcing. Read 2026-09-12. Other fields: Lifecycle states, Ending early. All of them: the field list.