Which models Luma carries

Luma (lumalabs.ai) names two of its own Ray generations and around nine licensed entries on one plan table, and describes what a plan covers as its own models plus other makers rather than as a list that will stay put. As of 2026-09-12.

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

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.

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.

2The plan wording is doing real work here

Describing a plan as covering its own models plus other makers' is not filler. It is the closest thing on the page to a statement about volatility: the licensed half is a set the seller curates, and a curated set is one that can be edited. What the wording does not do is say who edits it, on what notice, or whether a subscriber is told at all.

Luma and third-party image and video models

Luma, plans and pricing

Read next to the plan table, the effect is that two generations of one house model are the only lines whose future this company controls. Everything else on the table belongs to a maker with its own schedule, and in one case that schedule has already produced dated shutdowns: earlier Veo versions were given a shutdown date on the Gemini API deprecations page.

3Two house generations is the pattern worth watching

Keeping Ray3.2 alongside Ray3.14 does the same thing as keeping two Kling entries: it lets work started under one version continue under it. No policy on the page promises that, which makes it a state rather than a commitment, and states get tidied when a table gets long.

A nine-name licensed half also creates a subtler risk than withdrawal, which is substitution. If one licensed entry is replaced by its own successor under a similar label, the plan table still reads correctly while the output changes. That is the failure this register cannot detect from a page read, and it is why each row here carries the date it was read rather than a claim about what is running now. The same problem is discussed on Adobe Firefly, where partner names appear without version numbers in places.

4Read column by column

This register reads Luma along named replacement and default tier. One page each.

• Named replacement — two house generations on one table, with the licensed half belonging to six other makers
• Default tier — a plan table of house and licensed lines with no starting one identified

5Sources

Menu taken from the plans and pricing page on lumalabs.ai, 2026-09-22. Any end date beside a model comes from whoever makes it, and is listed on the calendar.

• Models carried
  Ray3.2 and Ray3.14 in house, plus Veo 3.1, three Kling entries, MiniMax H3 and three Seedance variantshouse and licensed on one tableLuma, plans and pricing / recorded 2026-09-22
• How the plan describes the menu it sells
  Plans are described as covering Luma models alongside models from other makersLuma, plans and pricing / recorded 2026-09-22