SILO: S3-Compatible Object Storage by PigstySkip to content<br>Docs<br>Blog<br>Download & Install<br>简体中文<br>Light / Dark<br>GitHub · 2.0k
OPEN-SOURCE S3-COMPATIBLE OBJECT STORAGE<br>S 3 I nterface<br>L ibre O bject<br>Silo is maintained by the Pigsty Community<br>With supply-chain continuity and security updates<br>Documentation<br>Download & Install<br>What we promise, and what we won't — the Silo Manifesto →
SILO // STORAGE NODE<br>PGSTY-01<br>S3 API:9000 APPLICATION TRAFFIC<br>OBJECT STORAGE CORE<br>SILO<br>S3-COMPATIBLE<br>CONSOLE:9001 OPERATOR ACCESS
ERASURE SET // DISTRIBUTED DISKS<br>D01 ONLINED02 ONLINED03 ONLINED04 ONLINE
COMMUNITY FORKMAINTAINED BY PIGSTY
KEY METRICS<br>Maintained in public, visible at a glance
501,861<br>Docker Pulls<br>1,956<br>GitHub Stars<br>19<br>Security Fixes<br>Releases
Dokploy PRODUCT TEMPLATE
RAGFlow DEFAULT COMPOSE
Grafana Loki HELM · BUNDLED SERVICE
Omnia HPC PLATFORM RUNTIME
nixpkgs DISTRIBUTION PACKAGE
Pigsty PG BACKUP REPO
DaoCloud PUBLIC IMAGE MIRROR
ModelarDB CI · INTEGRATION
Measure BACKEND DEPLOYMENT
AgentsMesh COMPOSE · CI
Firemoot REFERENCE COMPOSE · CI
buun-stack KUBERNETES STACK
Open-Lutra S3 DEV PROFILE
Kukan COMPOSE MIGRATION
Dokploy PRODUCT TEMPLATE
RAGFlow DEFAULT COMPOSE
Grafana Loki HELM · BUNDLED SERVICE
Omnia HPC PLATFORM RUNTIME
nixpkgs DISTRIBUTION PACKAGE
Pigsty PG BACKUP REPO
DaoCloud PUBLIC IMAGE MIRROR
ModelarDB CI · INTEGRATION
Measure BACKEND DEPLOYMENT
AgentsMesh COMPOSE · CI
Firemoot REFERENCE COMPOSE · CI
buun-stack KUBERNETES STACK
Open-Lutra S3 DEV PROFILE
Kukan COMPOSE MIGRATION
VALUE PROPOSITION<br>What upstream dropped, SILO picks up<br>MinIO's community edition gutted its console, stopped shipping binaries, and archived its security updates. SILO restores all three—on the same code, at the same performance.
WEB CONSOLE<br>The full console, restored<br>◇ Manage buckets, identity, monitoring, and replication in the browser<br>Upstream stripped the AGPL web console down to a stub<br>SILO ships the full management UI: buckets, IAM, monitoring, site replication<br>No paywall, no feature gate—the console every operator remembers<br>The console upstream took away, back in your browser
SECURITY PATCHES<br>Patched, not abandoned<br>＋ CVEs get fixed here, advisories next to the code<br>Upstream's community edition is archived—new CVEs land on no one's desk<br>19 security fixes shipped on the active release line, each with an advisory<br>Report privately, triage reproducibly, publish transparently<br>Security that keeps moving
blog/security · 14 ENTRIES2026-08-04Three Headers, One Lie: Making the Client Source Address Mean Something<br>2026-08-04Absent Is Not Empty: A Blank versionid and the Fail-Open It Invites<br>2026-08-04Object Grant, Bucket Reach: When 'bucket/*' Could Rewrite the Bucket Itself<br>2026-08-04The Parser Knew, the Schema Didn't: Config Keys That Could Take Every Notification Down<br>2026-08-03Sorted Is Not Increasing: How One Duplicate Part Number Doubled an Object<br>2026-08-02Internode Path Containment Audit: Paying Off What CVE-2026-42600 Left Owing<br>2026-06-12CVE-2026-42600: ReadMultiple Storage-REST Path Traversal<br>2026-04-16CVE-2026-41145: Unsigned-Trailer Query Authentication Bypass<br>2026-04-16CVE-2026-40344: Snowball Auto-Extract Authentication Bypass<br>2026-04-15CVE-2026-39414: Oversized S3 Select Records and a SIMD Bypass<br>2026-04-15CVE-2026-34204: Replication Metadata Injection<br>2026-04-15CVE-2026-33419: LDAP STS Enumeration and the Throttling Chain<br>2026-04-15CVE-2026-33322: OIDC JWT Algorithm Confusion<br>2026-04-15CVE-2026-32285: The jsonparser Advisory That Required No Patch<br>BROWSE THE SECURITY CHRONICLE →
RELEASE ARTIFACTS<br>Binaries, prebuilt and signed<br>▦ From source to signed, runnable packages<br>No self-build requirement, no detour through a closed commercial download<br>Versioned binaries, RPM / DEB / APK , and multi-arch container images<br>GPG-signed packages with published checksums<br>The delivery surface, maintained
SILO // RELEASE SURFACE VERSIONED · CHECKSUMMED<br>OCI amd64 · arm64<br>RPM EL compatible<br>DEB Debian · Ubuntu<br>APK Alpine Linux<br>BIN server · client<br>SUM SHA256 checksums<br>ACTIVE RELEASE LINE →
COMPATIBILITY<br>A drop-in replacement<br>⇄ Swap the image name; your data stays in place<br>The delivery surface is renamed silo ; the protocol and data are not<br>S3 API, MINIO_* variables , metrics, routes, and disk format unchanged<br>See the compatibility audit and migration guide, rollback included<br>Point the image at pgsty/silo—everything else stays
docker-compose.yml# Migrate from MinIO to Silo<br>services:<br>minio:<br>- image: minio/minio:latest<br>+ image: pgsty/silo:latest<br>environment: # MINIO_* unchanged<br>volumes: # same volume, same data
S3 INTERFACE<br>The interface your stack already speaks<br>Silo renames the product and its delivery surfaces—never the protocol. The S3 API, MINIO_* configuration, and on-disk format stay as your stack expects, with every difference recorded in the compatibility audit.<br>Compatibility Notes →<br>S3 Clients →<br>Environment Variables →<br>Command-Line Client →
S3S3 APIApplication interface<br>$siloServer...