BuildFetch Cache

What BuildFetch Cache is

BuildFetch Cache is a remote cache platform intended to reduce build times and CI costs by sharing build outputs across engineer workstations, CI and AI agent environments. It lists support for Bazel, Gradle, Maven, Sbt, Buck2, Moon, Buildbarn, Ccache, Sccache, Go, Nx and Turborepo; Bazel can use either gRPC or HTTP remote cache APIs. The service uses NVMe for ephemeral cache storage and SSD for persistent storage. A project dashboard shows throughput, tail latency, request volume and storage use, while scoped project tokens can grant read-only or read-write access. BuildFetch says data is encrypted in transit with TLS and at rest with LUKS AES-256 or similar technologies. It is available through BuildFetch Cloud or as a Custom Cloud or on-premise Kubernetes deployment. Listed regions are US West and EU Central. The free plan has resource caps; paid plans start at $55 a month, and a 45-day trial is listed. Basic and Pro plans allow separately priced storage, traffic and request overages.

Who it suits

It suits teams using supported build systems that want to share cached outputs across developers, CI and AI agents. Organizations can choose a cloud service or a self-hosted deployment, including on-premise Kubernetes.

Limits

The free Open Source plan includes 20GB fast cache storage, 50GB network traffic, 100,000 cache requests, and 45 days of LRU retention; its resource caps cannot be exceeded. Basic includes one project, 50GB fast cache storage, 100GB network traffic, 300,000 requests, and 45 days of retention. Pro provides 75 days of retention and unlimited projects and users.

Getting started

1. Visit the BuildFetch website.
2. Choose BuildFetch Cloud, custom cloud, or on-premise Kubernetes deployment.
3. Select the Open Source plan or a paid plan; the free plan includes a 45-day trial.
4. Configure a supported build system to use the remote cache.
5. Use scoped project tokens to set read-only or read-write access.

Verdict

BuildFetch Cache pairs broad build-system support with shared remote caching, usage metrics and deployment choices. Review the free-tier caps and overage terms, or consider self-hosting if the listed cloud regions do not fit.