Avrea Cache

Avrea Cache eliminates the network round-trips that slow down GitHub Actions workflows. Your builds hit caches colocated with your runners instead of fetching from remote storage.

Three caching layers work together, each targeting a different part of the pipeline:

GitHub Actions Cache

Drop-in replacement for GitHub's built-in cache. Works with actions/cache@v4+ and language setup actions. No workflow changes. Learn more →

Build Cache

Remote caching for build tools. Shares compilation artifacts across jobs and branches so rebuilds only recompile what changed. Learn more →

Package Cache

Pull-through proxy for package registries. Caches downloaded packages locally so npm install, pip install, and go mod download resolve instantly on repeat runs. Learn more →

How it works

All three caches run on the same infrastructure as your Avrea runners. When a workflow runs:

1. GitHub Actions cache requests route to a local proxy instead of GitHub's remote storage.
2. Build tools (Go, Bazel, Gradle, etc.) are pre-configured to use a colocated remote cache.
3. Package managers (npm, pip, Cargo, etc.) resolve through a local pull-through proxy.

No self-hosted infrastructure to manage. No S3 buckets to configure. Avrea handles storage, eviction, and lifecycle.

What's automatic

On Avrea runners, most caching is pre-configured:

Layer	Configuration	What you do
GitHub Actions	Fully automatic	Use actions/cache@v4+ as normal
Build cache	Environment variables and config files injected	Some tools need minor workflow additions
Package cache	Registry URLs pre-configured	Package managers resolve through cache automatically

See the individual integration pages for tool-specific details.

Storage and limits

• Default quota: 25 GB per repository (across all cache types)
• Eviction: Least-recently-used entries are evicted when quota is exceeded
• Retention: Unused entries expire after 7 days

See Storage & Eviction for details.