Reuse
See which cache reads found a result and which missed.
Demo
Compare build time and cache storage across projects, then use the same integration in your repository.
Average restore, build and save · lower is better
4 vCPU · 16 GB · Ubuntu 24.04 x86-64
Base · Image layers
Plus · Image layers, tool caches and cache mounts
1.96× on the 10 build pairs with the same CPU model
4 vCPU · 16 GB · Ubuntu 24.04 x86-64
Base · Image layers
Plus · Image layers, tool caches and cache mounts
8 vCPU · 32 GB · Ubuntu 24.04 x86-64
Base · Image layers
Plus · Image layers, tool caches and cache mounts
16 vCPU · 32 GB* · x86-64
* Builder sizes published by providers.
BoringCache on Depot runner, 8 vCPU: 5 min 58 s against 6 min 34 s on the builds both ran
4 vCPU · 16 GB · x86-64
Base · Image layers
Plus · Image layers, tool caches and cache mounts
8 vCPU · 16 GiB* · x86-64
* Builder sizes published by providers.
BoringCache on Namespace runner, 4 vCPU: 9 min 16 s against 10 min 3 s on the builds both ran
Average restore, build and save · lower is better
4 vCPU · 16 GB · Ubuntu 24.04 x86-64
Base · sccache compiler cache
Plus · sccache, Cargo registry and target directory
1.21× on the 6 build pairs with the same CPU model
8 vCPU · 32 GB · Ubuntu 24.04 x86-64
1.48× on the 29 build pairs with the same CPU model
4 vCPU · 16 GB · Ubuntu 24.04 x86-64
Base · sccache compiler cache
Plus · sccache, Cargo registry and target directory
4 vCPU · 16 GB · Ubuntu 24.04 x86-64
These runners have no other cache at the same level to compare with BoringCache.
Average restore, build and save · lower is better
4 vCPU · 16 GB · Ubuntu 24.04 x86-64
1.33× on the 1 build pair with the same CPU model
Average restore, build and save · lower is better
4 vCPU · 16 GB · Ubuntu 24.04 x86-64
2.26× on the 7 build pairs with the same CPU model
Average restore, build and save · lower is better
4 vCPU · 16 GB · Ubuntu 24.04 x86-64
1.75× on the 3 build pairs with the same CPU model
Average restore, build and save · lower is better
4 vCPU · 16 GB · Ubuntu 24.04 x86-64
1.30× on the 7 build pairs with the same CPU model
Average restore, build and save · lower is better
4 vCPU · 16 GB · Ubuntu 26.04 x86-64
1.28× on the 11 build pairs with the same CPU model
See which cache reads found a result and which missed.
Inspect the data a run restored and uploaded.
Find the tool responsible for each kind of cache activity.
Choose a tool to see its .boringcache.toml configuration and build command.
Reuse image layers across compatible builds. The CLI adds shared cache to the command in your repo configuration.
Set up Docker →workspace = "my-org/app" [adapters.docker] tag = "docker-cache" command = ["docker", "buildx", "build", "."]
boringcache docker
Share Turborepo's remote cache across developers and CI jobs. Skip tasks when their inputs already have cached results.
Set up Turborepo →workspace = "my-org/app" [adapters.turbo] tag = "turbo-cache"
boringcache turbo -- npx turbo run build
Run Cargo with dependency, target, and compiler caches from the same workspace.
Set up Cargo →workspace = "my-org/app" [adapters.cargo] tag = "rust-build" [adapters.sccache] tag = "rust-compiler"
boringcache cargo -- build --release
Connect sccache to your workspace with the CLI. Keep using your existing build and test commands.
Set up sccache →workspace = "my-org/app" [adapters.sccache] tag = "rust-compiler"
boringcache sccache -- cargo test
Use Bazel's native remote cache to reuse completed build work across your team.
Set up Bazel →workspace = "my-org/app" [adapters.bazel] tag = "bazel-cache"
boringcache bazel -- bazel build //...
Connect Gradle's build cache to your workspace. Reuse matching task outputs on the next runner or developer machine.
Set up Gradle →workspace = "my-org/app" [adapters.gradle] tag = "gradle-cache"
boringcache gradle -- ./gradlew build --build-cache
Commit .boringcache.toml once. Your CI jobs and local worktrees read the same workspace and tool definitions.
Run your configured Docker build locally. Compatible builds can reuse cache published by CI or another developer.
boringcache docker
Your committed configuration goes with the checkout. Build Docker images with shared cache while keeping the worktree's files separate.
git worktree add ../app-review -b review cd ../app-review boringcache docker
Add the Action after checkout. It reads your repo configuration and uses the workspace connection approved for your repository.
Set up GitHub Actions →permissions: contents: read id-token: write steps: - uses: boringcache/one@1781572d7b3ec5aef652f8ba479b981439b2776b # v1.48.2 with: mode: docker trust-policy: auto
With the CLI installed on your runner, run the Docker adapter through your approved Buildkite OIDC connection.
Set up Buildkite →steps: - label: Build command: > boringcache ci run --oidc-provider buildkite -- boringcache docker
With the CLI installed, connect your job through GitLab OIDC and run the same Docker command. Your approved workspace connection controls access.
Set up GitLab CI →build: timeout: 1h id_tokens: BORINGCACHE_OIDC_TOKEN: aud: urn:boringcache:workload script: - boringcache ci run --oidc-provider gitlab -- boringcache docker
Start with the part of your build you want to improve. Use the others when you need them.
Reuse dependencies, compiler results, task outputs, and Docker layers across compatible builds.
Explore Cache →Keep exact build outputs for testing, deployment, and release downloads. Choose their retention.
Explore Artifacts →Store private container images and pull them with your existing deployment tools.
Explore Registry →Approve the connection between your repository and workspace. CI jobs use workload identity to connect without a stored BoringCache secret.
Connect your CI →Separate readers and publishers
Connect one repository and inspect its first run.
curl -sSL https://install.boringcache.com/install.sh | sh cd your-project boringcache onboard
We use cookies to understand how people use BoringCache. Privacy policy