Same Connect protocol. Same repo IDs. Same checkout and changelists. Promote the host role to Kenavo Cloud without rewriting history or retraining the team.
You don’t pick “self-host forever” or “cloud forever” on day one. You grow into Kenavo Cloud when a desktop that must stay online stops being enough.
A Desktop on the studio network hosts the object store. Teammates join over Kenavo Connect: invites, exclusive locks, Get Latest with pause/resume.
Same project, same history. Hand the host role to Kenavo Cloud when you need always-on hosting, remote teams, or a machine that isn’t someone’s workstation.
Kenavo was designed local-first with stable IDs from create. Connect is a host role, not a one-way migration into a foreign server model.
Repository, stream, and workspace IDs don’t change when you promote the host.
Locks, Get Latest, and resumable transfers stay on the Connect path artists already know.
Checkout → work → submit via kenavo-agent. Hosting mode is infra, not a new VCS religion.
Download Desktop, share over Connect, invite the team. Kenavo Cloud promote when you need always-on.