“A quiet morning above the cloud forest...”
Natural voice · Take 04 · source script attachedOne local studio for every creative capability.
Choose the capabilities you need and keep them inside one coherent workspace.
Colvri is designed to coordinate creative models, isolated runtimes, and project files without forcing every user into the same installation.
Workspace Local environment readyThree capabilities. One creative thread.
Each module keeps its own controls while sharing projects, local files, and a visible runtime.
One project keeps the creative decisions together.
Colvri is designed so a script, visual direction, motion study, and their selected models can share context without forcing every capability into the same control surface.
Project threadEverything useful keeps its context.
Saved locally
Visual direction A
Motion study · 00:06A clear path from model choice to local output.
The system is planned around visible decisions before, during, and after installation.
Inspect the fit
Review the exact source, license, storage footprint, runtime, and hardware requirements.
Install the module
Add only the capability and adapter selected for the current creative workflow.
Create in the project
Keep prompts, source media, useful outputs, and their configuration in one local thread.
The studio grows by module, not by hidden dependency.
A capability can be installed, replaced, or removed through an explicit boundary. The core coordinates projects and files without absorbing every model-specific runtime.
- Install only what the work needs.
- Keep third-party terms separate.
- Preserve one coherent project system.
Local control is expressed in the interface.
Privacy, storage, compatibility, and licensing should be visible product states—not promises hidden below an install button.
Your machine remains the workspace.
Project files and generated media stay in the environment the user controls.
ExecutionLocal runtimeNo required cloud handoff
Project filesUser-controlled storageSources and outputs stay connected
LicensingSeparated by layerCore, adapter, model, and weights
InstallationCapability by capabilityRequirements shown before download
Product questions, answered without hiding the boundaries.
Colvri is still pre-release. These answers describe the product direction and make clear where implementation, model, and license details remain separate.
No. Colvri is designed so voice, image, and video can be added independently, keeping downloads and runtime requirements aligned with the work you actually do.
That is the planned workspace model. Source files, prompts, useful outputs, and capability-specific settings stay connected through one project without flattening every tool into the same interface.
Replaceable adapters are part of the architecture. A supported model should be selectable without becoming a hidden dependency of the Colvri core.
The product direction keeps them in a user-controlled local workspace. Colvri does not require a proprietary cloud handoff to organize or generate project media.
No. The interfaces explain the intended product system. Availability must be confirmed through current project documentation and implemented capability status.