Nx Cloud's distributed task execution and remote caching transforms monorepo CI from a bottleneck into a competitive advantage — reducing CI times from 30–60 minutes to 5–15 minutes by caching task outputs across machines and distributing test execution in parallel. For engineering organisations with growing monorepos where CI time is becoming a developer friction point, Nx Cloud provides the highest-ROI infrastructure investment available. This guide covers the setup, the cost model, and the configuration patterns that maximise performance.
What Nx Cloud Provides
Setup and Configuration
In your Nx workspace: npx nx connect. This adds an nxCloudId to nx.json and sets up the remote cache connection. Create an account at cloud.nx.app — the first organisation is free (up to 500 hours compute saved/month). Commit the updated nx.json. From this point, any developer or CI run that executes Nx tasks will: check the remote cache first, use cached results if available, upload new results to the cache for others to benefit from. First-time setup: 5 minutes. Immediate benefit: cache hit rates of 60–80% on typical monorepos within a week of the team using it.
For DTE in CI: update your CI config to use multiple agents. GitHub Actions example: define a main workflow that runs npx nx-cloud start-ci-run --distribute-on="3 linux-medium-js", then N agent jobs that run npx nx-cloud start-agent. The main workflow coordinates; agents pick up and execute tasks in parallel. Nx Cloud handles task ordering (ensuring build runs before test) across agents automatically. Configure in .nx/workflows/agents.yaml for Nx's first-party CI integration. With 3–5 agents: CI time typically drops 60–70% vs serial execution on a single machine.
Monitor cache hit rate in the Nx Cloud dashboard (cloud.nx.app → workspace → CI analytics). Target: >70% cache hit rate for stable CI. Improve hit rate: add inputs configuration to nx.json to precisely define what files affect each task (avoid broad glob patterns that invalidate cache unnecessarily). Example: for a build task, inputs should include source files and tsconfig but exclude test files. Each cache input tweak improves hit rate. Low hit rate (<50%): check whether inputs configuration is too broad, or whether a shared dependency is changing frequently and invalidating downstream caches.
Our DevOps and software development teams configure Nx Cloud for enterprise monorepos — remote cache setup, DTE configuration, and cache hit rate optimisation. Book a free advisory session.