One schedule against six, and no dates either way
These two entries mark the ends of the aggregation axis. One names a single house model on every plan and controls when it changes. The other names models from six makers and controls none of those decisions. Neither publishes a date or a successor, which is the point of reading them together. From 2 source pages, read 2026-09-12; no maker pays to be listed.
| On this point | Pika | invideo AI |
|---|---|---|
| Schedules in play | One, and it belongs to this company | Six, none of them this company's |
| If the model moves | Every plan changes at once | Five other lines remain on the menu |
| Fallback listed | None; there is one line | Whatever the other makers still offer |
| Who a customer can ask | The company that made it | A reseller who did not decide |
| Dates published | None | None, though one listed model has one |
Inclusion rule. Both cells on a row come from the entry's own published model pages. A date beside a model comes from whoever makes it and is recorded on the calendar. Order. Schedules first, then what happens when one moves.
1Fewer models is not automatically less risk
A single house line means one schedule to watch and no inherited dates, which is genuinely simpler. It also means nothing is left on the shelf when that line moves, so the whole customer base migrates on the same day.
An aggregated menu spreads the risk across six makers and keeps a working product when one of them retires something. What it loses is any authority over the decision.
2The consolation depends on what was built
Losing one of six models leaves a functioning subscription and a broken series, if the series was established on the line that went. Losing the only model leaves a broken subscription and the same broken series.
So aggregation helps the customer and does nothing for the production. That distinction is why this register tracks model lines rather than product features.
3One aggregated line already has an ending
One model on the aggregated menu carries a date published by its maker, and the menu still names it. Both statements are current and the register keeps them side by side.
Menus are marketing pages and they lag. The habit that survives both arrangements is checking the maker, which the aggregation question sets out.
4The same question, put to a third entry
| On this point | SceneMixer | Source |
|---|---|---|
| When a tier is withdrawn | When a tier is withdrawn, text and image work falls back to the default tier and video to the tier the episode last used if it is still listed, otherwise the default; the price shown is the tier that will run | SceneMixer, withdrawn tier guide |
Inclusion rule. SceneMixer's own statements that bear on the column this pair was chosen for. Order. The statement closest to the column first.
All of its readings are on the SceneMixer entry.
5Sources
Both readings come from the pages the entries publish themselves: Pika and invideo AI, read 2026-09-22. The column being compared is Named replacement. Other pairs: Pika and Adobe Firefly, Kling AI and Hailuo AI.