A series of long-reads on the production stacks that run without a producer. Each one names the layers, names the tools, names the worked example. All nine share the same throughline: design once, runs forever.
Every system on this list solves the same problem. The 80% of work that repeats, the steps that never change, the inputs that always come from the same sources. Most tools charge you to handle the 80%. These systems handle it themselves, once, and the rest of your time goes to the 20% that requires taste.
The nine systems below are not frameworks. They are actual production stacks I'm running or have run, in 2026, on a MacBook Pro, with a $0–$50/mo tool budget. Each is named with the jobs it covers, the tools it uses, and a worked example from a real session. Fork what fits. Skip what doesn't.
Every system on this list is structured the same way. Five jobs, twelve tools, one worked example. The five jobs are the structure. The twelve tools are 2026's best answer. The worked example is the proof that the system runs, end-to-end, on a real session, with a real timestamp.
When the tools change — and they will, in 18 months, in 6 months, in 6 weeks for the fast-moving layers — the structure holds. The voice-AI stack is still listen / think / speak / clone / ship when the TTS model is from a different vendor. The video stack is still script / voice / visuals / edit / distribution when the editor swaps. The structure is the system. The tools are the binding.
That's why the title is systems that run themselves, not tools you should buy. The system runs without you re-deciding every component every quarter. You pick the structure once. You pick the tools once. The system runs.