Skip to content
sccache remote cache

Share compiler results across machines.

Give Rust, C, and C++ builds access to one shared sccache store. Reuse eligible compilations from CI, containers, and local development.

.boringcache.toml
workspace = "my-org/app"

[adapters.sccache]
tag = "sccache-cache"
command = ["cargo", "build", "--release"]
boringcache sccache

How BoringCache fits your build.

Compiler reuse

sccache decides whether an invocation can use a stored result.

Shared storage

Matching compiler-cache data is stored once in the workspace.

Visible activity

Inspect compiler-cache reads, writes, and transfers.

Use compiler caching on its own or with Cargo.

The sccache adapter connects compiler caching to your command. For Rust builds that also need dependency and target-state reuse, use the Cargo integration.

See compiler-cache reuse in each build.

Inspect cache hits, misses, and transfers from sccache in your workspace.

Explore the workspace →
Deno · Workspace insights
Cache hits

BoringCache · GitHub runner · 4 vCPU

97.1% of 20,352 lookups over 8 builds

Served from the runner
Under 1 ms per read
Measured by sccache
2.0 ms per hit
Read from cache
9.62 GB

Rust benchmark

All Rust results →

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

Deno

Rust

Benchmark →

JavaScript and TypeScript runtime written in Rust.

Average restore, build and save · lower is better

GitHub runner

4 vCPU · 16 GB · Ubuntu 24.04 x86-64

Base · sccache compiler cache

BoringCache
26 min 0 s 8 builds
Depot Cache
29 min 25 s 8 builds
GHA Cache
29 min 0 s 8 builds
kache
26 min 6 s 8 builds

Plus · sccache, Cargo registry and target directory

BoringCache +
22 min 0 s 8 builds
GHA Cache + target
25 min 13 s 8 builds
mr-boxington
33 min 4 s 8 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.

Depot Cache vs BoringCache
1.13× · 2 of 8
GHA Cache vs BoringCache
1.04× · 1 of 8
kache vs BoringCache
1.13× · 2 of 8
GHA Cache + target vs BoringCache +
1.09× · 1 of 8
mr-boxington vs BoringCache +
1.51× · 2 of 8
5 CPU models recorded
BoringCache · sccache compiler cache
AMD EPYC 9V74 (4 builds) · AMD EPYC 9V45 (2 builds) · AMD EPYC 7763 (1 build) · Intel Xeon Platinum 8370C (1 build)
BoringCache + · sccache, Cargo registry and target directory
AMD EPYC 7763 (5 builds) · AMD EPYC 9V74 (3 builds)
Depot Cache · sccache WebDAV backend
AMD EPYC 9V74 (4 builds) · AMD EPYC 7763 (2 builds) · Intel Xeon Platinum 8573C (1 build) · AMD EPYC 9V45 (1 build)
GHA Cache · sccache GitHub Actions backend
AMD EPYC 7763 (3 builds) · Intel Xeon Platinum 8573C (2 builds) · AMD EPYC 9V74 (2 builds) · AMD EPYC 9V45 (1 build)
kache
AMD EPYC 9V45 (3 builds) · AMD EPYC 7763 (2 builds) · AMD EPYC 9V74 (2 builds) · Intel Xeon Platinum 8573C (1 build)
GHA Cache + target · sccache plus actions/cache for registry and target
AMD EPYC 9V74 (3 builds) · AMD EPYC 9V45 (2 builds) · AMD EPYC 7763 (2 builds) · Intel Xeon Platinum 8573C (1 build)
mr-boxington
AMD EPYC 7763 (4 builds) · Intel Xeon Platinum 8573C (2 builds) · AMD EPYC 9V45 (1 build) · Intel Xeon Platinum 8370C (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
Base · sccache compiler cache
BoringCache sccache compiler cache 39 min 29 s 29 min 26 s AMD EPYC 7763
Depot Cache sccache WebDAV backend 43 min 11 s 32 min 55 s AMD EPYC 7763
GHA Cache sccache GitHub Actions backend 40 min 35 s 34 min 39 s Cold: Intel Xeon Platinum 8573C · Warm: AMD EPYC 9V74 Different CPU
kache 33 min 0 s 80.2 s Cold: AMD EPYC 9V74 · Warm: AMD EPYC 7763 Different CPU
Plus · sccache, Cargo registry and target directory
BoringCache + sccache, Cargo registry and target directory 41 min 52 s 59.2 s Cold: AMD EPYC 7763 · Warm: AMD EPYC 9V45
GHA Cache + target sccache plus actions/cache for registry and target 42 min 23 s 28 min 14 s AMD EPYC 7763 Different CPU
mr-boxington 39 min 24 s 34 min 8 s Cold: Intel Xeon Platinum 8573C · Warm: AMD EPYC 9V74 Different CPU
Cache hits

BoringCache · GitHub runner · 4 vCPU

97.1% of 20,352 lookups over 8 builds

Served from the runner
Under 1 ms per read
Measured by sccache
2.0 ms per hit
Read from cache
9.62 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 sccache?
No. sccache still wraps the compiler and decides cache hits. BoringCache provides the shared remote cache endpoint.
Is this only for Rust?
No. sccache is commonly used for Rust, C, and C++ compiler outputs.
Read the sccache setup guide →

Set up sccache 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 sccache