UnitCompose is an embeddable Rust framework for building performance-critical algorithms from typed, testable, and replaceable Units.
Connect Units through named Resources, compose them into configuration-driven DAGs, and prepare storage before execution. Algorithm teams can evolve implementations and compositions independently, while host applications retain control of lifecycle, communication, threading, and deployment. The same binary can load different algorithm compositions without rewriting the host or hard-coding the graph in source code.
UnitCompose is built on lessons from 1,000 days of engineering across 10+ algorithm teams, 1,000+ engineers, and software shipped at million-product scale. It is designed for autonomous driving and embedded intelligence, and for any system that needs predictable performance without sacrificing a decoupled development experience.
UnitCompose targets the layer inside a larger component. A ROS node, service, simulator, offline tool, or another framework owns the Module and decides when to build, run, replace, and destroy it. UnitCompose does not take over the application lifecycle or communication system.
| Prepared Module | Measured over 1,000 runs |
|---|---|
 |
 |
| Interactive navigation episode | |
 |
|
View the latest CI-generated reports for all three demos.
Each successful main build publishes fresh Module graphs, measured timings,
run metrics, and interactive Rerun recordings. Pull requests retain the same
report as a downloadable GitHub Actions artifact.
The prepared graph is available before execution; the measured view adds timing from completed runs. Click the Rerun preview to inspect the recorded episode.
UnitCompose has three public concepts:
- Unit: one independently testable computation step with declared ports;
- Resource: one named, typed value connecting Module inputs and Unit outputs;
- Module: one validated Resource DAG, prepared once and run by its host.
The host registers available Unit implementations. YAML selects the implementations and connections, while Module construction validates the graph and prepares its storage. Inspection, timing, diagnostics, and visualization remain read-only views of that Module.
- Registration showcase guide contains local commands, verified datasets, expected results, and recording details.
- Documentation index routes to the concept model, terminology, architecture contract, implementation evidence, and design decisions.
- V0 architecture specification is the normative source for supported behavior and boundaries.
This project is licensed under the MIT License.