- Do we have to change our workflows?
- Not for the Actions cache and artifacts. Point your runners’ environment at CacheFlow once, and stock actions/cache, setup-node, Swatinem/rust-cache and upload-artifact use it unchanged. On GitHub-hosted runners the same workflows keep using GitHub’s cache. The Turborepo remote cache takes one setup-cacheflow step per workflow.
- Where does our data live?
- In your Cloudflare account: bytes in R2, key ownership in D1, a read path in KV and in-flight sessions in Durable Objects. Telemetry records Actions cache keys and artifact names only as a keyed hash. We are also planning a managed plan, run by CacheFlow for you.
- What does it cost?
- The Cloudflare resources CacheFlow uses are billed to your own Cloudflare account, and R2 charges no egress fees. We will share pricing for CacheFlow itself with early-access teams.
- Is it faster than GitHub’s cache?
- We make no speed claim. Bytes come from Cloudflare R2 over the internet, and we have not measured a restore-speed advantage. If you need a cache next to the runner, a runner vendor’s cache may suit you better.
- How do jobs authenticate?
- Jobs using the CacheFlow actions or setup-cacheflow exchange a short-lived GitHub OIDC token. Drop-in jobs on stock actions use the runtime token GitHub already gives every job. Either way, no long-lived secret is stored in your pipelines. Other CI systems and developer laptops use a token issued by your operator.
- Can we switch back?
- Yes. CacheFlow speaks the protocols your tools already use: the Actions cache and artifact services and the Turborepo remote cache. Remove the runner setting or the setup-cacheflow step, and your workflows go back to the cache they used before.