The original faceless-channel programme and the ChannelForge SaaS: design, operations, results and economics
made, checked and published with no one filming, editing or uploading: 2,015 by the original programme, 944 on ChannelForge.
on 16 live channels in their first month, with 13,481 followers and subscribers — ×2.1 in the eleven days since the first edition.
an episode under 8 never reaches a platform: 30 of 2,015 were held by the gates, and a fact, a unit or a caption out of sync holds one too.
charged to customers at cost times 1.8 to 3 — a margin of 44 to 67% on every credit at list value, so every episode a customer makes earns more than it costs.
every refusal on the record with a lever beside it; GPU work fails over across zones, regions and cloud accounts, as it did on 14 November.
1,106 test files, golden GPU images, runbooks and a written disaster-recovery plan; either system can be sold on its own.
| 3 November | 14 November | ||
|---|---|---|---|
| Episodes made by the original programme | 941 | 2,015 | ×2.1 |
| Posts by the original programme | 2,261 | 4,421 | ×2.0 |
| Views on its live channels | 2.15 million | 4.43 million | ×2.1 |
| Followers and subscribers | 5,279 | 13,481 | ×2.6 |
| Channels (live) | 33 (13) | 65 (16) | |
| Long-form films | 16 | 28 | |
| ChannelForge episodes | 440 | 944 | ×2.1 |
| ChannelForge channels | 22 | 49 | |
| ChannelForge features switched on | 36 | 166 | ×4.6 |
| GPU boxes (original) | 12 | 30 | |
| Lines of code · test files | 700,000 · 450 | 1.14 million · 1,106 |
In 33 days, from 12 October to 14 November 2026, the two systems described here made 2,959 finished videos and published them as 4,621 posts. The original programme's channels have been watched 4,434,425 times — more than twice the 2.15 million of the first edition, eleven days earlier. Nobody films, edits, writes or uploads anything: an AI agent writes each episode — as code, or since 10 November as a photoreal Blender scene — a GPU renders it, a voice model narrates it, captions are timed to every spoken word, a battery of quality gates checks it, and the system posts it on a human-looking schedule to each channel's own accounts — then reads the audience numbers back and learns from them.
What the two systems do, who they serve, and what they have produced in their first month.
65 channels in ten projects, the pipeline that makes their episodes and films — in code and in Blender, captioned word for word — the publishing calendar, every failure and its lever, the self-healing layer, and the portal the owner runs it from.
The same engine as a multi-tenant product: what customers get, how it is built, how tenants are kept apart, how GPUs are shared fairly, how it charges, and how other software drives it.
Where everything runs, how the GPUs are managed, how nothing is ever lost, what it is built with, what it costs, and how long it took.
What the channels have reached so far, what a buyer receives, and who built it.
The original programme's 65 channels, ChannelForge's channels, and a glossary of the terms this dossier uses.
Either system — or both — can be acquired outright, licensed, or delivered as a done-for-you build on the buyer's own cloud. The handover includes all source code, infrastructure scripts and golden machine images, the complete documentation and runbooks, the deployed-state snapshot, and a guided transfer. The chapter 'What a buyer receives' lists everything; the one after it introduces the author.