Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

Silo

github.com

  • Free plan
  • Linux
  • Web
  • Self-hosted
7.1 Club score Visit github.com

What Silo is

Silo is a self-hosted HTTP server for remote Gradle build caching. It speaks the Gradle build cache protocol, with GET, PUT, and HEAD support for retrieving, uploading, and checking cached artifacts. The project is intended to replace the end-of-life Gradle Remote Build Cache Node. It currently stores cache data on a filesystem; S3 and GCS support remain roadmap items.

Silo runs on Linux and requires JVM 21 or later. It is distributed as a fat JAR and a multi-architecture Docker image for linux/amd64 and linux/arm64. Cache controls include LRU eviction, TTL, size and entry caps, and reserved free-space thresholds. Authentication options include HTTP Basic and OIDC/Bearer, with read-only and read-write role mapping. Monitoring includes Prometheus metrics, structured JSON logs, health and readiness endpoints, and a live stats stream. There is an admin dashboard at /admin, with a demo that uses simulated data. Silo is open source and free, but is described as alpha and pre-1.0; only the latest v0.x release receives security fixes.

Who it suits

Silo is for teams running Gradle builds that want to host their own remote build cache. It may suit Linux operators comfortable with JVM 21 or later and an alpha-stage project.

Good to know, and what to watch

  • Free and open source under Apache-2.0
  • Provides filesystem-backed Gradle HTTP caching
  • Offers multiple authentication and role options
  • Includes Prometheus metrics and health endpoints
  • Supports cache limits and eviction controls
  • Project is described as alpha and pre-1.0
  • S3 and GCS storage are roadmap items
  • Only the latest v0.x release receives security fixes
  • Requires JVM 21 or later

Silo

Free

Free plan

The verdict

Silo offers self-hosted Gradle caching with useful cache controls and monitoring. Its alpha status and filesystem-only storage may matter for teams evaluating it for production use.

What the maker publishes

Admin dashboard
Silo includes a single-page admin dashboard at /admin, and its live demo runs with simulated data without installation or a backend. source
Authentication
Silo supports HTTP Basic and OIDC/Bearer authentication with read-only and read-write role mapping. source
Cache management
It supports LRU eviction, TTL, byte and entry caps, and reserved free-space thresholds. source
Current status
The project describes itself as alpha and says S3/GCS backends, compression, and replication remain open work. source
Deployment
Silo is distributed as a fat JAR and a multi-architecture Docker image for linux/amd64 and linux/arm64. source
Implementation
Silo is written in Kotlin using Ktor and requires JVM 21 or later. source
Monitoring
Silo provides Prometheus metrics, JSON-structured logs, health and readiness endpoints, and a live stats stream. source
Protocol
It supports the Gradle HTTP build cache protocol methods GET, PUT, and HEAD. source
Purpose
Silo is a self-hosted HTTP server that speaks the Gradle build cache protocol and replaces the end-of-life Gradle Remote Build Cache Node. source
Release integrity
The security policy says release artifacts are cosign-signed, the fat JAR has a SHA-256 checksum, and every release includes a CycloneDX SBOM. source
Security
The project says it has no phone-home telemetry or accounts and supports atomic writes with crash recovery. source
Security support
Silo is pre-1.0, and only the latest v0.x release receives security fixes; the policy promises acknowledgement within 3 business days and initial assessment within 7 business days. source
Storage
Filesystem storage is implemented, while S3 and GCS are listed as roadmap items. source

Checked against the maker's pages on 8 Oct 2026.