LLMSwaps

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

When the default is the entire menu

Every priced plan names the same house model, so there is no selector and nothing to default to. The register still records a default here, because from a customer's side the behaviour is identical: work arrives from a model nobody chose. Plans separate by resolution and features instead. 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 entryWhat Pika publishesWhat PikapublishesWhat that leaves openWhat that leavesopenIs a starting tier statedIs a starting tier stated — What Pika publishes: It follows from one model on every planIs a starting tier stated — What that leaves open: No statement about defaults is neededWhat distinguishes the plansWhat distinguishes the plans — What Pika publishes: Resolution and feature accessWhat distinguishes the plans — What that leaves open: Not the model, which is constantCan a customer choose another engi…Can a customer choose another engineCan a customer choose another engine — What Pika publishes: No alternative model is offeredCan a customer choose another engine — What that leaves open: So there is nothing to select away toWhat a version change would reachWhat a version change would reach — What Pika publishes: Every plan simultaneouslyWhat a version change would reach — What that leaves open: There is no unaffected tier to move to
Fig. 1 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 announcementWhat Pika publishes3 of 4What that leaves open3 of 4
Fig. 2 How many entries carry an announcement in each column. Silence is the common case and is recorded as such.
What a single-line menu settles about the starting engine. Recorded 2026-09-22.
What the page is askedWhat Pika publishesWhat that leaves open
Is a starting tier statedIt follows from one model on every planNo statement about defaults is needed
What distinguishes the plansResolution and feature accessNot the model, which is constant
Can a customer choose another engineNo alternative model is offeredSo there is nothing to select away to
What a version change would reachEvery plan simultaneouslyThere is no unaffected tier to move to

Inclusion rule. Filled when the entry's own public page says which model a new project starts on, or when a single-model menu makes the answer follow from the list having one line. Order. What follows from the menu first, then what the plans actually vary.

1A default by absence behaves like a default

Nothing here decided which engine a new customer gets, because there was never a second option. The outcome is the same as a stated default and the mechanism is different, which is why the cell is filled with an explanation rather than a name.

The practical reading is that every customer is on the same exposure. No subset of this user base is insulated from a version change by having selected something else.

A menu with one line has no detection surfaceWhere tiers name different models, a reader can watch the names and see a swap. Where every plan names the same model, a version change leaves no trace on the page, so the plan table stops being evidence of anything.Tiers naming modelsOne model everywherePlans differ byThe engineResolution and featuresA swap shows asA changed nameNothing on the pageCustomers affectedWhoever used that tierAll of them, at onceFallback listedSometimes an older lineNoneWhy a single-line menu is a narrower and deeper risk
Fig. 3 Same name in every row: a reader comparing two readings would find the page unchanged.

2Plans that vary by resolution hide the engine question

Because the model is constant, a plan table here says nothing about which engine produced anybody's work. A reader comparing plans is comparing output sizes and features, not lifecycles.

That also removes the plan table as a detection surface. Where tiers name different models, a reader can watch the names; here the same name sits in every row, so a version change would leave no trace on the page.

3One schedule and no shelf

Owning the model means this company controls when it changes, which removes the inherited calendars every aggregating entry carries. It also means no previous generation is listed to finish a season on.

The register keeps that trade in the succession reading for this entry. Narrower risk, and nothing behind it when the risk arrives.

  • Models carried
    Pika 2.5 onlyin house onlyPika, pricing / recorded 2026-09-12

4Sources

Read from the pricing page on pika.art, 2026-09-22. The whole entry is on Pika, and the column it sits in is on Default tier. Same column, other entries: Hailuo AI, Vidu.