Autonomous Video Studios
HomePART V · Results and the offer
CHAPTER 26 · THE OFFER

What a buyer receives

Either system can be acquired on its own, or both together. Three forms are possible: outright purchase with full rights, a licence to run it, or a done-for-you build on the buyer's own cloud accounts with the buyer's own channels.

Original programmeChannelForge
Source codepipeline, kits, control plane, portal, Studioapp, control plane, gateway, pipeline, infrastructure
Running system65 channels with their brands, kits and stock, the Blender toolkit and its asset catalogue; optionally the live accountsthe live product, its flags, plans and catalogue
Machine imagesgolden GPU images (both clouds), setup scriptsthe GPU box images and setup
Datathe media archive and its replica, analytics history, R&D findings, the failure ledgerthe schema, migrations, settings, the three feature studies
DocumentationREADMEs, runbooks, DR.md, the operations lessons, this dossierthe same plus 82 public docs pages, an operator RUNBOOK and the three feature studies
Handoverguided transfer of hosts, accounts and schedulesguided deployment and the first weeks of operation

What the buyer needs#

  • A cloud account for hosting (Google Cloud as today, or any Linux cloud) and one or two AWS accounts with an L4 GPU quota.
  • Access to Claude models (Amazon Bedrock, or Anthropic's API) and Google Cloud Text-to-Speech.
  • Developer apps on the platforms to publish to: a Google Cloud project for YouTube, a Meta app for Facebook, Instagram and Threads, and LinkedIn, X and TikTok apps as needed — each needs the platform's review for public use.
  • For ChannelForge: Stripe and/or PayPal merchant accounts, a domain, Amazon SES (or any SMTP provider).

How it would be moved#

  1. Provision hosts, a database and buckets on the buyer's cloud from the infrastructure scripts.
  2. Restore code from the repositories and the data from the backups; install the golden GPU images.
  3. Hold posting; connect the buyer's model, voice and platform accounts; run the account checks and a render parity check.
  4. Rehearse: one generation per pool, one publish per platform, a schedule cycle — then release posting.
  5. Hand over the runbooks and operate together for an agreed period.