AISeriesMaker

The plan limits behind an AI series

StoryShort's four-series ceiling, read against the sheet

StoryShort's pages describe an automated feed of short videos with voiceovers, background music and auto-posting, and they count series by plan: one on Starter and four on Ultra. A thirty-second video with AI images is put at about fifteen credits. From 10 source pages, read 2026-09-25 to 2026-10-25; no maker pays to be listed.

A ceiling counted in series, not in minutesOne plan names one series and another names four. Between the plan and the feed sit the rows the sheet does record: how many people share it, where the files live and what deleting does.One plan, two currenciesOnly footage countedwhat the sheet recordsMinutes per month, Scenes per projectBoth listsstated in both waysStorage per plan, Seats andcollaboratorsOnly channels countedwhat only the plan namesOne series on Starter, Four on UltraThe sheet quotes whichever the page states
Fig. 1 The same plan page, read for channels instead of footage.

1What the sheet already records

Nine seat rows from the sheet, ordered from team arrangements down to one user per plan, then the storage row that decides where a run of series actually lives.

2What StoryShort's pages state

StoryShort's pages describe an automated feed of short videos with voiceovers, background music and auto-posting. The word series is counted by plan: one series on Starter, four on Ultra. Costs are stated per video rather than per month — about fifteen credits for a thirty-second video with AI images, about a hundred and ten for something called an AI movie.

Counting the product in series rather than in minutes is its own kind of cap, and the sheet quotes it in the maker's words. Four automated feeds is a different ceiling from 110 minutes a month: it limits how many channels can run at once rather than how much footage they may make, and the two numbers would plan very different years.

3A ceiling counted in series

The sheet has no limit field for channels, so StoryShort's plan names do not appear in its nine columns. What the sheet does record is the machinery a run of feeds needs: seats, storage and recovery. Its seat rows run the whole range. Frameo gives one credit pool to unlimited users with no seat fees; OiiOii includes team seat management with up to five groups; Krea includes up to fifty seats in its business workspace; Higgsfield includes two to nine seats on one team plan and five to fifteen on the next.

Further down the same column sit arrangements that count people the other way. Topview's team plan is counted per seat, with seat management; Heygen adds team members per seat on its business tier; LTX Studio invites three collaborators per project; Luma gives guest collaborators edit access; Synthesia states one editor with three guests on one tier and five on the next; and Morphic's row is the plainest of all — one user only on its Free, Basic and Standard plans, with extra users sold on Pro and Max.

4Where a run of series lives

Storage is the second half of the same question, and the sheet's rows again differ in shape rather than size. Descript states cloud storage set per plan, from 5 GB up to 2 TB; Invido puts 200 GB on one plan; Kapwing offers 5, 200 or 800 GB by plan; Pippit states up to 500 GB of team storage. AI Drama Generator's row is a clock rather than a size: 30 days of cloud storage on the free plan, after which the sheet says nothing about what happens.

Keeping and deleting are the third piece. Pippit keeps deleted drafts and videos recoverable for up to thirty days; Kapwing keeps project files for three days on its free plan and for the length of the subscription on paid ones; Luma and SceneMixer are both plain that deleting is permanent, with the sheet recording no recovery step for either. A season's runs of series need the first kind of row; a shared drive needs the second stated clearly.

5What the counted material keeps beside the plan

One family carries the biggest comment tally in the material collected for this column: Sora, counted at 11,729 posts and 4,662 mentions, with quotations asking what creators do now and whether anyone will miss it. Runway's share of the posts read in one subreddit is 1.4%, and no post count is kept for it, so that cell is left empty rather than estimated.

None of that measures a plan, and the sheet is honest about the boundary: community counts describe talk, the register describes pages, and a four-series ceiling is a fact of the second kind only. SceneMixer's own row below is a fact of the same kind — a figure measured across the jobs the site finished, quoted with its window. Each table carries its makers' wording and dates.

6What each maker's own pages state

What each maker's own pages state, read 2026-10-13. No prices are carried.
MakerWhat its own pages stateWhat it publishesPer-video cost it statesPages read
Revid AICreate, publish, learn, repeat: rendering, publishing, performance stats and Auto-ModePublish to TikTok, Instagram and YouTube from the appNot carried on the pages read2026-10-13
SceneMixer“Measured across every job that finished successfully on scenemixer.com in the thirty days to 20 September 2026: analysis of a whole book runs about 2 minutes 49 seconds at the median, one episode's storyboard 1 minute 54 seconds, one video segment 3 minutes 20 seconds, and compositing an episode 3 minutes 52 seconds.”Not carried on the pages readNot carried on the pages read2026-10-13
StoryShortAutomated short videos with voiceovers, background music and auto-postingAn automated feed of videos (1 series on Starter, 4 on Ultra)About 15 credits for a 30-second video with AI images; about 110 for an “AI movie”2026-10-13

Inclusion rule. Rows are the makers this page is about, each read on its own public pages, plus the drama pipeline whose limits this sheet keeps. A line a maker's page does not carry is written here as not carried on the pages read, which describes the reading rather than the plan. Order. Alphabetical by maker name.

Which limits each tool publishesSolid: a limit is published. Hollow: nothing on the pages read.Which limits each tool publishesStoryShortPippitSceneMixerWhat it runsWhat it runs — StoryShort: An automated feed of short videos, one series on Starter and four on UltraWhat it runs — Pippit: Creative suite with team storage and a 30-day recovery windowWhat it runs — SceneMixer: A drama pipeline of episodes, segments and takesPeoplePeople — StoryShort: Not stated on the pages readPeople — Pippit: Team accounts supportedPeople — SceneMixer: Not stated on the pages readStorageStorage — StoryShort: Not stated on the pages readStorage — Pippit: Up to 500 GB of team storageStorage — SceneMixer: Upload storage grows with the tier; generated files do not countAfter deletingAfter deleting — StoryShort: Not stated on the pages readAfter deleting — Pippit: Drafts and videos recoverable for up to 30 daysAfter deleting — SceneMixer: Deleting is permanent; there is no restore
Fig. 2 Solid: a limit is published. Hollow: nothing on the pages read.
Tools that publish each limitCounted from the table: tools that publish each limit.Tools that publish each limitStoryShort1 of 4Pippit4 of 4SceneMixer3 of 4
Fig. 3 Counted from the table: tools that publish each limit.
Three readings of the same four lines, from two video makers and a drama pipeline.
Asked of each readingStoryShortPippitSceneMixer
What it runsAn automated feed of short videos, one series on Starter and four on UltraCreative suite with team storage and a 30-day recovery windowA drama pipeline of episodes, segments and takes
PeopleNot stated on the pages readTeam accounts supportedNot stated on the pages read
StorageNot stated on the pages readUp to 500 GB of team storageUpload storage grows with the tier; generated files do not count
After deletingNot stated on the pages readDrafts and videos recoverable for up to 30 daysDeleting is permanent; there is no restore

Inclusion rule. Answers read from each maker's own pages as this sheet recorded them — the vendor pages on 2026-10-13, the register rows on 2026-09-25. A line the pages do not carry is written here as not stated on the pages read, which describes the reading rather than the plan. Order. As the lines are listed above.

7What the collection counted

Two readings below: the family with the largest comment count in the material collected for this column, and one share figure kept for another. Neither measures a plan.

Posts and comment mentions for the model family counted on this page, collected 2026-10-14.
FamilyPostsComment mentionsPositiveNegative
Sora1172946621112452

Inclusion rule. Families the collection counted on this page's subject, from one subreddit. A thread can be counted on both sides. Order. Descending by posts.

Share of the posts read in one subreddit that name a model family.
Model familyShare of postsPosts counted
Runway1.4%Not carried on the pages read

Inclusion rule. Model families the collection put a share against, counted from the posts it read. Order. Descending by share.

8When the other maker's plan suits better

  • Several feeds are the point — One series on Starter and four on Ultra is how the plans count the product, which suits a channel owner running more than one feed.
  • The cost is stated per video — About fifteen credits for a thirty-second video is a figure a posting schedule can be multiplied by before anything is paid for.
  • The last mile is automatic — Voiceovers, background music and auto-posting are named as the feed's parts, which suits publishing without a weekly pass through an editor.

The words behind this page are "storyshort ai"; the counts below belong to model families the community material keeps records for. Beside it: credits read against a year of work and project caps read across the sheet.