Services
Four caches for everything a build downloads
Packages, container images, build outputs and CI caches. Each service works on its own; together they share one workspace, one set of tokens, one region and one bill.
CP-01Service
Package ProxyA read-through cache for 18 package registries behind one workspace URL.Learn more →
CP-02Service
Container MirrorA pull-through cache for Docker Hub, GHCR, Quay and other OCI registries.Learn more →
CP-03Service
Build CacheA remote cache for Gradle, Bazel, Turborepo, Nx, sccache and ccache.Learn more →
CP-04Service
CI CacheFast storage for actions/cache-style steps and GitLab runner caches, restored from your region.Learn more →
Which one do I need
What each service caches
| Service | Caches | Used by |
|---|---|---|
| Package Proxy | Packages from 18 registries | npm, pip, Maven, Go, Cargo, apt and other clients |
| Container Mirror | Images and OCI artifacts | Docker, containerd, Kubernetes, Helm |
| Build Cache | Task and compile outputs | Gradle, Bazel, Turborepo, Nx, sccache, ccache |
| CI Cache | Saved folders between jobs | GitHub Actions, GitLab Runner, any CI through the CLI |
Start on the free plan
20 GB of cache, every registry, unlimited users. Upgrade when your pipelines outgrow it.