Autonomous Video Studios
PART IV

Infrastructure, operations and economics

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.

HomePART IV · Infrastructure, operations and economics
CHAPTER 19 · INFRASTRUCTURE

Infrastructure map

Both systems run on Google Cloud in europe-west1 since 2 November 2026, with their GPUs on AWS in us-east-1 and us-east-2 and their models on Amazon Bedrock. Cloudflare fronts both sites.

YouTube
Facebook
Instagram
LinkedIn
X
TikTok
Threads
each channel's own accounts; analytics are read back the same way
publish — from the control host to every platform
Google Cloud · europe-west1
Control host · LXC 269
  • ctl.py — the only door: batch, publish, status
  • publishers: YouTube · Meta · LinkedIn · X · TikTok
  • sentinel, every 5 minutes; failure ledger, 5 min
  • Studio: 4 code lanes, 4 Blender lanes, quick, connect
  • scheduler · film autopilot · R&D wing
  • GPU reconcilers: 13 pools, two accounts
  • posting guard · archive guard · alerts
The library

ready stock per channel; a video leaves the host only once the archive holds it at its exact size

n8n — the slot and generation clocks
  • calls ctl.py over SSH: a forced command, never a shell
Portal · LXC 268
  • content.storeswiki.com: Next.js and Postgres
  • dashboard · Studio · Eagle Eye · calendar
  • failures and levers · connections · long-form
  • content sync and archive sweep every 5 min
Google Cloud Storage — the media archive
  • every video, kit and record; versioned; copied hourly to a 2nd bucket
start · sync · render · stop
AWS us-east-1 and us-east-2 · two accounts
Account one · 22 × L4
P1 · P2 · Studio lanes 1–4
films · Blender lanes 2–4
zones 1a–1d and Ohio
every pool's later boxes
Account two · 8 × L4
P1 · P2 · Studio lanes 1, 2
films · Blender P1, P2,
Studio lane 1
a pool's first box
Amazon Bedrock

Claude Fable 5.2 · 5.1 (agents, critic) Opus 5.5 · 5 · 4.8 · Sonnet 5.5

Google Cloud TTS

Chirp 3 HD voices

Cloudflare

DNS · TLS · edge for both sites

Figure 35. The original programme's architecture. ChannelForge (Figure 29) runs on its own host, database and GPU fleet.
ComponentWhereWhat
Control host (original)Google Cloud, a Linux container on the estate's Proxmox hostctl, publishers, sentinel, schedulers, workers, reconcilers, the failure ledger
Portal (original)Google Cloud, a second container beside itcontent.storeswiki.com, its Postgres, content sync
ChannelForge hostGoogle Cloud, an Arm VM (c4a)app, control plane, gateway, Redis
ChannelForge databaseGoogle Cloud SQL, PostgreSQL 16313 tables, through the Cloud SQL Auth Proxy
MediaGoogle Cloud Storage, a bucket per systemthe original's versioned, Autoclass, 90-day soft delete, copied every hour to a second bucket; ChannelForge's private, per workspace
GPUsAWS us-east-1 and us-east-2, two accountsNVIDIA L4: 30 boxes for the original in 13 pools, ChannelForge's own fleet beside them
ModelsAmazon BedrockClaude Fable 5.2 and 5.1, Opus 5.5, 5 and 4.8, Sonnet 5.5, Haiku 5.5
VoiceGoogle Cloud Text-to-SpeechChirp 3 HD; word timing by faster-whisper on the GPUs
Schedulesn8nslot and generation clocks for Projects 1 and 2
EdgeCloudflareDNS, TLS, proxying for both sites
EmailAmazon SESalerts and ChannelForge's mail