Task output reuse
Make a completed task available to the next matching build.
Share the results of completed tasks with CI runners and local worktrees. Turbo restores matching outputs and runs tasks that need new results.
.boringcache.toml
workspace = "my-org/app" [adapters.turbo] tag = "turbo-cache" command = ["pnpm", "turbo", "run", "build"]
boringcache turbo
permissions: contents: read id-token: write steps: - uses: boringcache/one@1781572d7b3ec5aef652f8ba479b981439b2776b # v1.48.2 with: mode: turbo trust-policy: auto - run: pnpm turbo run build
steps: - label: Build command: > boringcache ci run --oidc-provider buildkite -- boringcache turbo
build: timeout: 1h id_tokens: BORINGCACHE_OIDC_TOKEN: aud: urn:boringcache:workload script: - boringcache ci run --oidc-provider gitlab -- boringcache turbo
Make a completed task available to the next matching build.
Keep the task definitions and commands in your repository.
Use the same workspace from both environments.
BoringCache supplies the remote-cache endpoint. Turbo still computes hashes and runs tasks.
Inspect task-cache reads, misses, transfers, and storage in one workspace.
Explore the workspace →BoringCache · GitHub runner · 4 vCPU
77.0% of 2,225 lookups over 30 builds
Build times grouped by runner, with cold and warm builds shown separately.
Turborepo
Benchmark →Workflow automation platform. Node.js monorepo with a pnpm workspace.
Average restore, build and save · lower is better
4 vCPU · 16 GB · Ubuntu 24.04 x86-64
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.
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.
| Cache | Cold | Warm | CPU |
|---|---|---|---|
| BoringCache Remote cache | 2 min 59 s | 49.4 s | Cold: AMD EPYC 7763 · Warm: AMD EPYC 9V45 |
| Depot Cache | 2 min 43 s | 43.6 s | AMD EPYC 7763 Different CPU |
| GHA Cache Local cache directory restored and saved by actions/cache | 2 min 35 s | 36.7 s | Cold: AMD EPYC 9V74 · Warm: AMD EPYC 7763 Different CPU |
| Vercel Remote Cache | 2 min 38 s | 46.4 s | Cold: Intel Xeon Platinum 8573C · Warm: AMD EPYC 7763 Different CPU |
BoringCache · GitHub runner · 4 vCPU
77.0% of 2,225 lookups over 30 builds
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
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 turbo
We use cookies to understand how people use BoringCache. Privacy policy