Welcome to the Cachely blog. This is where we will write about remote caching for Nx monorepos: how it works, where teams lose time, how to keep a shared cache safe, and what we are building.
Why a blog
Cachely is a managed implementation of the Nx self-hosted remote cache. The product is intentionally small and sharp, but the topics around it are not: build performance, CI economics, and supply-chain safety all touch the cache. A changelog cannot do them justice, so we are starting here.
What to expect
- Build performance. Practical notes on cache hit rates, task hashing, and why your CI is slower than it needs to be.
- Cache safety. Why a shared cache is a supply-chain surface, and how read-only tokens close cache-poisoning attacks like
CVE-2025-36852(CREEP). - Product updates. What we ship, what we learn, and where the roadmap is heading (Turborepo and Bazel are on it).
New here? Start with how to improve CI times, then read what makes a good build cache and the CREEP breakdown.
Start here
If you want the short version of how Cachely works, the docs walk through connecting an Nx monorepo in about five minutes: create a workspace, generate a token, set two environment variables, and your team starts sharing build cache across CI and laptops.
Have a topic you want us to cover? Email us - we read everything.
Speed up your builds
Create a workspace, drop in a token, and watch your hit rate climb. Free tier - no credit card.