Generations doing the job of states
Two generations sit on one plan and are promoted differently, so current and previous end up doing the work of lifecycle labels. Neither is published as a condition, nothing says what happens when a third generation arrives, and promotion order can change without any retirement taking place. As of 2026-09-22.
| What the page is asked | What Kling AI publishes | What that leaves open |
|---|---|---|
| How many states are named | None published as conditions | Generations are listed as plan benefits |
| What functions as a state | Which generation is promoted as current | A placement rather than a declaration |
| Is the older line labelled | It appears as a benefit, unlabelled | Not marked legacy or previous on the page |
| What happens at the next generation | Not described anywhere | So the pattern cannot be extrapolated |
Inclusion rule. A state counts when the entry publishes the label itself. A marketing word such as new or classic is not a lifecycle state and does not fill a row. Order. The absence first, then what stands in for it.
1Promotion order looks like a lifecycle and is not one
Readers naturally translate promoted and still listed into current and legacy, because those are the words the rest of the software industry uses. Nothing on this page performs that translation, and the register declines to do it either.
The difference matters when a third generation ships. A published state system would say what happens to the oldest line; a promotion order says only which two are being sold hardest.
2Bundling makes the implied states cheap to use
Because both generations come with one membership, a production can act on the implied states without buying anything extra: stay on the older line, or move. That is more than most entries in this column allow.
It is also revocable at the level of a page edit. The arrangement is convenient now and carries no statement about later, which is the pattern recorded across this entry's other readings.
3What a published state would have added
One sentence saying the previous generation remains available until a stated date would convert the whole arrangement from a menu into a plan. Nothing prevents it and nothing here does it.
Two platforms in this register do publish exactly that kind of sentence, and both sell to developers. The notice question sets out why the commitment appears on one side of the market and not the other.
4Sources
Read from the membership plans on kling.ai, 2026-09-22. The whole entry is on Kling AI, and the column it sits in is on Lifecycle states. Same column, other entries: Wan-AI, Amazon Bedrock.