One command clones any project and provisions its exact toolchain. Reprobuild replaces your Dockerfile, Nix flake, Makefile, compose file, and Terraform module with one compile-time-verified model — builds, dependencies, dev environments, and services, with correct caching everywhere.
Every number links to a benchmark you can rerun on your own hardware. Figures shown here are illustrative examples for this prototype — the published site will carry live, reproducible measurements, and we never print a number we can’t reproduce.
Not just your software — anyone’s. One command clones the source and provisions the exact toolchain, libraries, and services to build it. When the bug turns out to be a level deeper, you pull that dependency in beside it — no container to rebuild, no environment to reconcile.
A Firefox checkout plus every tool and library needed to build it — on Linux, macOS, Windows, or *BSD. No prior setup on the machine.
The bug is really in Cairo? Run this from inside the same workspace. Your checkout grows to include Cairo, and Firefox builds against your local copy.
Reprobuild describes your project once, in a typed repro.nim model — and that one description is the build, the dependencies, the dev shell, the services, and the deployment. The same model your team runs is the one CI runs and the one that caches.
On a warm incremental build — monitoring on — Reprobuild’s scheduler matches Ninja, one of the fastest build engines there is. Split the work across machines and it scales nearly linearly, because every action is content-addressed and independently cacheable.
Illustrative example data for this design prototype. Every figure on the live site will link to a rerunnable benchmark in the public repo.
The CLI and your local cache are MIT and free, forever. When your team wants the shared, fast, and provable versions, they run on our infrastructure — priced per second of compute, never per seat of the tool.
A shared, remote binary cache your whole team and CI hit. Because it’s content-addressed over complete inputs, a hit is never a wrong answer — your team already built that, and nobody should build it twice.
Reprobuild Cache →One line — runs-on: reprobuild — and every job starts warm from the shared cache. No build rewrite, no migration quarter. The wedge first, the graph later.
Distributed execution across the fleet, metered by the second. A cache miss becomes a burst, not a coffee break — and the result is content-addressed, so everyone gets it next time for free.
Reprobuild Cloud →A cache is only useful if it is never wrong. Reprobuild fingerprints the complete inputs to every step — sources, tools, environment — and addresses the result by that fingerprint. No timestamps, no make clean folklore, no guessing.
Every output is keyed by the fingerprint of its complete inputs. Same inputs anywhere — your laptop, a teammate’s, CI — means the same result, byte for byte.
io-mon observes the files a build actually touches, so an undeclared dependency can’t hide. BuildXL’s idea — shipped cross-platform and typed.
A build-twice byte-equality gate in CI proves reproducibility instead of asserting it. Every claim on this site is a build target you can rerun.
The monitored cache runs where your team runs — Windows included, not as a footnote. Correct and typed and cross-platform.
repro develop <x> with local develop-mode overridesrepro.nim configurationrepro shell / repro dev)On the roadmap — shared/remote binary cache and Build Cloud, distributed execution, sandboxes and fleet management, hot-code reload with CodeTracer replay, and ReproOS with hardware attestation. We don’t ship a page before the product works, and every published number resolves to a benchmark you can rerun.