Skip to content

Cache

Shared Build Cache

Make completed build work available to the next machine. Reuse native tool results and directory caches across CI and local development without changing runner providers.

Shared build cache One workspace

Completed build work

  • Compiler results
  • Dependencies and task outputs
  • Docker layers

Hosted CI

Self-hosted

Local builds

Build time by tool

Average restore, build and save time for one public project per tool, on the same runner class and commits as other caches.

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

All published projects, runners and caches are on the benchmark page. See all benchmarks →

Restore dependencies in seconds. Send less when they change.

BoringCache restored a 2.7 GB dependency cache in 10.0–17.1 seconds across four CI providers. Saving it after a dependency change sent about 90% less data than the compared caches.

PostHog pnpm dependency restore 2.7 GB · 163,161 files · 4 vCPU Linux x86-64
Runner Compared cache BoringCache restore Other restore
GitHub GitHub Actions cache 17.1 s 17.2 s
Depot Depot runner cache 11.5 s 5.7 s
Namespace GitHub Actions cache 11.9 s 18.7 s
Blacksmith Blacksmith cache 10.0 s 15.5 s
Saving PostHog's pnpm cache 4 vCPU Linux x86-64
Runner / cache Initial save Initial egress Reuse save Reuse egress
GitHub / BoringCache 15.7 s 117 MB 9.5 s 76 MB
GitHub / Actions cache 14.1 s 757 MB 17.3 s 757 MB
Depot / BoringCache 8.2 s 117 MB 6.0 s 76 MB
Depot / Depot runner cache 10.9 s 756 MB 10.5 s 759 MB
Namespace / BoringCache 9.6 s 114 MB 6.8 s 72 MB
Namespace / Actions cache 7.3 s 743 MB 7.4 s 727 MB
Blacksmith / BoringCache 10.6 s 113 MB 9.5 s 72 MB
Blacksmith / Blacksmith cache 6.1 s 722 MB 7.0 s 723 MB

One run per cache and runner. Saves use an existing workspace: the initial save uses a new key, and the reuse save follows a dependency change. Egress is data sent during the save.

Read the build and cross-provider restore results →

Upload the changes. Keep less duplicated data.

Matching cache content is stored once within a workspace. Related builds can reuse existing data instead of uploading and storing another full copy.

One workspace

Cache entry 1

A B C

Cache entry 2

A B D
Stored chunks
A B C D

Shared cache. Fast reads on the build machine.

Local serving and preloading help supported tools read cached results with less waiting. Data missing locally is fetched from the workspace.

Bring reusable state to fresh runners and keep local data between builds on persistent machines.

Inspect reuse and transfers →

2.7 ms

Median cache read time

Median of tool-reported project averages across 3 benchmarks. Hits can be served locally after prefetch.

On the build machine

Your build tools

Native cache integrations

BoringCache CLI

Local hit → serve cached data

Fetch data missing locally

Shared workspace cache

Docker build cache

A changed Docker layer need not mean a cold build.

Share layers, then add package and compiler caches for work inside instructions that have to run again.

Explore Docker caching →

Docker layers

Reuse an unchanged instruction's output.

Compiler and tool caches

Reuse matching results when an instruction runs again.

Persistent cache mounts

Keep package downloads and build directories between runs.

1.89×

Faster Docker builds

Best Docker result against the GitHub Actions cache on the same runner class.

Choose who can contribute to shared cache.

Reuse does not have to mean giving every job write access. Keep access scoped to the workspaces each job needs.

Explore security →

Separate readers and publishers

  • Trusted CI jobs Publish shared cache for the next build Read + publish
  • Pull requests Reuse cache without replacing it Read only
  • Sandboxes and agents Reuse cache and keep new outputs local Read only

Connect supported CI through OIDC instead of keeping a reusable BoringCache secret in your workflow.

Try the next build with shared cache.

Start with one tool in one repository. Try it for 30 days. No credit card required.

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