Completed paths
Retrieve published outputs on a fresh machine.
Share completed store paths and their dependencies with compatible Linux and macOS builds. Nix keeps its derivations and substitution rules.
.boringcache.toml
workspace = "my-org/app" [adapters.nix] tag = "nix-cache" command = ["nix", "build", "."]
boringcache nix
permissions: contents: read id-token: write steps: - uses: boringcache/one@1781572d7b3ec5aef652f8ba479b981439b2776b # v1.48.2 with: mode: nix trust-policy: auto - run: nix build .
steps: - label: Build command: > boringcache ci run --oidc-provider buildkite -- boringcache nix
build: timeout: 1h id_tokens: BORINGCACHE_OIDC_TOKEN: aud: urn:boringcache:workload script: - boringcache ci run --oidc-provider gitlab -- boringcache nix
Retrieve published outputs on a fresh machine.
Make the required output dependencies available too.
Keep global Nix signature checks enabled.
BoringCache provides the HTTP cache endpoint. For multi-user Nix, the runner identity needs the trusted-user permissions required by the per-command setup.
Inspect binary-cache reads, transfers, and published cache data in your workspace.
Explore the workspace →BoringCache · GitHub runner · 4 vCPU
96.2% of 179,564 lookups over 30 builds
Build times grouped by runner, with cold and warm builds shown separately.
Nix
Benchmark →Code editor written in Rust.
Average restore, build and save · lower is better
4 vCPU · 16 GB · Ubuntu 24.04 x86-64
Builds of one commit can land on different CPU models. These ratios use only the build pairs where both caches ran on the same model; above 1.00× means BoringCache's total time over those pairs was lower.
Each table is one workflow run with one build per cache. A row marked Different CPU ran on another CPU model than BoringCache at the same level, so part of its time difference can come from the hardware.
| Cache | Cold | Warm | CPU |
|---|---|---|---|
| BoringCache Binary cache | 1 h 8 min | 4 min 19 s | Cold: AMD EPYC 9V45 · Warm: AMD EPYC 7763 |
| Cachix | 1 h 41 min | 4 min 1 s | Intel Xeon Platinum 8573C Different CPU |
4 vCPU · 16 GB · Ubuntu 24.04 x86-64
AMD EPYC 9R45
BoringCache · GitHub runner · 4 vCPU
96.2% of 179,564 lookups over 30 builds
Give consumers restore access and publishers a separate permission. Connect supported CI through OIDC or use scoped credentials.
Connect your CI →Separate readers and publishers
Install the CLI. Run onboarding to connect your repository and configure your cache.
30-day trial. No credit card required.
curl -sSL https://install.boringcache.com/install.sh | sh
boringcache onboard
boringcache nix
We use cookies to understand how people use BoringCache. Privacy policy