CacheFlow vs caches bundled with CI runner vendors

As of

Third-party GitHub Actions runner vendors bundle a cache with their runners. Several make stock actions/cache use it with no workflow change; some place the cache close to the runner or on a volume attached to it. You get the cache by running your jobs on that vendor’s runners.

CacheFlow is not a runner. It is a cache and artifact service you run on your Cloudflare account for runners whose environment you control, and it stays the same whichever machines you run on. It serves bytes from R2 over the internet, and makes no speed claim against caches that sit next to the runner.

At a glance

Cache How the cache attachesWorkflow changeRetentionBranch scoping
Blacksmith [1] Official GitHub and popular third-party cache actions talk to a cache stored in the same datacenter as the runners. None. 25 GB free per repository per week; least recently used entries last accessed more than 7 days ago are evicted. Each entry is scoped to its branch or tag.
Namespace [2] [3] Cache Volumes: NVMe-backed storage attached to the runner instance and persisted across runs. Add nscloud-cache-action, which bind-mounts the listed directories onto the volume. The docs suggest disabling GitHub’s built-in caching. Volumes start at 20 GB per runner profile. Retention not documented. An allow-list of branches (for example main) may commit changes to a volume; other branches can read it but their changes are not persisted.
Depot [4] [5] [6] actions/cache uses Depot Cache on Depot runners. Depot Cache also serves Bazel, Go, Turborepo, Nx, sccache, Pants and Gradle, from any CI. None on Depot runners. 7, 14 (default) or 30 days, or a size limit. 25 GB (Developer) or 250 GB (Startup) included, then $0.20/GB/month. Not isolated by branch: entries from all branches share one namespace.
WarpBuild [7] Setup actions use WarpBuild Cache automatically on WarpBuild runners. Replace actions/cache@v4 with warpbuilds/cache for direct caching. Expires 7 days after last use. Hosted storage $0.20/GB-month plus $0.0001 per operation. Scoped to key, version and branch.
RunsOn [8] Magic Cache: a sidecar on the runner forwards cache requests to an S3 bucket in your own AWS VPC. Works with actions/cache, setup-* actions and Docker type=gha. Add the extras=s3-cache job label and runs-on/action@v2 (or enable it for a runner fleet in Terraform). Fixed window, 10 days by default; hits do not extend it. No RunsOn size cap. Opt-in isolation by repository and branch (v3.2+).
CacheFlow Serves the Actions cache and artifact protocols from your Cloudflare account (R2) to runners whose environment sets ACTIONS_RESULTS_URL. None. Namespace size limits; no time-based eviction. Drop-in jobs follow GitHub’s own cache grant, including the real default branch. OIDC jobs write to their own ref and read through the pull request base, then configured fallback branches (main and master by default).

Where CacheFlow is the better fit

  • You run your own runners (or a runner platform that lets you set the runner environment) and want one cache that does not depend on a runner vendor.
  • Release and deploy jobs should restore only what a trusted build saved: CacheFlow records provenance per entry, and a trusted-consumer policy limits the jobs it covers to entries from push, schedule and manual runs on the protected branch.
  • You want the GitHub Actions cache, artifacts and the Turborepo remote cache served by one deployment in a Cloudflare account you own, with its operations recorded in one place.

Where a runner vendor’s cache is the better fit

  • You want managed runners, and the cache is part of the package with nothing extra to operate.
  • Restore speed is the priority: Blacksmith colocates the cache with its runners and Namespace attaches it as a volume, while CacheFlow serves bytes over the internet and has no measured speed advantage.
  • You need remote caching for Bazel, Gradle or Nx: Depot Cache documents those; CacheFlow supports Turborepo, and sccache and Pants through the Actions cache.
  • You want cache data in your own AWS account: RunsOn’s Magic Cache writes to an S3 bucket in your VPC.
  • Your caches exceed what you want to operate yourself, and a vendor’s included storage or per-GB pricing is simpler.

How to switch

Moving to CacheFlow means running jobs on runners whose environment you control and setting one variable on them. Workflows that use stock actions/cache need no change. If you replaced it with a vendor action (such as nscloud-cache-action or warpbuilds/cache), switch back to actions/cache.

# runner environment: set once, per runner pool
ACTIONS_RESULTS_URL=https://cache.cacheflow.sh/

# your workflows: unchanged
- uses: actions/cache@v4
- uses: Swatinem/rust-cache@v2
- uses: actions/upload-artifact@v4

Sources

Claims about other products come from their public documentation, retrieved on . Claims about CacheFlow describe what ships today; planned work is marked as planned.

  1. Blacksmith Docs: Dependencies cache: https://docs.blacksmith.sh/blacksmith-caching/dependencies-actions (retrieved 2026-09-28)
  2. Namespace Docs: Caching in GitHub Actions: https://namespace.so/docs/solutions/github-actions/caching (retrieved 2026-09-28)
  3. Namespace Docs: namespacelabs/nscloud-cache-action: https://namespace.so/docs/reference/github-actions/nscloud-cache-action (retrieved 2026-09-28)
  4. Depot Docs: Cache, GitHub Actions integration: https://depot.dev/docs/cache/integrations/github-actions (retrieved 2026-09-28)
  5. Depot Docs: Depot GitHub Actions runners: https://depot.dev/docs/github-actions/overview (retrieved 2026-09-28)
  6. Depot Docs: Depot Cache overview: https://depot.dev/docs/cache/overview (retrieved 2026-09-28)
  7. WarpBuild Docs: Caching: https://www.warpbuild.com/docs/ci/features/caching (retrieved 2026-09-28)
  8. RunsOn Docs: Magic Cache for GitHub Actions: https://runs-on.com/docs/performance/caching/actions/ (retrieved 2026-09-28)