CP-03 · Service
One remote build cache for every build tool
Build tools can skip work they have done before, if they can find the result. Build Cache gives Gradle, Bazel, Turborepo, Nx, sccache and ccache a shared remote store next to your runners.
- Tools
- Gradle, Bazel, Turborepo, Nx, sccache, ccache
- Endpoint
- https://acme.cacheport.cc/<tool>/
- Protocols
- HTTP cache, Bazel HTTP and gRPC, WebDAV
- Eviction
- Least recently used, per project
- Write access
- Separate tokens for CI and laptops
- Reports
- Hit rate and saved time per project
What you get
Everything in Build Cache
Native protocols
Each tool talks to Build Cache with its own built-in remote cache support. No plugins, no wrappers.
Read-only laptops
Give developers read tokens and CI write tokens, so the cache only holds outputs from clean builds.
Per-project quotas
Split your plan's build cache storage between projects so one busy monorepo cannot evict everyone else.
Hit-rate reports
See hits, misses and bytes served per project and per tool, and which tasks miss most.
Regional storage
Entries are stored in your workspace region, a few milliseconds from runners in the same cloud region.
Same tokens as packages
One workspace, one set of tokens and one audit log for packages, images and build outputs.
Start
Up and running in three steps
Turborepo
Turborepo reads its remote cache settings from three environment variables.
terminal export TURBO_API=https://acme.cacheport.cc/turbo export TURBO_TEAM=acme export TURBO_TOKEN=$CACHEPORT_TOKEN turbo run buildBazel
Point Bazel at the HTTP cache in .bazelrc and pass the token as a header.
config build --remote_cache=https://acme.cacheport.cc/bazel build --remote_upload_local_results=false # CI adds: --remote_header=Authorization=Bearer <token>sccache
sccache uses the WebDAV backend for remote storage.
ci log export SCCACHE_WEBDAV_ENDPOINT=https://acme.cacheport.cc/sccache export SCCACHE_WEBDAV_TOKEN=$CACHEPORT_TOKEN export RUSTC_WRAPPER=sccache cargo build --release
| Supported tools | Gradle (HTTP build cache), Bazel (HTTP and gRPC remote cache), Turborepo (remote cache API), Nx (self-hosted remote cache), sccache (WebDAV), ccache (HTTP storage) |
|---|---|
| Regions | Frankfurt (fra1), Ashburn (iad1), San Jose (sjc1), Singapore (sin1), Sydney (syd1) |
| Largest entry | 2 GB |
| Eviction | Least recently used once the project quota is full |
| Authentication | Bearer tokens with read or read-write scope, OIDC from GitHub Actions and GitLab CI |
Ecosystems
Setup guides by package manager
Common uses
Where it pays off first
Monorepos
Turborepo and Nx skip unchanged packages entirely, on every runner, not only the one that built them last.
Rust and C++
sccache and ccache share compiled objects, so a fresh runner does not recompile every dependency.
JVM services
The Gradle build cache reuses compile and test outputs across branches with identical inputs.
FAQ
Questions
Is it safe to share outputs between branches?
Yes. Entries are keyed by a hash of every input, so a task only reuses outputs from builds with identical inputs.
Can developers push from laptops?
They can, but we recommend read-only tokens for laptops so the cache only contains outputs from CI.
Does it work with Nx Cloud features?
Build Cache stores task outputs. Distributed task execution and other Nx Cloud features are not part of it.
How do I see if it helps?
The workspace dashboard shows hit rate, bytes served and estimated time saved per project.
Works with the rest of Cacheport
Same workspace, same tokens
Start on the free plan
20 GB of cache, every registry, unlimited users. Upgrade when your pipelines outgrow it.