Governed beta for growth creative
Build a video plan around your campaign goal.
Connect a campaign or content opportunity to a script, visuals, voice, brand assets and captions. Video Factory has conditional production and render paths in governed beta; availability depends on configured providers, trusted policy, scoped assets, storage and approval. Video supports the growth strategy rather than becoming an isolated production task.
Interactive Capability Preview
Illustrative workflow with sample telemetry. Real captures appear on the homepage.
No customer production job or media loaded. No playback, render outcome or performance data is shown. Video serves a campaign or content opportunity.
Five potential providers · not active connections- Runway
- Google Veo
- HeyGen
- ElevenLabs
- Remotion
- Social shorts
- Article summaries
- Branded videos
- Product explainers
- Avatar presentations
- Educational clips
- Campaign creatives
- Campaign / Content
- AI script
- visual generation
- voice
- brand assets
- captions
- Remotion composition
- review
- publish/distribute
Remotion is a potential composition path; the current renderer catalog uses Shotstack. Actual availability requires a configured adapter and provider. This does not establish that the entire journey is enabled.
Production is conditional on trusted platform policy, source evidence, verified scoped assets with rights and brand review, storage, budget and enabled provider capabilities. Supported approval paths require an independent human reviewer.
Provider states and uncertain outcomes are recorded separately. Render completion, QA and publish/distribute are separate outcomes; completing a render does not distribute the asset.
How the capability works
1. Match the output to the growth objective
Possible outputs include social shorts, article summaries, branded videos, product explainers, avatar presentations, educational clips and campaign creatives. These are output concepts, not proof that each format has an enabled end-to-end production path.
2. Review the canonical production journey
Campaign / Content → AI script → visual generation → voice → brand assets → captions → Remotion composition → review → publish/distribute. This canonical model includes potential paths; the configured renderer and supported distribution determine what can actually run.
3. Distinguish potential providers from availability
Potential providers include Runway, Google Veo, HeyGen, ElevenLabs and Remotion. Provider names do not establish a connection. Current adapters include video, avatar and voice providers; the current renderer catalog uses Shotstack. Remotion composition is a potential path, not a claim that it is the active runtime renderer.
4. Check the gates before production and release
Production requires trusted platform policy, verified source evidence, scoped assets with rights and brand review, storage, budget and enabled provider capabilities. Supported approval paths require an independent human reviewer; render completion and QA remain distinct. Publication or distribution requires a separate supported path and is not implied by a completed render.
Frequently asked implementation questions
Are all providers and output formats enabled?
No. Provider and output lists describe potential choices. A usable production path needs configured capabilities, credentials behind the provider boundary, policy, assets, storage and the required approvals.
Does rendering publish the video?
A render has its own persisted outcome and QA state. Publishing or distributing the approved asset is a separate supported operation.
Want to see what your site is missing?
Connect your domain, inspect the evidence, and use Groviqo to prioritize the next growth moves.
Start at your pace. Connect your data sources, surface high-impact opportunities, and execute improvements with total control.