How Vsync works

You only need a few concepts to use Vsync effectively.

Builds

A build is an immutable snapshot of a directory. Its build ID is derived from its contents, so identical directories have the same ID. Builds can also carry a human-readable version, source revision, build configuration, notes, and status flags.

Games and platforms

One server can host several games. Each build belongs to one game and one platform, such as win64, linux, ps5, or xsx.

Streams

A stream is a movable name such as nightly, release, or qa. It points to one build per platform and keeps a history of its previous builds. Fetching a stream gets its current build; fetching a build ID always gets that exact immutable build.

Cache and checkouts

The local cache stores chunks and manifests that can be reused by future builds. A checkout is a normal directory containing a materialized build that you can run, copy, or inspect.

Deleting cached chunks does not delete checkouts. Deleting a checkout does not necessarily remove its chunks from the cache.

Deduplication

Before transferring a build, Vsync asks which chunks the destination already has. Only missing chunks cross the network. Updating a checkout is staged and then swapped into place, so cancellation or failure leaves the previous build intact.