Production Hub

The production hub that
runs the campaign.

Campaigns run as projects. Each workspace carries a stage rail, the project files, and a Cast drawer. Approval gates decide what the client sees, and one token-gated link puts the cut in front of them without an account.

Start freeSee team plans
5seats on Studio15seats on Studio Scale0client accounts needed20VX free on signup
01

One workspace per campaign

THE WORKSPACE

A project is not a folder of exports. It is the room the campaign happens in: status on the rail, files in reach, identity one drawer away.

The stage rail

Every project moves along production stages. Where a shot sits on the rail is the status meeting, so nobody writes one.

Project files

What the campaign produces stays attached to the project. The files a review needs are already in the room, not in a thread.

The project Cast drawer

The Cast the campaign is locked to sits inside every workspace. Pull the identity into a shot without leaving the project.

02

Clients see what passes the gate. Nothing else.

CLIENT REVIEW

Review is a control surface, not a folder dump. Approval gates sit between production and the client view, and the share link only carries what cleared them.

Agencies lose clients in review, not in render. The hub separates the two: the team works loud inside the project, the client reads a quiet, gated cut.

  • Included:Approvals recorded per shot and per gate
  • Included:The gate decides what appears in the client view
  • Included:Share links are token-gated: no client accounts, no platform tour
  • Included:You control exactly what is visible on the link
01

Gate the shot

Run per-shot approvals in the gate panel. A shot that has not passed its gate stays internal, whatever state the rest of the project is in.

02

Send one link

Generate a token-gated share link for the review. The client opens it in a browser. No account, no signup, no access beyond the link.

03

Direct the review

You decide exactly what the link shows. The client reviews the cut you sent, not the work in progress behind it.

03

Run proven workflows against the project

REPEATABILITY

A recipe that worked last campaign is a template, not a memory. Point it at the new project and the output lands in the workspace.

Import from the Workflow Marketplace

Pick a workflow template from the public marketplace and run it against the project. The results file themselves with everything else the campaign owns.

Browse the marketplace

Built on the Workflow Canvas

Workflows are node graphs. See how a shot becomes a repeatable graph you can hand to the next campaign.

Explore the Canvas
04

Scoped to the org, sized to the team

ORG SCOPE

Projects live inside your organization. Seats and the shared Cast library come with the plan, from the Studio plan up.

PlanSeatsShared Cast library
Studio5Included
Studio Scale15Included

Seat counts read from the same tier table that gates the studio, so this page and the product never disagree.

FAQ

The Production Hub, answered

What is the VisionX Production Hub?
The Production Hub runs a campaign as a project. Each workspace carries a stage rail of production stages, the project files, and a project Cast drawer, so the work, the assets, and the identity stay in one place.
Can clients review work without a VisionX account?
Yes. Share links are token-gated: the client opens the link in a browser and reviews what you sent. No account, no signup, and nothing outside the link is visible.
How do approval gates work?
Approvals are recorded per shot and per gate. A shot that has not passed its gate stays internal, and the client view shows only what the gates have cleared. Production stays messy, review stays clean.
Can I reuse a workflow across campaigns?
Yes. Workflow templates from the Workflow Marketplace run directly against a project, so a recipe that worked on the last campaign becomes the starting point for the next one.
Which plans include team seats and a shared Cast library?
Team features are org-scoped from the Studio plan up. Studio includes 5 seats and Studio Scale includes 15, both with a Cast library shared across the organization.
Does the Production Hub handle scheduling or invoicing?
No. The hub covers the creative pipeline: project workspaces, per-shot approvals, and client review. Scheduling, call sheets, and invoicing stay in the tools you already use.
05

The rest of the pipeline

THE PLATFORM

AI Video Generator

Cinema-grade video across Seedance, Sora, Veo, Kling, and Grok. One Cast, every engine.

Explore

AI Image Generator

Key art, product stills, and character sheets from GPT Image, Nano Banana, FLUX.2, Grok, and Seedream.

Explore

Consistent AI Characters

The moat: a brand-locked character identity that holds across every shot, engine, and cutdown.

Explore

AI Lip Sync

Dialogue that lands on the face. Sync any performance to any script, in any language.

Explore

AI Dubbing & Voice Cloning

The Audio Studio: AI dubbing, voice cloning, and text-to-speech tuned for campaign work.

Explore

AI Storyboard Generator

Board the campaign before you burn budget: beats, frames, and shot plans in minutes.

Explore

AI Workflow Canvas

A node graph for shots: chain images into video, extend clips, and reuse the graphs that work.

Explore

AI Video Upscaler & Finishing

Master the final cut: upscale, boost frame rate, and clip long renders into social shorts.

Explore

Reference Plates

Lock locations, products, and wardrobe once. Every shot that references a plate stays on set.

Explore

The whole campaign, run in one place.

20 VX free on signup, no card required.