My own content business
The Studio: an AI content engine
One engine runs several short-video channels: an AI agent drafts, local models render, and nothing goes out without my approval.
7,400+views on the first 6 Shorts
3channels warming up
20clips made as versioned recipes
7klines of Python, plus a Remotion motion layer
What it is
A shared Studio core with one module per content stream: paid clip campaigns, a faceless AI-news channel, and an AI-presenter reel. Each stream plugs into the same database, job queue, renderer, scheduler and publisher.
The engine
- Every clip is a versioned recipe: a timeline in JSON. A tweak edits the recipe, never pixels, and every version is kept.
- Rendering: recipe to video with ffmpeg and Remotion, with speech-to-text captions (Parakeet on MLX), scene detection, subject cut-outs and smart reframing.
- Local generative models on a Mac: image (Z-Image, FLUX.2-klein), video (LTX), voice (Qwen3-TTS) and upscaling (SeedVR2).
- A local dashboard and Telegram inbox: I approve clips, leave notes at exact moments, and answer one-tap questions from the agent.
- Claude operates the Studio through its own skills; YouTube analytics snapshots feed back into what gets made next.
Rules I built in
- Nothing is published without my approval. Agents write drafts only.
- Platform tokens live in the macOS Keychain and are read only by the publisher, never in prompts, the database or chat.
- No automating platforms whose terms forbid it, and only original characters and voices.
Stack
PythonSQLiteffmpegRemotionMLXParakeetQwen3-TTSLTXFLUXMediaPiperembgClaude Code