What is Kache used for?

Kache is a zero-copy, content-addressed compiler cache for Rust, C/C++ and CUDA that reuses build outputs across worktrees, branches and CI runs. It is a good fit for speeding up Rust builds across git worktrees, sharing build caches between CI runs and cutting disk usage from duplicate build outputs.

Is Kache open source?

Yes. Kache is open source under the Apache-2.0 licence. Its source code is on GitHub at kunobi-ninja/kache and is written mainly in Rust.

Yes. Kache is open source, so the software itself is free to use.

What are some alternatives to Kache?

Similar open-source tools in the CI/CD & DevOps category include NativeLink, Danger JS and Danger. SaaS products in the same category include Blacksmith, Depot and Travis CI.

Is Kache actively maintained?

Yes. The most recent commit to Kache was on 2 October 2026, and the latest release is v0.28.1, published on 29 September 2026. The project has 1k stars on GitHub.

Kache: open-source CI/CD & DevOps

About Kache

Kache, built by Kunobi, is a compiler cache for Rust, C and C++ and CUDA. It keys every compiler invocation by the content of its inputs, so something built once is restored instead of rebuilt in your next worktree, branch or CI run. Cargo commands stay the same, because it plugs in as the rustc wrapper after a one-time init command.

A compiler wrapper hashes the inputs that change the output, normalizing machine-local paths so two worktrees of the same revision produce the same key. Outputs live in a local content-addressed store that uses hardlinks to avoid copies and wasted disk, and they can be shared through S3-compatible or filesystem remotes, with an optional background daemon. It supports Linux, macOS and Windows on x86_64 and ARM, and a comparison with sccache and benchmarks are published.

Kache is written in Rust and licensed under Apache-2.0. Installation is available through cargo install, Homebrew, APT, AUR, winget, Scoop, Chocolatey, mise and Nix. It runs on developer machines and in CI, and suits teams with large Rust or C++ builds who want faster iterations.

Key features

Content-addressed compiler cache
Zero-copy storage using hardlinks
Rust, C/C++, and CUDA support
Sharing through S3-compatible remotes
Reuse across worktrees and branches
Packages for Homebrew, APT, and winget

Good fit for

→Speeding up Rust builds across git worktrees
→Sharing build caches between CI runs
→Cutting disk usage from duplicate build outputs

Built with: Rust
Tags: build-cache; rust; compiler-cache; ci; cpp; cuda; sccache-alternative; developer-tools; s3

Kache: questions and answers

What is Kache used for?: Kache is a zero-copy, content-addressed compiler cache for Rust, C/C++ and CUDA that reuses build outputs across worktrees, branches and CI runs. It is a good fit for speeding up Rust builds across git worktrees, sharing build caches between CI runs and cutting disk usage from duplicate build outputs.
Is Kache open source?: Yes. Kache is open source under the Apache-2.0 licence. Its source code is on GitHub at kunobi-ninja/kache and is written mainly in Rust.
Is Kache free?: Yes. Kache is open source, so the software itself is free to use.
What are some alternatives to Kache?: Similar open-source tools in the CI/CD & DevOps category include NativeLink, Danger JS and Danger. SaaS products in the same category include Blacksmith, Depot and Travis CI.
Is Kache actively maintained?: Yes. The most recent commit to Kache was on 2 October 2026, and the latest release is v0.28.1, published on 29 September 2026. The project has 1k stars on GitHub.