Inputs
References, images, prompts, masks, palettes and spatial views enter only where the receiving tool can use them.
Knowledge base
Learn the system through creative tasks, not technical graph theory.
First session
Install VEINDRA Studio on Windows and create or open a canvas.
Add supported provider keys in Settings, or install/connect VEINDRA Brain for compatible local jobs.
Drag an image, paste a screen capture, import a 3D reference or begin from a prompt.
Route the source, direction and generator into a visible workflow. Generate only when the chain is ready.
Keep the canvas, settings and creative path together for the next session.
Core concepts
References, images, prompts, masks, palettes and spatial views enter only where the receiving tool can use them.
Global Context carries shared direction; Subject Context keeps subject identity separate when the workflow needs it.
Chain Context can pass relevant creative history forward. Use it when continuity matters and avoid it when a clean restart is better.
Duplicate a path to compare alternatives without destroying the direction that already works.
Save repeated generator configurations as reusable personal tools.
Local AI
Studio should stay focused on creative direction. Brain owns compatible local models, LoRAs, GPU jobs and diagnostics.
Install Studio and Brain on the workstation. Studio discovers the local endpoint and available models.
Install Brain on a suitable GPU machine in a trusted local network, then connect Studio to the Brain address.
Download or import a supported model inside Brain after reviewing and accepting its separate licence.
Brain never silently falls back to a cloud API. A local job either runs on the selected Brain or reports an actionable local error.
System requirements
Modern multi-core CPU, 16 GB RAM recommended, current GPU drivers and sufficient project storage.
A supported Google or OpenAI configuration. Provider availability, pricing and model terms apply.
Current supported runtime targets Windows with compatible NVIDIA drivers. Lower-memory paths are not promised unless explicitly validated.
Studio and Brain must be able to reach the configured endpoint. Do not expose Brain publicly without a separately secured deployment.
Support
Describe the workflow, provider or local model, exact error and the action that triggered it. Never send project assets or API keys unless a specific secure support process requests them.
Next / put it to work