Docs · Boltzmann
The boltzmann version-control & ticketing system.
Boltzmann is project history built for engine work: depots, streams of work, tickets living beside the assets they describe, and live collaboration between editors. It runs as an extension on the godspeed engine and also standalone. Product page: /products/boltzmann.
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
Coming soon; founders subscriptions are open. 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. Packaged builds publish as the surfaces harden; subscribers’ keys activate the first one.