Carrying one model against carrying several
Pika names one model, Pika 2.5, across every plan. Kling AI sells two generations at once, with 3.0 and 3.0 Omni promoted and VIDEO 2.6 still appearing as a plan benefit. As of 2026-09-12.
| Entry | What is published | Detail |
|---|---|---|
| Pika | One house model | Pika 2.5 on every plan |
| Kling AI | Two generations live | 3.0 and 3.0 Omni, plus VIDEO 2.6 listed |
| Neither | No end date announced | Nothing published for any line |
Inclusion rule. Models named on the app's own priced pages. A model named only in documentation or a blog post is not counted. Order. By how many lines the app keeps live.
1Two generations at once looks like a migration path and is not described as one
An older generation still listed as a plan benefit has the practical effect of a fallback: work started on it is not forced forward the day a newer line ships. Nothing published says that is the intent, and a benefit list can be edited without an announcement.
So this register records two lines as live and records no policy, because there is none to record. A reader hoping for a commitment is looking at a table that cannot carry one.
2A single line removes one risk and concentrates another
One house model means no inherited retirement calendar and no confusion about what a plan buys. It also means that when that line moves, there is nothing listed to fall back to, and every project on the platform moves at once.
Neither shape is safer in general. Which one suits depends on whether a production would rather manage several schedules or have no choice about one.
3What neither app publishes is the same thing
No end date for any line, and no statement about whether output generated on a version stays reproducible after that version changes. The second is the question that decides whether a series can be finished on the model it started on, and it is unanswered across this entire register.
It is also the question a vendor could answer most cheaply, since it is a statement about their own engineering rather than a promise about the future.
4Sources
Dates come from the vendor that makes the model; menus come from the app, and both are linked on the calendar. Read 2026-09-12. What counts as a date is on sourcing. Nearby: Naming versions, Blank dates, Who names a successor.