A pilot brought to life, against a structure repeated to a schedule
One page gives developing characters, story arcs and episode boards and then bringing the pilot to life as a use of its board. The other describes repeatable episode structures the user builds in order to publish on an ongoing schedule. One stops at episode one; the other starts at episode two. As of 2026-09-22.
| Point at issue | Luma Agents | Crano AI |
|---|---|---|
| The unit described | A pilot | A repeatable structure |
| Who does the structuring | The board, with the user on it | The user, building a template |
| What is never mentioned | Episodes after the first | Dividing an existing script |
Inclusion rule. Neither page describes splitting a text. Both are recorded as publishing something because each names a real object, and the objects sit on opposite sides of the first episode. Order. The page that ends at a pilot first, then the page that begins after one.
1The pilot is the episode with no continuity obligations
Nothing has to match in a first episode. No face has drifted, no room has changed shape, and the audience has no memory to contradict. Every product in this market can make a pilot, and this file exists because of what happens at episode nine.
Naming the pilot as the milestone is honest about scope. It also means the column's actual question, what happens across a run, is unanswered on that page.
2A template answers the run and skips the source
Repeatable structures are about the second, tenth and fortieth instalment: a shape to pour each new story into so the crew can work to a cadence. That is closer to how a serialised channel is really operated than any single act of creation.
What it does not do is divide the novel somebody arrived with. A template is not a split, and a reader holding a finished script gets no help from it.
3Together they show what this column is missing
Between a pilot and a template there is a gap: reading a long text and deciding where twenty-four episodes begin and end. Two vendors on this file publish a ceiling for that work and a handful describe the operation; most of the column describes something adjacent to it.
Recording the adjacency rather than scoring it keeps the column usable. A buyer needs to know which adjacent thing they are being offered.
4The wording both sides published
- Script to episodesDeveloping characters, story arcs and episode boards and then bringing the pilot to life is given as a use of the boardboards and a pilot
- Script to episodesRepeatable episode structures are described as something the user builds in order to publish on an ongoing schedulea shape rather than a split
5The same column, read for a third tool
On the split into episodes, SceneMixer's published page puts it in one line: One upload analysed into characters, scenes, props and episodes
. Its reading here, One upload read once, with the episode structure falling out of it, sets out what that line settles for a series and what it leaves to a production run.
6Sources
Read from the product page at lumalabs.ai and the short-drama generator page at crano.ai, both checked 2026-09-22. The full column is on script to episodes; the single readings behind this contrast are Luma Agents and Crano AI. Other contrasts filed here: StoryShort and AI Drama Generator, invideo AI and Showrunner Studio, AI Dramas and SceneMixer.