Turborepo Remote Cache

This Worker implements Turborepo's remote cache API, so CI runners and developer laptops can share build artifacts without Vercel's hosted cache. A bearer token protects the endpoint, and a daily Cron Trigger deletes old artifacts.

Artifacts land in an R2 bucket (turborepo-cache, bound as R2_STORE) or, after a configuration change, in Workers KV. Every day at 03:00 UTC a Cron Trigger removes objects older than BUCKET_OBJECT_EXPIRATION_HOURS, which defaults to 720 hours. Clients authenticate with the bearer token stored as the TURBO_TOKEN secret, and the README recommends turning on Turborepo's artifact signature verification as well. On the client side, the README puts TURBO_API, TURBO_TEAM, TURBO_TOKEN and TURBO_REMOTE_CACHE_SIGNATURE_KEY in a .env file and runs turbo through dotenv-cli. TURBO_TEAM must start with team_, and TURBO_API must not end with a slash. A VitePress documentation site covers both storage options. The repository runs CI with coverage reporting, and dependency updates are automated. Version 4.0.0 was released in January 2026.

Built for: Engineering teams with Turborepo monorepos who want remote caching in their own Cloudflare account

What you can use it for

• Share the Turborepo build cache between CI runners and developer machines
• Use Turborepo remote caching without a Vercel account
• Cut CI build times in a Turborepo monorepo by reusing cached task outputs

Deploy

• One-click · main path

  Branch master

  Deploy to Cloudflare

• CLI

  Branch master

  git clone https://github.com/AdiRishi/turborepo-remote-cache-cloudflare.git
  cd turborepo-remote-cache-cloudflare
  pnpm install
  pnpm wrangler r2 bucket create turborepo-cache
  pnpm run deploy
  echo "SECRET" | pnpm wrangler secret put TURBO_TOKEN

  Copy
  Docs

The button creates the Worker and R2 bucket. Add the TURBO_TOKEN secret, then set TURBO_API, TURBO_TEAM and TURBO_TOKEN in your Turborepo environment.

What it needs to run

• R2 bucketsturborepo-cache

Good to know

The Worker has no user interface, dashboard or usage view; it only answers Turborepo's remote cache API. Switching to KV storage means editing wrangler.jsonc.

Cost on Cloudflare

Where this comes from

• Repositoryhttps://github.com/AdiRishi/turborepo-remote-cache-cloudflare
• App websitehttps://adirishi.github.io/turborepo-remote-cache-cloudflare/
• Documentationhttps://adirishi.github.io/turborepo-remote-cache-cloudflare/introduction/getting-started

An alternative to Vercel Remote Cache.