Does BoringCache replace Turborepo?

No. Turbo still calculates task hashes and runs each task. BoringCache provides the remote-cache endpoint and shared workspace.

Can Turbo cache be restore-only in pull requests?

Yes. Use restore-only credentials for untrusted jobs and save access for trusted jobs.

Can Turbo and Docker share cache visibility?

Yes. They keep separate protocols while reporting into the same BoringCache workspace.

Turborepo remote cache

Reuse Turbo tasks across your team.

Share the results of completed tasks with CI runners and local worktrees. Turbo restores matching outputs and runs tasks that need new results.

Set up Turbo See the product

.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@f0fb9b2d926a32b10c543e92093ba00c5a291b79 # v1.33.0
    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

How BoringCache fits your build.

Task output reuse

Make a completed task available to the next matching build.

Your existing pipeline

Keep the task definitions and commands in your repository.

CI and local access

Use the same workspace from both environments.

Keep Turbo’s task decisions. Share their results.

BoringCache supplies the remote-cache endpoint. Turbo still computes hashes and runs tasks.

See cache activity across your monorepo.

Inspect task-cache reads, misses, transfers, and storage in one workspace.

Explore the workspace →

n8n-io/n8n

Cache stored

BoringCache0.775 GiB

actions/cache12.773 GiB

94%

Less cache stored

n8n-io/n8n · compared with actions/cache

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

Before you connect.

Does BoringCache replace Turborepo?: No. Turbo still calculates task hashes and runs each task. BoringCache provides the remote-cache endpoint and shared workspace.
Can Turbo cache be restore-only in pull requests?: Yes. Use restore-only credentials for untrusted jobs and save access for trusted jobs.
Can Turbo and Docker share cache visibility?: Yes. They keep separate protocols while reporting into the same BoringCache workspace.

Read the Turbo setup guide →

Use other tools in the same workspace.

Explore build cache →

Start with your next Turbo build.

Install the CLI. Run onboarding to connect your repository and configure your cache.

30 GB of cache free. No credit card required.

Set up Turbo Use GitHub Actions

curl -sSL https://install.boringcache.com/install.sh | sh
boringcache onboard
boringcache turbo