A tier that gates models against a plan that includes both
Both entries settle which engine a project reaches without publishing a default, in opposite ways. One gates partner models by tier, so the subscription decides. The other includes two generations on one membership, so nothing is decided and both remain available. From 2 source pages, read 2026-09-12 to 2026-09-22; no maker pays to be listed.
| On this point | Adobe Firefly | Kling AI |
|---|---|---|
| What decides access | The tier the subscription bought | Nothing; both generations are included |
| Is the mapping published | Yes, model by tier | Not applicable; there is no gate |
| Can access end without a retirement | Yes, by a tier change | Nothing published about removal |
| Whose models are involved | A house line plus partners | This maker's own two generations |
| Is either generation marked current | Partner models are named by tier | The newer pair is promoted |
Inclusion rule. Both cells on a row come from the entry's own published plan pages. A model reachable in the product but absent from the plan comparison does not fill a cell. Order. What decides access first, then what can change it.
1Gating and bundling both remove the unstated setting
Most entries in this column leave the starting engine unexplained. These two do not, because one answers it at the checkout and the other makes the question moot by including everything.
The cost is different. A gate makes access a commercial variable; a bundle makes it a product decision nobody has committed to keeping.
2One entry resells, the other makes
The gated menu mixes a house line with partner models, so part of its answer depends on other companies. The bundled menu is one maker's own generations, so the whole answer belongs to the company selling it.
That decides who a customer can usefully ask. On the bundled entry there is one party; on the gated one, the answer may belong to a maker the subscriber has never dealt with.
3Two ways to lose access with nothing retired
A tier restructure removes a partner model from a subscriber while the model continues to exist. A benefit list edit removes an older generation the same way. Neither event produces a retirement notice.
The register records both as page edits rather than as endings. The ending early column keeps every mechanism of that kind in one place.
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: Adobe Firefly and Kling AI, read 2026-09-22. The column being compared is Default tier. Other pairs: The Gemini API and Sora, invideo AI and Luma.