Which models Pika carries
Pika (pika.art) names one model on its priced pages, Pika 2.5, across every plan. It is the simplest entry in this register and the one with the least to track. As of 2026-09-12.
| Model | Whose model | Announced end |
|---|---|---|
| Pika 2.5 | In house, only model named | No date announced |
Inclusion rule. Models the app names on its own public pages. A model the app does not name is not listed, and an end date is recorded only when the vendor that makes the model has announced one. Order. As the app orders them on its own page.
1How many models each application names
| Entry | Rows it publishes |
|---|---|
| Adobe Firefly | 5 rows |
| Amazon Bedrock | 3 rows |
| fal | 4 rows |
| Gemini API | 5 rows |
| Hailuo AI | 1 row |
| invideo AI | 5 rows |
| Kling AI | 3 rows |
| LTX Studio | 4 rows |
| Luma | 6 rows |
| Microsoft Foundry | 2 rows |
| Pika | 1 row |
| PixVerse | 4 rows |
| Runway | 5 rows |
| SceneMixer | 5 rows |
| Vidu | 2 rows |
| Wan-AI | 5 rows |
Inclusion rule. Entries whose own pages name a model, a version identifier or a lifecycle state. House tier names with no model behind them are not counted. Order. Alphabetical by entry name.
| Entry | Rows with an announced end |
|---|---|
| Adobe Firefly | 1 announced |
| Amazon Bedrock | 3 announced |
| fal | 1 announced |
| Gemini API | 5 announced |
| Hailuo AI | 0 announced |
| invideo AI | 1 announced |
| Kling AI | 0 announced |
| LTX Studio | 0 announced |
| Luma | 1 announced |
| Microsoft Foundry | 2 announced |
| Pika | 0 announced |
| PixVerse | 0 announced |
| Runway | 0 announced |
| SceneMixer | 0 announced |
| Vidu | 0 announced |
| Wan-AI | 0 announced |
Inclusion rule. Counted only where the vendor that makes the model has announced a date in public. A date reported by press coverage alone is not counted. Order. Alphabetical by entry name.
2One model is a different risk profile, not a smaller one
An app carrying one house model has one schedule to manage and controls it. That removes the problem of inheriting another vendor's retirement calendar, which is the risk the aggregators in this register carry. It does not remove the problem of a version being replaced: a single model line still moves, and when it does there is no older generation listed to fall back to.
The pricing page draws the distinction between plans by resolution and by feature access rather than by model, which is why every plan names the same model. That is worth noting for anyone reading a plan table expecting the model to be the variable.
3What is not published
No end date, no notice period, and no statement about whether output generated on the current version remains reproducible after an update. None of the apps in this register publish the last of those, and it is the one that decides whether a season can be finished on the model it was started on.
Feature names on this vendor's pages move faster than model names do, which makes the model line look more stable than the product is. This register tracks the model line because that is what output depends on.
4Read column by column
This register reads Pika along named replacement and default tier. One page each.
- Named replacement — one house model on every plan, so there is no older line to fall back to
- Default tier — one house model on every plan, so the default is the whole menu
5Sources
Menu taken from the pricing page on pika.art, 2026-09-12. Any end date beside a model comes from whoever makes it, and is listed on the calendar.