Home / Use cases
Where rninja earns its keep
rninja is not a new build system and it is not a compiler cache you have to configure. It executes the build.ninja you already have, faster. These are the jobs where the cache and scheduler show up in your wall clock.
Local development
CMake & C/C++ incremental builds
Kill the two-minute inner loop on a large CMake + Ninja C/C++ project without touching your CMakeLists.
Read the walkthrough → Continuous integrationCI pipelines with warm caches
Turn the second and third CI build of the day into near-no-ops by sharing a content-addressed cache across runs.
Read the walkthrough → Teams & monoreposMonorepos with a shared remote cache
Let teams building overlapping subgraphs from the same sources reuse each other's results automatically.
Read the walkthrough →New to the mechanics? Start with how it works or the quickstart.