For a lot of people, you should. White Glove Content runs $86–$354/mo on its operator track and covers scripts, AI voice, edits, thumbnails, metadata and posting. Channel Farm starts at $49/mo. If you want a handful of videos a week and no machine to babysit, those are a better deal than this and you should take one.

The difference is cadence, volume and ownership. A five-business-day delivery window cannot put a long-form and four Shorts out every morning. A per-channel subscription scales linearly with channels; a licence does not. And at the end of a year with them you have videos, whereas here you have a system you can modify, fork into a new niche, or point at a client's channel. None of the individual steps in this pipeline are novel. What you are buying is that they run together, unattended, every day, and that the code is yours.

It can, and you need to go in knowing that. YouTube's inauthentic content policy, renamed and clarified on 15 July 2025, explicitly targets content "produced using a template with little to no variation" and content "easily replicable at scale". Mass-produced, generic or repetitive uploads do not earn ad revenue, and YouTube applies this retroactively. A pipeline that runs the same steps nightly across several channels is structurally what that policy describes.

What the kit does about it: a deterministic policy gate and a reviewer agent that reject template-like sameness before anything publishes, forced AI disclosure on every upload through containsSyntheticMedia, and instructions in SETUP.md to vary channels for real and to keep a human editorial pass on what ships. That reduces the risk. It does not remove it, and no seller can honestly tell you otherwise. If a demonetisation would sink your business, this is not a safe purchase.

We do not promise that, and the numbers in this genre are not kind. Only about 9–17% of YouTube channels ever reach 1,000 subscribers, which is the floor for the Partner Programme, and daily news and trend content sits in a sub-$5 RPM band. No view, subscriber, monetisation or revenue outcome is promised by this product, on this page or anywhere else. Anyone selling you one is worth a hard look.

What it does is displace cost. If daily production is already a line in your budget — an editor, a VA, a freelancer, your own evenings — this turns that line into a vendor bill of roughly $150 to $400 a month for three channels. Buy it for that. Do not buy it as a route to YouTube income you do not have yet.

The pipeline is agent-agnostic by design, and there is a real protocol for it rather than a promise. yca next --json returns the next actions as typed objects, yca describe prints the JSON Schema of every payload an agent can submit, errors come back with a category and a hint, and the exit code distinguishes an error from a locked run from one that needs a human. AGENTS.md is a one-page operating guide written for whichever agent you bring, and docs/AGENT-INTEGRATION.md is the full spec. Anything that can run a shell command drives it.

If you want off Claude Code entirely, the kit ships a Vercel AI SDK 7 reference runner in agents/ai-sdk/, with its own MCP clients for the image, voice and publishing vendors, per-role tool scoping and trace propagation. It passes an end-to-end test against mock providers. It has not yet run a full production day, so treat it as a working starting point rather than a proven one.

Two things stay Claude-specific. The twelve subagents and eight skills in .claude/ are Claude Code's format and only Claude Code auto-loads them; they are markdown, so you can hand them to another agent as instructions, but that is your work. And the kit ships no .mcp.json, so outside Claude Code you wire the vendor connectors yourself — which is exactly what the AI SDK runner already does.

Claude Code is what the three live channels run on and the only path proven across a full day. Codex, Cursor, Windsurf and your own loop will drive the same CLI, and we have not tested them end to end.

Either. yca schedule install renders the same job table as launchd jobs on macOS, or as systemd --user timers or cron entries on Linux, and yca doctor knows about both, down to checking systemd linger so your timers survive a logout. A Linux box is covered by the kit's own self-tests.

Being straight about the asymmetry: our three channels run on macOS, so that is the configuration with real nights behind it. Linux is supported and tested, not yet production-proven by us. Either way the machine has to be awake and online at run time, which is the part people underestimate. A Mac mini on a shelf or a small always-on Linux box is the normal setup.

Beyond the OS it needs ffmpeg, python3 with Pillow, and whichever agent engine you picked. yca doctor tells you which of those is missing before you find out at 3am.

Roughly $150 to $400 a month in vendor spend for three daily channels, on top of a machine you already own. That breaks down as Claude Code at $20–$200, Higgsfield at $19–$129, ElevenLabs at $11–$99 and Blotato at $29–$97, depending on tier and volume. Push more channels or longer videos and it goes up.

There is no licence renewal and no per-video fee from us. The full table is in the cost section.

No. Not at $4,997. You get the source, the architecture document, SETUP.md and the test suite, and that is the whole deal. There is no SLA, no onboarding call, no bug-fix promise and no guaranteed reply time. The only thing the support address handles at this tier is a broken download link or a refund.

If you want someone on the hook, the $15,000 tier includes setup and 30 days of integration support, or the managed tier means we run it. Both are enquiries above and neither takes payment on this page.

Run the evals. yca eval run --suite regression replays four golden runs and nine mutations, each one a real failure we have had, and it costs no credits because it grades recorded output. That is the suite to run before you merge anything. The four behavioural cases and the capability tasks cost credits, so they are meant for the weekly job the scheduler already installs.

If you want to go further, yca eval hillclimb proposes one patch at a time to a role's instruction file, scores it against a held-out split the proposer cannot see, and keeps it only if the gain is bigger than the measured noise and nothing regressed. It writes a diff for you to review and never edits your repo. You can run the whole loop offline on the mock engine with the example suite before you spend anything.

The pipeline stops at that step, logs the error, and resumes from that step once it is fixed. Fixing it is yours to do. Each vendor sits behind one small adapter in the provider layer, so a breaking change is usually one file, and the vitest suite tells you what broke. The design assumes breakage and aims for a fix a developer can finish in an afternoon.

We patch the system we run ourselves, but the licence carries no update entitlement. Buying it does not buy you future versions.

Yes. LICENCE.md is a single-operator commercial licence: one operator, unlimited channels, including channels you run for paying clients. Agencies are an intended buyer. What it does not permit is reselling, sublicensing or redistributing the code itself, or handing the kit to a client as their own. Read LICENCE.md in full before you buy if this matters to your business model, and email us if your setup sits in a grey area.

Source code and a setup guide, sold as-is under a single-operator commercial licence. It is software. It is not a business, not an income opportunity and not advice of any kind. You get the files listed in the licence section, you run them on your own machine with your own vendor accounts, and what the channels do after that is yours.

There are no customer testimonials on this page because there are no customers yet. The three channels are ours, and the terminal output further up was pasted out of the running system so you can judge it without taking our word for anything.

30 days, no questions asked. Email [email protected] from the address you paid with, within 30 days of purchase, and we refund in full. We do not ask you to prove you tried it, and we do not ask you to delete anything. This is source code, so we are relying on people being straight with us, and so far that has been fine.