A menu of one against a menu gated by plan
Both entries answer the default question without stating a default. On one, every plan names the same house model, so there is nothing to choose. On the other, partner models are named tier by tier, so what a project can reach is decided at the checkout rather than in a setting. From 2 source pages, read 2026-09-12 to 2026-09-22; no maker pays to be listed.
| On this point | Pika | Adobe Firefly |
|---|---|---|
| How the answer is settled | One model on every plan | The tier the subscription bought |
| What distinguishes the plans | Resolution and feature access | Which partner models are named |
| Can the answer change | Only if the single line moves | By a tier change, with nothing retired |
| Is the mapping published | Not needed; there is one model | Yes, tier by tier |
| Whose models are involved | One house line | A house line plus several partners |
Inclusion rule. Both cells on a row come from the entry's own priced pages. Models available in other products from the same company are not counted. Order. How the answer is settled first, then what can change it.
1Two stable arrangements, stable for different reasons
A single line is stable because there is nothing to switch. A tier gate is stable because the subscription fixes the answer until somebody changes plan. Both remove the unstated setting that most entries here leave unexplained.
The difference is who can move it. One answer moves when the maker ships a new version; the other moves when a pricing team restructures a plan.
2A tier gate creates a second way to lose a model
Everywhere else in the register a model becomes unreachable because it was retired. On a tier-gated menu it can also become unreachable because the tier moved, and the model continues to exist one plan above.
Identical effect for a production, and no lifecycle document is involved. The ending early reading covers which document would announce it, and the answer is a pricing page.
3Publishing the mapping is what makes either legible
One entry publishes which partner model sits in which plan, which is more detail than most entries give. The other needs no mapping, because a one-line menu is self-describing.
Both are therefore readable before paying, which separates them from the entries where the starting engine is simply unstated. The default tier column records which entries manage that.
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.
- Which tier reaches which modelVeo 3.1 Fast and Kling 3.0 are named in the Premium tier, Kling 2.5 Turbo in Pro Plus
5Sources
Both readings come from the pages the entries publish themselves: Pika and Adobe Firefly, read 2026-09-22. The column being compared is Default tier. Other pairs: Kling AI and Hailuo AI, Luma and Vidu.