An aggregator inherits somebody else's calendar
Two apps here carry models made by other companies: one aggregates six makers, the other mixes two house generations with licensed Veo. Every licensed line on those menus runs on a schedule the app does not control. From 2 source pages, read 2026-09-12; no maker pays to be listed.
| Entry | What is published | Detail |
|---|---|---|
| invideo AI | Six makers aggregated | Veo, Sora 2, Kling, Wan, Pixverse and others |
| LTX Studio | Two house plus licensed | LTX-2.5 and 2.3 in house, Veo 3.1 licensed |
| Single-maker apps | One schedule | House models only |
Inclusion rule. Apps are read from the page naming what they carry. A model named on a priced page counts; a model shown in a launch post does not. Order. By how many makers' schedules the app carries.
1Six makers is six calendars and none of them is yours
An app carrying one house model has one schedule and controls it. An app aggregating six has six, controls none, and will usually learn about a retirement at roughly the same time its customers do. Neither arrangement is better; they fail differently and they should be planned for differently.
The aggregator's advantage is real too: when one maker retires a model, five others are still there. A single-model app has nothing to fall back to.
2Sora 2 is still on one of these menus
The one model in this register with an announced end date appears on an aggregator's list. That is not an error on anyone's part: the API runs until its end date and the app is entitled to sell access to it until then.
It is the clearest illustration of why this register keeps app menus and model dates on separate pages. They go out of step by design, and the gap between them is exactly what a production needs to see.
3Mixing house and licensed models splits the exposure
One app here does both: models it makes and a model it licenses. The house lines carry the app's own schedule, the licensed line carries somebody else's, and nothing on the page marks which is which for a reader who does not already know.
This register records the composition because that distinction determines who a production would have to ask when a line disappears.
4Production that outlasts a model
Model end dates touch “Aggregators”; SceneMixer's guides describe how its pipeline treats the models it runs:
The Seedance 2.0 tiers render segments up to 15 seconds; use a Seedance 2.5 or Wan tier for 30-second takes.
SceneMixer, Seedance 2.0 Fast — “Does Fast render 30-second takes?” (read 2026-10-13)
Doubao Seed 2.1 Turbo is the tier every account uses for text work until you change it: it reads the script, writes with AI when you ask, and generates each episode’s storyboard, at 50% of the base text rate.
SceneMixer, Doubao Seed 2.1 Turbo: the default text tier (read 2026-10-13)
5Sources
Dates come from the company that makes the model or the platform that serves it; 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: One or many, Naming versions, Blank dates.