Creator workflow
What 12 faceless creators actually made in month one
Our first-month production dataset, published unedited: every finished video, the style mix, the real per-video cost, and the caveats.
39 / 54
renders completed of those started - 72% success rate
15
failed renders, credits auto-refunded
12
distinct creators, 5 languages
~$2.32
real provider cost of a standard 30s video
The early adopters aren't making memes. They're making content with a script - the exact use case a faceless channel is built on.
Read the full dataset →Automation
Series Mode: a channel that publishes on its own schedule
Series Mode generates a recurring video per topic on a schedule, holds each as a reviewable draft, and publishes once approved - the workflow behind a hands-off faceless channel.
1
scheduled series included from the Starter plan
Draft
every video waits for review before it can publish
Refund
automatic credit refund on a failed render
TikTok · YT · IG
dashboard publishing, all three platforms
Review every video before publishing, or enable full autopilot - the two modes are explicit, not a buried setting.
Open Series Mode →Live reliability
How the pipeline performs right now
The 72% first cohort above is history; this is now - recomputed daily from production data. Sandbox jobs and unapproved Director drafts are excluded, nothing is hand-picked, and a render stuck in flight for over two hours counts as failed, not ignored.
| Period | Started | Delivered | Failed | Success rate |
|---|
| Last 7 days | 95 | 95 | 0 | 100% |
|---|
| Last 30 days | 191 | 191 | 0 | 100% |
|---|
| Last 100 renders | 100 | 100 | 0 | 100% |
|---|
Generation time: median 4m 4s, p95 8m 47s - n=190 delivered renders, last 30 days
Measured from scene submission to finished MP4 - excludes the scriptwriting/voiceover step and any time a Director-Mode draft waits for your review.
Publishing success by platform (last 30 days)
- Instagramn = 2 - too few to publish a rate (min 20)
0 of 0 failed renders in the last 30 days were refunded automatically - the refund is written in the same database transaction that marks the render failed.
Computed 2026-09-08 (UTC) - refreshed daily.
Download the anonymized per-render data (CSV) and recompute these numbers yourself - job ids are hashed, nothing else identifies a user or video.
Attribution policy: we publish named customer stories only with the customer's explicit written permission. Until then, every case study on this page is grounded in data you can verify - our open
production dataset and the demos on
Made with Reeloop.