Skip to content

Demo

See what changes with BoringCache.

Compare build time and cache storage across projects, then use the same integration in your repository.

Benchmark →

PostHog

Average restore, build and save · lower is better

GitHub runner

4 vCPU · 16 GB · Ubuntu 24.04 x86-64

Base · Image layers

BoringCache
15 min 2 s 30 builds
GHA Cache
28 min 22 s 30 builds
GHCR
20 min 58 s 30 builds

Plus · Image layers, tool caches and cache mounts

BoringCache +
18 min 1 s 30 builds
GHA Cache Dance
41 min 8 s 30 builds
Saved per build
13 min 20 s
Faster than GHA Cache
1.89×

1.96× on the 10 build pairs with the same CPU model

Builds compared
30

Know what to look at next.

Reuse

See which cache reads found a result and which missed.

Transfers

Inspect the data a run restored and uploaded.

Tools

Find the tool responsible for each kind of cache activity.

Inspect the same activity in your build.

Choose a tool to see its .boringcache.toml configuration and build command.

Keep your Docker build command.

Reuse image layers across compatible builds. The CLI adds shared cache to the command in your repo configuration.

Set up Docker →
.boringcache.toml
workspace = "my-org/app"

[adapters.docker]
tag = "docker-cache"
command = ["docker", "buildx", "build", "."]
Docker
boringcache docker
Explore all supported tools →

Use the same cache wherever you build.

Commit .boringcache.toml once. Your CI jobs and local worktrees read the same workspace and tool definitions.

Use cache from earlier builds.

Run your configured Docker build locally. Compatible builds can reuse cache published by CI or another developer.

Local build
boringcache docker

Cache, Artifacts and Registry

Start with the part of your build you want to improve. Use the others when you need them.

Connect CI with OIDC. Control who can publish.

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

  • Trusted jobs publish Give trusted workflows permission to publish new cache. Keep access scoped to the workspace they need. Read + publish
  • Pull requests read Let pull requests reuse published cache without replacing the cache other builds depend on. Read only

Try it on a build you know.

Connect one repository and inspect its first run.

curl -sSL https://install.boringcache.com/install.sh | sh
cd your-project
boringcache onboard