| Cost
[1]
| Free on all plans, subject to fair use: uploads of 100 GB/month (Hobby), 1 TB/month (Pro) or 4 TB/month (Enterprise). | Runs on your Cloudflare account; the resources it uses are on your Cloudflare bill. |
| Who operates it
[1]
| Vercel. | You, on your Cloudflare account (R2, D1, KV, Durable Objects). |
| CI authentication
[2]
| OIDC: vercel/setup-turborepo-remote-cache-action exchanges a GitHub OIDC token for a short-lived Turborepo token. Other providers can exchange their own OIDC token. A team-scoped personal access token is the fallback. | In GitHub Actions, setup-cacheflow mints a GitHub OIDC token (no stored secret) and exports TURBO_API, TURBO_TOKEN and TURBO_TEAM. Elsewhere, an operator-issued token. |
| Developer laptops
[1]
| Each developer runs turbo login and turbo link. | An operator-issued token. |
| Sharing scope
[1]
| The Vercel team: artifacts are shared with all of the team’s projects and members. | The GitHub organization: default-branch artifacts are read by every repository and branch of the owner. Other branches read and write only within their own repository. |
| Who can write | Not covered in the cited references. | The first write to a hash wins; later writes leave it unchanged. On the OIDC path a job on any other branch writes only to that branch, in its own repository, so a pull request cannot change what main replays. Default-branch pushes write to a scope shared by all of the owner’s repositories, so any of them can seed what the others replay. Events outsiders can trigger, such as pull_request_target or issue_comment, write to a quarantined scope. Operator-issued tokens are read-only unless issued writable. |
| Retention
[1]
| Uploaded artifacts expire automatically after 7 days. Team owners can clear the cache at any time. | Artifacts expire 7 days after last access (sliding: each hit extends it; configurable with TURBO_ARTIFACT_TTL_DAYS). A full namespace evicts its least recently used artifacts instead of refusing the upload. |
| Rate limits
[1]
| Fair-use artifact requests: 100/minute (Hobby), 10,000/minute (Pro and Enterprise). | Not published. |
| Build tools
[1]
| Turborepo natively; Nx and Rush through Vercel’s Remote Cache SDK plugins. | Turborepo only. No Nx, Bazel or Gradle remote-cache protocol. |
| Usage insight
[1]
| Artifact counts, sizes and a “time saved” metric. | Turborepo downloads and uploads are recorded with bytes; batch-lookup misses are not. Turborepo content hashes are recorded as-is, by design. A per-repository summary is operator-only; there is no tenant view yet. |
| Beyond Turborepo | Not compared. | The same deployment serves the GitHub Actions cache and artifact services, and a CLI and Python SDK for generic caching. |