Your build cache shouldn't die with its vendor.
FosterStack is a self-hosted remote build cache server — a Develocity Build Cache Node replacement that speaks the same Gradle remote build cache HTTP protocol, so migrating is mostly a URL change. The same server doubles as a Maven build cache through the Apache Maven Build Cache Extension's remote HTTP mode, so a mixed Gradle and Maven shop runs one deploy instead of two. Open source core, one-command deploy, and the thing that actually matters: it stays patched, on a promise.
Join the waitlist
Private beta this October, free. Public launch in November — before the EOL, with a migration guide that gets you off the Build Cache Node in about 30 minutes.
What you get that a bare HTTP endpoint doesn't give you
Yes — Gradle's remote cache protocol is just GET and PUT, and you could point it at any object store. What you'd be rebuilding yourself is everything around that:
Cache management
Eviction policies, size limits, and TTLs that keep a busy CI cache healthy without hand-tending.
Access control
Read/write credentials for CI vs. developers, so laptops consume the cache but never poison it.
Metrics & UI
Hit rates, entry sizes, and top misses — visible, so you know the cache is earning its keep.
Maintenance on an SLA
Dependency CVEs remediated fast — target within 48 hours of disclosure — with a public changelog as proof.
Day-one compatibility
A CI matrix tests every new Gradle and JDK release the day it ships. Upgrades stop being a gamble.
30-minute migration
A guide and config translator for existing Build Cache Node deployments. Same protocol, same CI config shape.
Built to be verified, not trusted
We're a new vendor asking to sit in your build pipeline, so the burden of proof is on us. The answer is to make everything checkable:
- MIT-licensed core. Read the code before you run it.
- One public container image. Free and paid users pull the identical bytes — scan exactly what you deploy.
- A license key unlocks enterprise features (SSO, HA, analytics, priority support). No private registry, no gated downloads.
- Security patches are never withheld from the free tier. Not delayed, not embargoed — never.
- Signed commits, signed releases, public changelog, public compatibility matrix.
Pricing at launch
| Free | Team | Business |
|---|---|---|
| The full cache server, MIT-licensed, self-hosted. Forever free. | $49/month — access control, metrics UI, email support. | $199/month — SSO, HA/replication, analytics, priority support with the CVE-response SLA. |
Self-serve, credit card, cancel anytime. Priced so an engineering manager can expense it without a procurement cycle — the incumbent's median contract runs $57k/year.
Roadmap honesty
Gradle and Maven both run against the same server today (v1 targeted before the EOL); we maintain the cache server, while the Maven client side is Apache's own Build Cache Extension. An npm remote cache for CI — same core, a third protocol — follows. If you need that today, tell us in the waitlist form reply; it moves the roadmap.