Turbo-native artifacts
Turborepo still hashes task inputs and stores task artifacts through its remote-cache API.
Getting started
On this page
j / k move between sections.
Docs / Adapter commands / Turborepo
Keep Turbo's task hashes, graph, and outputs. The adapter supplies the remote-cache endpoint and short-lived process credential.
Turborepo still hashes task inputs and stores task artifacts through its remote-cache API.
Use the same cache from GitHub Actions, another CI runner, or a local shell.
Restore from pull requests. Save from trusted jobs.
Keep the command and cache tag in .boringcache.toml, then use the same boringcache turbo entrypoint locally and in CI.
[adapters.turbo] tag = "turbo-cache" command = ["turbo", "run", "build"] # Run: boringcache turbo
The Action starts the Turbo adapter and gives the later Turbo command its remote-cache environment.
- uses: boringcache/one@1781572d7b3ec5aef652f8ba479b981439b2776b # v1.48.2 with: trust-policy: auto mode: turbo - run: pnpm turbo run build
Approve the repository through Connect CI and grant the job contents: read and id-token: write. The Action uses that Machine connection. Pull requests restore by default; trusted jobs may publish. See the authentication example in the GitHub Actions reference for scoped credentials when OIDC is unavailable.
n8n builds the same upstream commits with BoringCache, Depot Cache, GHA Cache and Vercel Remote Cache on the same runner classes.
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
Check the tool's own reference when you need cache-key rules, build settings, or version-specific behavior.
Compare every supported command, protocol, and Action mode in one place.
Adapter command index →Need help or found something unclear? Open an issue or browse the CLI repo.
We use cookies to understand how people use BoringCache. Privacy policy