A bundled subscription against models priced one by one
Both entries sell other companies' models and neither states a default. On one they are bundled into a subscription, so which engine runs is unstated and unpublished. On the other each model carries its own price and nothing runs unless a request names it. From 2 source pages, read 2026-09-12 to 2026-09-22; no maker pays to be listed.
| On this point | invideo AI | fal |
|---|---|---|
| What a customer buys | A subscription covering six makers | Output from a named model |
| Who chooses the engine | Unstated on the page | The caller, every time |
| Is a version given | Makers named, versions mostly not | Model names on the price list |
| Can the engine be identified later | Not from anything published | Yes, from the invoice |
| What a version change reaches | Unknowable from the page | Only callers naming that model |
Inclusion rule. Both cells on a row come from the entry's own priced pages. A maker counted here is one the entry itself names. Order. What a customer buys first, then who chooses, then what is recorded.
1A bundle hides the answer; a line item is the answer
Where six makers sit behind one subscription, nothing published says which produced a particular clip. Where each model is priced separately, the bill records it without anybody making an effort.
That is the single most useful difference in this column. Every explainer here ends by recommending a per-file record, and one of these two arrangements produces it automatically.
2Both inherit other companies' schedules
Neither entry makes the models it sells, so both are exposed to retirements decided elsewhere. One carries six makers' schedules with no versions; the other carries several with names on a price list.
Only the second lets a dated announcement be matched to a purchased line. The aggregation question sets out why that matching is the whole problem.
3Neither has a default to publish
One has none because a subscription does not expose the choice; the other has none because the choice is compulsory. The first is an absence of disclosure and the second an absence of the concept.
The register records them separately for that reason. The reading for the priced list explains why a caller's own string becomes the effective default.
4The same question, put to a third entry
| On this point | SceneMixer | Source |
|---|---|---|
| The default tier | Wan 3.0 at 480P | SceneMixer, price list |
| 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: invideo AI and fal, read 2026-09-22. The column being compared is Default tier. Other pairs: Wan-AI and fal, Foundry and Bedrock.