One Engine
Transit keeps embedded and server mode on the same storage model instead of splitting the product in two.
Lineage-Aware Event Rails
Move event history like a rail network, not a dead-end queue.
Transit is an append-only event engine with native branches, explicit merges, and tiered storage. It runs embedded in your process or as a server without changing the underlying model.
- Keep immutable history explicit instead of implied.
- Branch cheaply without copying ancestor bytes.
- Separate local, replicated, and tiered durability claims.
Why Transit Feels Different
The engine is built around divergence, provenance, and explicit storage boundaries.
Transit does not pretend branching, publication, and durability tradeoffs are edge cases. The docs shell should reflect that the product is intentional all the way down.
Lineage Native
Streams can branch and merge explicitly, so divergence is recorded instead of hidden.
Tiered By Design
Remote object storage is a first-class part of the history model, not an afterthought bolted onto local append.
Choose Your Track
Take the route that matches how you plan to use the engine.
The same storage semantics show up in two packaging modes. Start with the adoption path that matches your current job, then move deeper into the shared contracts.
Blue LineEmbedded TrackStart from the shared Rust engine when you want append, replay, branch, merge, and publication in-process.Green LineServer TrackStart from the daemon and client surfaces when you want the same semantics through a network boundary.Yellow LineReference TrackMove from the public narrative into foundational contracts when you need the exact repo-level constraints.
Start Here