FosterStack

Overview

FosterStack is an open-source, self-hosted remote build cache for teams using Gradle or Maven. It is best suited to teams seeking a replacement for the discontinued standalone Develocity Build Cache Node and willing to operate an early-stage service themselves.

Its useful controls and no-cost core are balanced by v0.1 maturity, incomplete Maven acceptance coverage and paid tiers that are not yet available.

Key features

FosterStack supports Gradle and implements Maven’s remote HTTP cache mode, though Maven acceptance coverage remains in progress. That makes Gradle the more established fit for teams evaluating build-tool compatibility; Maven users should account for the unfinished acceptance work.

A size cap and least-recently-used eviction keep the cache within a chosen limit by removing older entries when new ones arrive. HTTP Basic Auth over TLS, constant-time credential comparison and no credential logging provide a focused access-control baseline. Prometheus metrics and a read-only status page show hit rates and cache size against its cap, giving operators visibility into cache use.

Teams can deploy a Docker image or static binary. Signed releases and SLSA provenance add artifact-verification evidence, while the MIT-licensed core receives security patches in the free tier. The maker says that core makes no outbound connections and collects no telemetry or usage data. FosterStack is not FedRAMP or CMMC compliant; its published evidence and validated crypto are intended to support a customer’s own compliance program, not replace compliance.

The product is v0.1, and nobody outside the maker’s own work is yet running it in a production build pipeline. That is a material adoption risk for teams that need an established production track record. Windows is not built or planned.

Pricing

The pricing model is freemium, with a free self-hosted core and paid plans described at $49/mo and above. The paid tiers are not yet available, so their features and support should not be treated as purchasable today.

The free plan supplies the full self-hosted cache and security patches, but lacks the multi-user controls, SSO, analytics and support commitments described for paid plans. Team is aimed at groups that need those capabilities; Business adds resilience and priority support; Compliance adds documentation, questionnaire assistance and LTS. Since none of the paid tiers is available yet, teams needing those services now should look elsewhere. GitHub issues are the route for bug reports and questions in the meantime.

Platforms

FosterStack runs on Linux and macOS, with release binaries for amd64 and arm64 on both. It is self-hosted and can run as a Docker image or static binary. Windows is not supported or planned, so Windows-reliant teams should choose a different option.

Who it's for

FosterStack is a plausible fit for Gradle teams, and for Maven teams prepared to account for acceptance coverage still in progress, that want a self-hosted cache with open-source licensing, size controls and operator-facing metrics. It is less suitable for teams that require a proven production deployment, Windows builds, remote execution, or available paid support and access-control tiers. Remote execution is not part of the product.

Pros and cons

Pros

• Full cache server at no cost: the free plan includes the self-hosted server, MIT license and security patches.
• Operational visibility and limits: Prometheus metrics, a read-only status page and size-capped LRU eviction help teams monitor and bound cache use.
• Verifiable release practices: signed artifacts and SLSA provenance support release verification.
• Privacy-oriented core: the maker says the free core makes no outbound connections and collects no telemetry or usage data.

Cons

• Very early maturity: it is v0.1, with no external production build-pipeline users reported by the maker.
• Maven coverage is unfinished: acceptance work is still in progress, making it a less settled choice for Maven users.
• Paid capabilities are not available: multi-user access, OIDC SSO, analytics, HA/replication and the described support commitments cannot yet be bought.
• No Windows support or remote execution: both are exclusions for teams that require those capabilities.

Alternatives

Build Cache Software is the broader category directory for comparing cache options.

• Bitrise is worth considering when a team wants a freemium build platform with a one-person Hobby plan and a small-project allowance of build credits a few times per month, rather than FosterStack’s self-hosted cache server.
• Ccache is a free option for Linux, macOS, Windows and self-hosted environments when single-file compilation caching is the need; some compiler flags fall back to the compiler.
• EngFlow Remote Caching fits teams that want a free in-cluster option limited to one machine, 32 CPU cores and Linux, or an enterprise plan with custom pricing.
• cachepot is a free Apache-2.0 option for teams looking for open-source cache software across Linux, macOS, Windows and self-hosted environments.
• MozJPEG is a free open-source JPEG encoder library with a demo cjpeg tool, not a substitute when the need is a Gradle or Maven remote build cache.
• NativeLink is a free self-hosted alternative when distributed scheduling, remote caching across all build systems, major cloud providers and community Slack support are priorities.
• bazel-remote is a free, Apache-2.0 self-hosted cache with configurable cache size for teams whose needs align with that option.
• BuildFetch Cache offers a free tier with 20GB fast cache storage, 50GB network traffic, 100,000 cache requests and 45 days of LRU retention; consider it when those published quotas suit the workload.

Verdict

Choose FosterStack if your Gradle or Maven team wants an MIT-licensed, self-hosted remote cache and can accept v0.1 maturity, with Maven users especially mindful of incomplete acceptance coverage. Its free core combines cache controls, authentication and monitoring without telemetry, but teams needing production-proven software or paid access controls and support today should look elsewhere.