Lineage artwork for Local, Hybrid & Private
Lineage visual · lineage texture platform local hybrid private

Local, Hybrid & Private

Local, Hybrid & Private

Where your work runs is a decision we state plainly, including what is not yet live. This page maps each deployment mode and what it is designed to do. It does not round anything up.


Deployment modes

Deployment What it is, by design
Owner-local The platform runs on your own machine, with the authority layer beside the work.
Local, invited Auteur Conductor connects a local AI harness to authorized Auteur domains on the same machine, with no hosted dependency.
Hybrid (local bridge) A hosted control plane coordinates approved work while proprietary media, files, and GPUs stay on your machine, with no inbound listener exposed. The protocol is designed and substantially tested; its live persistent transport is not yet complete.
Private hosted A private, project-scoped hosted deployment with verified organization and project boundaries and a provider vault. Designed for tenant isolation; not yet live.

Why local is the honest default

Keeping the work local is not a fallback; for proprietary material it is the point. Agent work runs in isolated worktrees, kept away from your primary checkout and independently verified before anything is integrated, so even local, autonomous work stays contained and auditable.

In owner-local operation, the engine and your work run on your own machine, and the authority layer runs beside the work as part of that operation.


What the hybrid bridge is designed to do

The local bridge is designed to keep proprietary media local while a hosted control plane coordinates approved work. By design it is an outbound, mutually authenticated connection with no inbound listener to expose, and it is designed so that a hosted coordinator could request approved work beside your own Resolve, local models, files, and GPUs without those assets leaving your machine.


What private hosting is designed to do

Private deployment covers verified organization and project authorization, private data boundaries, a provider vault, and enterprise-private operation.