The boltzmann version-control & ticketing system.

The pieces

• Depots — versioned storage designed for projects made of scenes, assets, and binaries — not just text files.
• Streams — lines of work you move between, made for the way teams actually pass work around.
• Tickets ("memory") — tasks and project memory attached to the work itself, versioned with it, browsable from the same panel.
• The VC explorer — browse history, inspect changes, and manage streams visually, in-engine or in the standalone panel.
• Live collaboration — two editors on one scene over the network, exchanging changes as reviewable diffs.

Three modes

Adopt boltzmann one piece at a time — each mode is fully supported:

• Tasks-only on plain git — keep your repos; add boltzmann’s ticketing and project memory on top.
• Depot-only — boltzmann versioning without the ticketing layer.
• Fused — the full product: depots, streams, tickets, and collaboration in one flow.

With ash

On a subscription that also carries ash, model development becomes versioned work like any other: experiments, model versions, and their tickets ride the same depots and streams — automated model development with real history.

Licensing & activation

• Boltzmann activates with its own BZ-XXXX-XXXX-XXXX-XXXX key; the boltzmann panel is unlocked by boltzmann’s key, not the engine’s. Any supported OS, transferable between machines.

Status & roadmap

Available now. The core — the versioned depot server, two-editor collaboration with diffs, and the panel in both standalone and in-engine forms — is built and in daily internal use on our own repositories. Today Boltzmann is delivered as the Version Control panel compiled into the godspeed editor bundle: download it with your BZ- key and the panel unlocks in the session you already have open. The standalone VC Explorer and the VS Code extension follow. One caveat worth stating plainly: the link between peers is not encrypted yet, so collaboration is for a trusted local network, not the open internet.