Cachely is a managed remote cache for monorepos that shares build artifacts across CI and developer machines to cut build times, with built-in ROI tracking and cache-poisoning protection (CVE-2025-36852).
What is Cachely?
Cachely is a managed remote-cache backend for build tools like Nx, Turborepo, Gradle, and Bazel. It takes build-task content hashes and returns cached artifacts from Cloudflare’s edge, or accepts uploads on cache misses. The product is built by Cachely (no parent company stated) and runs entirely on managed Cloudflare R2 storage — no servers to provision, patch, or secure.
Key Features
- Shared remote cache — Works natively with Nx (self-hosted protocol), Turborepo (Vercel Remote Cache protocol), Gradle (HTTP Build Cache v1), and Bazel (HTTP action cache and CAS). Set two environment variables (
NX_SELF_HOSTED_REMOTE_CACHE_SERVER and a token) to get started.
- Read/write token scoping — Issue per-pipeline or per-developer tokens with read-only or read-write permissions. Revoke any token in one click without affecting others. Read-only tokens for PR/fork builds block untrusted writes, preventing the CVE-2025-36852 cache-poisoning attack.
- ROI and optimization dashboard — Tracks cache hit rate, slowest tasks per project, estimated CI minutes saved, and dollar savings (using a configurable CI cost per minute). Suggests which tasks to cache aggressively.
- Immutable writes — Cachely enforces the Nx OpenAPI spec:
PUT on an existing hash returns 409 Conflict instead of overwriting, neutralizing the race condition exploited by cache-poisoning attacks.
- Managed Cloudflare R2 storage — Artifacts are stored with workspace isolation, auto-expire after retention, and are served from edge in milliseconds.
- No per-seat pricing — Flat subscription with a free tier for individual developers; no per-user or per-workspace fees.
Who is it for?
- Nx monorepo teams — Teams already using (or considering) the Nx self-hosted remote cache who want a managed backend instead of running their own server.
- CI-heavy engineering teams — Teams burning CI minutes on rebuilds of unchanged tasks; one warm cache shared across CI runners and laptops reduces repeated builds.
- Engineering leads needing to prove caching ROI — Leads who need concrete numbers (minutes saved, cost reclaimed per project) to justify tooling spend.
- Teams that want to avoid cache-infra ops — No bucket provisioning, IAM management, or security patching; Cachely handles storage and access control.
What can you do with Cachely?
- Speed up PR builds — On PRs touching a small slice of the monorepo, most tasks return from cache in milliseconds instead of minutes of cold rebuilds. Typical hit rate after week one: 60–80%.
- Prove CI cost savings — Cachely multiplies each cache hit by that task’s historical cold runtime and displays estimated CI minutes and dollars saved per week, per project, per token. Example: if
nx build web-app takes 4m 20s cold and is served from cache 31 times in a week, saved time is ~134 minutes.
- Protect against cache poisoning — Issue read-only tokens to untrusted CI runs (forks, PRs) so they can read the cache but never write, closing CVE-2025-36852. See the CVE writeup and Cachely’s practical guide.
How does Cachely work?
- Sign in with Google, create a workspace, and generate an API token scoped to it.
- Set two environment variables in CI and local environments:
NX_SELF_HOSTED_REMOTE_CACHE_SERVER=https://remote.cachely.dev and NX_SELF_HOSTED_REMOTE_CACHE_ACCESS_TOKEN=<token>. Builds immediately start sharing cache.
- Monitor hit rates, slowest tasks, and savings on the dashboard. Tokens can be toggled read-only/read-write or revoked at any time.
