Cached content served close to every build
- Develocity Edge nodes run as a container, a JAR, or inside your Kubernetes cluster, next to your CI agents โ so all cached content is served at LAN speed.
- You choose where cached content lives โ from fully managed to self-hosted, where build data never leaves your network. Develocityยฎ coordinates the Edge either way.
- A new Edge node has immediate access to everything already cached โ nearby nodes peer, and content replicates across Edge locations, so every build benefits whichever node it hits.




