A build cache that made CI six times faster
A content-addressed build cache daemon. A hit on one branch is a hit on every branch.

README.md · CASE STUDY
A content-addressed build cache daemon. A hit on one branch is a hit on every branch.
A content-addressed build cache daemon. A hit on one branch is a hit on every branch.
Our CI rebuilt the same objects on every branch because cache keys included the branch name. Cold pipelines took 18 minutes and engineers stopped waiting for them.
The fix
kiln keys every build step by a hash of its real inputs: source files, environment and toolchain version. Nothing else. A step that ran on main is a hit on every feature branch that did not change its inputs.
Running it
A small hot set lives in memory in front of disk, eviction runs by total size, and large objects stream in 4 MB chunks. One daemon serves 40 engineers across two companies.
Result
Median CI time fell from 18 m 04 s to 2 m 57 s, and egress dropped by 80%. The sizing guide in the repo covers teams from 10 to 100 engineers.
More projects.
Every project opens the same way: problem, fix, numbers.
Notes from the work.
Short write-ups of things that broke and how they got fixed. Plain language, real numbers.