History model
Nothing disappears. Nothing rewrites. Ever.
Immutable states, stable change identifiers, and content-addressed integrity across every hosted repository. The kind of history you can reference a year from now and trust completely.
LOOM.
Product
Version control built for teams that demand clarity.
What happened, who acted, and how access is governed — visible to operators, developers, and security stakeholders from one hosted surface. No ambiguity. No tooling patchwork.
Control plane
One surface for your entire hosted estate.
Namespaces, repositories, and grants with effective role resolution at every level. Set policy once, let inheritance do the rest. Stop configuring the same access in twelve places.
Provenance
You always know who acted. Human or AI.
Provider, model, confidence, and verification status live beside every change as structural data. Not parsed from commit messages. Not inferred. Known.
Sync and bridge
Git bridge, wire protocol, refs — one coherent view.
Sync status, bridge state, threads, markers, and oplog in one surface. No separate tooling for each concern. No context switching between dashboards.
Four pillars
What the best engineering teams see at a glance.
Immutable history
Nothing disappears. Nothing moves without a record. Every state remains stable, inspectable, and attributable — the kind of history you can actually trust.
Hosted control plane
One quiet admin surface for namespaces, repositories, and grants. Role resolution that flows down cleanly so you set policy once and stop thinking about it.
Human + AI provenance
See who acted, which model participated, and whether the result was verified. The teams that move fastest are the ones that always know who did what.
Multi-repo coordination
Namespaces, repositories, threads, and worktrees — without losing track of who changed what or why. Complexity handled, not hidden.
Interface direction
Quiet enough for leadership. Precise enough for staff engineers.
Every view answers the same questions: what happened, who acted, and what access governs it. The teams that move fastest are the ones that never have to ask twice.