Get started in five minutes

1. Create an account and a workspace. Sign in with Google and create a workspace. Your cache is stored on fully managed Cloudflare R2 - zero configuration, nothing to provision, secure, or patch.
2. Generate an API token. Open the workspace and create a token with a descriptive name (e.g. github-actions-prod or alice-laptop). Copy the raw value immediately - it is shown once and never again. See tokens and access control.
3. Point your build tool at the cache. One workspace token works for every protocol. For Nx and Lerna that is two environment variables:

   export NX_SELF_HOSTED_REMOTE_CACHE_SERVER=https://remote.cachely.dev
   export NX_SELF_HOSTED_REMOTE_CACHE_ACCESS_TOKEN=<your-token>

   Copy
4. Build something twice. The first run uploads the result (a put); every later run on any machine using a token in the same workspace downloads it instead of rebuilding (a hit).

Pick the guide for your build tool, then wire it into CI and lock the token down.

• NxTwo environment variables, the bare-host rule, and the Nx versions that share a cache.
• LernaSame protocol as Nx, plus the nx.json targets and the Lerna/Nx version matrix.
• TurborepoTURBO_API, TURBO_TOKEN, TURBO_TEAM, and how to confirm a remote hit.
• GradleHttpBuildCache in both DSLs, org.gradle.caching, and the CI-push pattern.
• BazelThe .bazelrc / user.bazelrc split, AC and CAS, and who may write.
• CI setupJob-level environment, read-only pull-request tokens, and other CI providers.
• Tokens and accessScopes, rotation, revocation, and the read-only token that stops cache poisoning.
• TroubleshootingA symptom-first index: 401, 403, 404, silent misses, and an empty dashboard.

Managed (R2). Cachely stores cache objects in Cloudflare R2 on your behalf. Zero configuration, included in the subscription. Artifacts are content-addressed and immutable: an existing cache key cannot be overwritten, so a known good build can never be silently replaced. Cachely never stores your source code, only task outputs and their content hashes.

These pages explain the concepts rather than the Cachely setup: what a remote cache is, how the Nx remote cache works, how to improve a low hit rate, and monorepo build performance.

Join the Cachely Discord to ask setup questions, compare cache configurations with other teams, and hear about protocol support as it lands. For anything account-specific - billing, quotas, a workspace you cannot reach - email hello@cachely.dev instead, so it stays off a public channel.