How the factory works, what it costs to run and how it keeps your channels safe.
It runs a production pipeline for YouTube: it researches topics, writes a script with Claude, plans scenes, generates clips with Google Veo, records a voiceover, builds subtitles, assembles the video with FFmpeg, runs quality checks and uploads to your channel through the YouTube Data API. You set the niches, languages, channels and the daily target; the factory does the rest.
Any. A niche is configuration, not code: audience, tone, factual rules, visual style, recurring characters, prompts, formats and limits are all edited in the console. Devotional stories, finance explainers, kids' science, history shorts — you define the rules and the factory follows them.
Any language you configure a profile for — script, writing direction, voice defaults and subtitle rules are set per language. Content styles such as Hinglish ride on a base language, so a Hindi channel can choose between pure Hindi and Hinglish scripts.
Yes. Formats (including vertical Shorts and landscape long-form) are configured per niche and channel, with their own duration limits and aspect ratios. Targets can be split by format.
Yes. Every new workspace starts with a free trial that includes a few real videos, and simulated providers let you run the whole pipeline end to end as often as you like at no cost. Simulated results are clearly labelled in the console and are never published to YouTube.
Every video passes automated checks before publishing: black frames, silence, loudness, duration, metadata limits and an AI review of the script and metadata. A failed check regenerates the affected stage or stops the job with a reason — it never ships silently.
Not unless you choose that. The safe default is to upload as a private draft with AI disclosure on, so you can review before making a video public. Safety settings only get stricter as overrides stack — a niche cannot make videos public if the global default holds them private.
Yes. The altered or synthetic content disclosure is set on upload according to your channel settings, which default to on. You remain responsible for following YouTube's policies for your channel and content.
Uploads are resumable. If an upload may have reached YouTube before a crash, the worker reconciles it against your channel instead of blindly uploading again, so you don't end up with duplicates.
Your plan does. We run the AI and media providers on our own platform accounts, and every plan includes a monthly usage allowance (real videos and provider spend) shown on your Billing page. There are no separate provider bills and no API keys to set up; if you reach the allowance, new real videos wait for the next month or an upgrade.
Every paid call reserves budget first, using the provider's configured prices. Daily and monthly limits apply per provider, niche, channel and campaign; if a call would exceed a limit, it waits for the next window instead of spending. The Costs page shows estimated spend against each budget.
It depends on the video length, the number of generated scenes, the model and voice you choose and the providers' current prices. It comes out of your plan's included allowance, and the console records the estimated cost of every call, so you can see what each niche uses.
Yes. Monthly plans run to the end of the paid month; yearly plans to the end of the paid year. See the Refund & Cancellation Policy for refunds on first-time yearly purchases.
In the console, open Channels and click Connect. Google's consent screen opens in a popup; once you approve, the popup closes and the channel shows as connected. Access tokens are encrypted at rest and can be revoked at any time from your Google account.
No. Just click Connect on the Channels page and approve access with the Google account that owns or manages the channel — the Google side (OAuth client, redirect address, YouTube quota) is set up and run by us. Finish the connection in the same browser you started it from. If Google shows an error such as “redirect_uri_mismatch”, it's a configuration problem on our side: contact support and we'll fix it. Enterprise workspaces can optionally connect channels through their own Google Cloud project for their own YouTube quota.
We use the YouTube Data API only to upload and manage videos, thumbnails and playlists on channels you authorise. By connecting a channel you also agree to the YouTube Terms of Service, and Google's Privacy Policy applies to data Google processes.
Yes. Invite your team to your workspace as members, each with a role — Owner, Admin, Content manager, Operator or Viewer, for example operators who can retry jobs but not change budgets. Growth and higher plans can also create custom roles. Only owners manage billing, nobody can give a member more rights than they hold themselves, and every configuration change is recorded in the workspace's audit log. The number of members depends on your plan.
YouTubeVision AI is a hosted service — there is nothing to install. We run the console, the API and the production workers for every customer, and each customer's data stays in its own private workspace. Enterprise is a plan on the same hosted platform with custom limits, your own Google Cloud project for YouTube quota and an SLA; talk to sales for the details.
Each job moves through a durable, stage-by-stage state machine with SQL leases, retries with backoff and idempotency keys. After a restart the worker picks up where it left off; paid steps that already succeeded aren't repeated.
Each workspace's data is isolated from every other workspace. OAuth tokens and provider keys are encrypted at rest, logs are redacted, sessions use HttpOnly cookies with CSRF protection, and access is permission-based and audited. See the Privacy Policy for what we store and for how long.