Which models Hailuo AI carries
Hailuo AI (hailuoai.video) puts one model name in front of a visitor, MiniMax H3, and says nothing anywhere on the page about the generations that came before it. As of 2026-09-12.
| Model | Whose model | Announced end |
|---|---|---|
| MiniMax H3 | In house, promoted as live now | 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.
2A launch page is a thin register source, and often the sole one available
This entry is read from a page whose job is to announce that something is live. That construction answers the question this register asks first, which model is named, and refuses the second, what happened to the last one. A page written to celebrate an arrival has no reason to mention a departure, so the absence here is structural rather than evasive.
The consequence for a production is concrete. Work generated under an earlier generation cannot be matched against anything published, because no page states whether that generation is still reachable, frozen, or gone. The row is therefore recorded with one model and a blank, and the blank is the finding.
3The same engine name appears in other registers here
This model is named on the pages of several other entries, which makes it one of the more widely resold lines tracked here: it appears in the plan tables of Luma and on the home page of PixVerse, alongside those companies' own generations. The maker's own site is the shortest of those pages and the least informative about lifecycle.
That inversion is common and worth stating plainly: a reseller with a long plan table often publishes more about a model than the company that built it, because the reseller has to explain pricing per model and the maker only has to explain why the new one is better. Neither publishes a withdrawal date.
4Read column by column
This register reads Hailuo AI along named replacement and default tier. One page each.
- Named replacement — one generation promoted on the home page, with no back catalogue mentioned
- Default tier — one generation promoted on the home page, which makes promotion the default mechanism
5Sources
Menu taken from the home page on hailuoai.video, 2026-09-22. Any end date beside a model comes from whoever makes it, and is listed on the calendar.
- Whether earlier Hailuo generations are still reachableNo date announced (as of 2026-09-12)not stated