Skip to main content
Dits LogoDits
v0.1.5 alphaLocal engine availableRemote collaboration: roadmap

Version the source. Explain every result.

Open, local-first version control for large media and asset pipelines. Dits gives asset-heavy teams exact local history today and is building toward a reproducible graph of edits, dependencies, and renditions shared through an open protocol.

Try the local alphaRead the architecture
packaged: macOS arm64 · Windows x64
npm install -g @byronwade/dits
mkdir dits-evaluation && cd dits-evaluation
dits init
dits add .
dits commit -m "First exact snapshot"
dits log

Alpha software. The v0.1.5 npm artifact packages Apple Silicon macOS and Windows x64; other targets require a source build. Use a disposable or independently backed-up project.

The model

From exact bytes to explainable outputs

Dits starts with trustworthy local history. Media structure, edit intent, derivation, and collaboration are added in that order.

Current
Exact source history
Commits, branches, tags, manifests, and byte-exact local reconstruction for mixed text and binary workspaces.
Current + experimental
Media-aware storage
Content-defined chunking, content-addressed objects, MP4-aware code, integrity checks, and early proxy and VFS paths.
Experimental
Reproducible asset graph
Explicit edits, dependencies, frames, timelines, and renditions instead of treating every output as an unrelated blob.
Roadmap
Open collaboration protocol
Verified object exchange, resumable transfer, atomic refs, identity, authorization, and lock leases across interchangeable transports.
Available locally
What you can evaluate now
The current claim is a local alpha, not a complete team platform.
  • Local repository initialization, add, commit, history, branch, merge, tag, diff, and checkout workflows
  • FastCDC chunking and BLAKE3-addressed local object storage
  • Hybrid handling for text and large binary assets
  • Byte-exact local reconstruction and integrity-oriented reads
  • MP4 structure-aware code plus experimental FACR, photo, proxy, and VFS paths
Know before trying
The boundaries are part of the product
A placeholder command or design page does not make a capability shipped.
  • Alpha software: evaluate on disposable or independently backed-up projects
  • Network push, pull, fetch, sync, and network clone do not transfer repository data
  • P2P, QUIC transport, a hosted service, public SDKs, and NLE plug-ins are not shipped
  • FACR, photo edit logs, proxies, VFS, and broad media compatibility remain experimental
Measured, not imagined

A small evidence base we can reproduce

These are component microbenchmarks from the committed artifact, recorded on an Apple M2 Pro. They do not establish end-to-end repository, media, or network performance.

See method and limitations
BLAKE3 hashing
1,809.96 MB/s
1 MiB input, 200 iterations
FastCDC chunking
991.76 MB/s
32 MiB input, 5 iterations
SHA-256 hashing
348.37 MB/s
1 MiB input, 100 iterations
Dependency-ordered roadmap

Safety before scale. Semantics before sync.

1. Credibility and data safety
Now
Crash-safe writes, recovery, compatibility fixtures, and truthful docs.
2. Stable format and scale
Next
Versioned deterministic objects, bounded-memory ingest, packs, indexes, and trees.
3. Semantic media
Research
Source, edit, dependency, timeline, and rendition records proven on real workflows.
4. Verified collaboration
Later
A transport-independent remote CAS protocol with atomic refs and recovery tests.
Explore the roadmap
Open source · Apache-2.0 OR MIT

Help make large-asset history trustworthy

The most valuable alpha contributions are real fixtures, failure cases, format reviews, and reproducible workflow evidence.

Start locallyReview the source