Skip to content
Nix binary cache

Download Nix outputs instead of rebuilding them.

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

How BoringCache fits your build.

Completed paths

Retrieve published outputs on a fresh machine.

Their closures

Make the required output dependencies available too.

Scoped trust

Keep global Nix signature checks enabled.

A binary cache for your existing Nix builds.

BoringCache provides the HTTP cache endpoint. For multi-user Nix, the runner identity needs the trusted-user permissions required by the per-command setup.

See what your Nix builds restore and publish.

Inspect binary-cache reads, transfers, and published cache data in your workspace.

Explore the workspace →
Zed · Workspace insights
Cache hits

BoringCache · GitHub runner · 4 vCPU

96.2% of 179,564 lookups over 30 builds

Served from the runner
Under 1 ms per read
Read from cache
41.7 GB

Nix benchmark

All Nix results →

Build times grouped by runner, with cold and warm builds shown separately.

Zed

Nix

Benchmark →

Code editor written in Rust.

Average restore, build and save · lower is better

GitHub runner

4 vCPU · 16 GB · Ubuntu 24.04 x86-64

BoringCache
1 h 7 min 30 builds
Cachix
1 h 4 min 30 builds
Same CPU model

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.

Cachix vs BoringCache
0.99× · 12 of 30
6 CPU models recorded
BoringCache · Binary cache
AMD EPYC 7763 (18 builds) · Intel Xeon Platinum 8573C (4 builds) · Intel Xeon Platinum 8370C (3 builds) · AMD EPYC 9V45 (3 builds) · AMD EPYC 9V74 (2 builds)
Cachix
AMD EPYC 7763 (13 builds) · AMD EPYC 9V74 (5 builds) · Intel Xeon Platinum 8573C (5 builds) · AMD EPYC 9V45 (4 builds) · Intel Xeon Platinum 8370C (2 builds) · Intel Xeon 6973P-C (1 build)
Cold and warm builds

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.

One cold and warm build per cache
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
Cache hits

BoringCache · GitHub runner · 4 vCPU

96.2% of 179,564 lookups over 30 builds

Served from the runner
Under 1 ms per read
Read from cache
41.7 GB

Keep shared-cache publication in trusted jobs.

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

  • Trusted builds Publish shared cache for the next build Read + publish
  • Pull requests Restore cache without replacing it Read only
  • Local development Use a scoped credential for the workspace Scoped access

Common questions

Does BoringCache replace the Nix store?
No. Nix still handles derivations, closures, store paths, and substitution. BoringCache provides the HTTP binary-cache endpoint used for shared reads and writes.
Do Nix signature checks stay enabled?
Yes. Trust is limited to the runner-local BoringCache store for the invocation.
What changes for multi-user Nix?
The runner user or one of its groups must be listed in Nix trusted-users so the per-command substituter and hook settings can reach the daemon.
Read the Nix setup guide →

Set up Nix caching

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