MAINTAINED SURFACE
What stays maintained
- Builds and dependencies for the active release line
- Applicable security fixes and advisories
- Focused fixes for reproducible defects
- Versioned artifacts and documentation
OPEN-SOURCE S3-COMPATIBLE OBJECT STORAGE
Silo is maintained by the Pigsty Community With supply-chain continuity and security updates
ERASURE SET // DISTRIBUTED DISKS
KEY METRICS
DokployPRODUCT TEMPLATE
RAGFlowDEFAULT COMPOSE
Grafana LokiHELM · BUNDLED SERVICE
OmniaHPC PLATFORM RUNTIME
nixpkgsDISTRIBUTION PACKAGE
DaoCloudPUBLIC IMAGE MIRROR
ModelarDBCI · INTEGRATION
MeasureBACKEND DEPLOYMENT
AgentsMeshCOMPOSE · CI
FiremootREFERENCE COMPOSE · CI
buun-stackKUBERNETES STACK
Open-LutraS3 DEV PROFILE
KukanCOMPOSE MIGRATIONVALUE PROPOSITION
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
Manage buckets, identity, monitoring, and replication in the browser
The console upstream took away, back in your browser
SECURITY PATCHES
CVEs get fixed here, advisories next to the code
Security that keeps moving
RELEASE ARTIFACTS
From source to signed, runnable packages
The delivery surface, maintained
COMPATIBILITY
Swap the image name; your data stays in place
Point the image at pgsty/silo—everything else stays
S3 INTERFACE
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.
USER VOICES
Public third-party records from February–July 2026. They describe individual environments, not universal compatibility or production guarantees.
“Using pgsty/minio's fork as the default storage is a reasonable solution right now.”
GitHub · RAGFlow #13840 · 2026-03-31“Drop-in replacement: same env vars, same server command, same /data on-disk format, and it restores the full web console upstream had gutted.”
GitHub · Dokploy templates #1012 · 2026-07-15“This PR switches to a community trusted minio image.”
GitHub · measure #3831 · 2026-06-06“To discover that the community maintained version not only exists, but has had a recent release which outperforms the last published minio image was a delight.”
GitHub · pgsty/minio #30 · 2026-04-19“Looks like a community fork of MinIO may be the real solution here … this is likely the easiest migration path.”
GitHub · Notesnook #79 · 2026-02-24“Override the upstream MinIO, Inc. images with the Pigsty (pgsty) community fork to mitigate the unresolved CVE in the abandoned MinIO images.”
GitHub · grafana/loki“Switching from minio/minio to pgsty/minio as neither RustFS and VersityGW seems suitable for a production deployment.”
GitHub · ModelarDB-RS #400 · 2026-06-22“A community fork of MinIO … that restores the admin console and ships patched binaries.”
GitHub · RAGFlow #13840 · 2026-03-28“The fork keeps the wire protocol, on-disk format, and mc client compatible with upstream.”
GitHub · pgsty/minio #42 · 2026-07-21“原 minio 官方已不再维护,pgsty 开源社区 fork 重新维护的版本是否考虑”
GitHub · 1Panel #12753 · 2026-05-18“Uses the pgsty/minio image, since MinIO's upstream Community Edition is archived/EOL; the embedded admin console is restored.”
GitHub · buun-ch/buun-stack · 2026-06-21“Thank you for the initiative. Just name it S4 — the next version of S3 😅”
GitHub · pgsty/minio #7 · 2026-03-20“This template uses pgsty/minio, the actively maintained community fork.”
docs.dokploy.com · 2026-07MAINTENANCE
SILO exists for continuity across existing MinIO-compatible deployments—not an unlimited product roadmap.
MAINTAINED SURFACE
EXPLICIT BOUNDARY
DOWNLOAD
Choose the server or admin client first, then use the install path that matches your operating system, architecture, and deployment model.
DATA SERVICE
Server binaries, container images, Linux packages, source, and Pigsty Ansible automation.
ADMIN CLI
A compatible command-line client for buckets, objects, identity, cluster administration, and daily operations.