Docs Blog Download & Install 简体中文 GitHub · 1.9k

OPEN-SOURCE S3-COMPATIBLE OBJECT STORAGE

S3 Interface Libre Object

Silo is maintained by the Pigsty Community With supply-chain continuity and security updates

SILO // STORAGE NODE PGSTY-01
S3 API:9000APPLICATION TRAFFIC
OBJECT STORAGE CORE SILO S3-COMPATIBLE
CONSOLE:9001OPERATOR ACCESS

ERASURE SET // DISTRIBUTED DISKS

D01ONLINED02ONLINED03ONLINED04ONLINE
COMMUNITY FORKMAINTAINED BY PIGSTY

KEY METRICS

Maintained in public, visible at a glance

VALUE PROPOSITION

What upstream dropped, SILO picks up

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

The full console, restored

Manage buckets, identity, monitoring, and replication in the browser again

  • Upstream stripped the AGPL web console down to a stub
  • SILO ships the full management UI: buckets, IAM, monitoring, site replication
  • No paywall, no feature gate—the console every operator remembers

The console upstream took away, back in your browser

SILO Console monitoring page showing servers, drives, and capacity

SECURITY PATCHES

Patched, not abandoned

CVEs get fixed here, with advisories next to the code

  • Upstream's community edition is archived—new CVEs land on no one's desk
  • 19 security fixes shipped on the active release line, each with an advisory
  • Report privately, triage reproducibly, publish transparently

Security that keeps moving

RELEASE ARTIFACTS

Binaries you can actually download

From source to signed, runnable packages

  • No self-build requirement, no detour through a closed commercial download
  • Versioned binaries, RPM / DEB / APK, and multi-arch container images
  • GPG-signed packages with published checksums

The delivery surface, maintained

PERFORMANCE

No performance tax

The same hot path as upstream—maintenance only

  • SILO tracks upstream's code; the storage and S3 hot paths are unchanged
  • Changes are build, dependency, security, and correctness—not rewrites
  • Erasure coding, parallelism, and throughput match the version you know

A fork you don't pay for in latency

Erasure-coded data and parity blocks

OPERATIONS

Familiar Console, monitoring, and replication workflows

Open Console Docs ↗
MORE FROM THE COMMUNITY · HOVER TO PAUSE · CLICK FOR THE SOURCE
Yingfeng
Founder @ InfiniFlow · RAGFlow

“Using pgsty/minio's fork as the default storage is a reasonable solution right now.”

GitHub · RAGFlow #13840 · 2026-03-31
Mauricio Siu
Creator of Dokploy

“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
Debjeet Biswas
Building measure.sh

“This PR switches to a community trusted minio image.”

GitHub · measure #3831 · 2026-06-06
chalukyaj
Author of Silo Operator

“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
Clayton Auld
Engineer @ GCI

“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
kuma_3838
Qiita Author

“最小限の変更で済むため、直近の対応としては最も手軽です。”

Qiita · 2026-02-25
Grafana Loki
Helm chart · values.yaml

“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
Søren Kejser Jensen
ModelarDB · Aalborg University

“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
Łukasz Różewicz
RAGFlow Community

“A community fork of MinIO … that restores the admin console and ships patched binaries.”

GitHub · RAGFlow #13840 · 2026-03-28
Du
Software Engineer

“The fork keeps the wire protocol, on-disk format, and mc client compatible with upstream.”

GitHub · pgsty/minio #42 · 2026-07-21
ekko
1Panel Community

“原 minio 官方已不再维护,pgsty 开源社区 fork 重新维护的版本是否考虑”

GitHub · 1Panel #12753 · 2026-05-18
buun-stack
Kubernetes Home Lab

“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
Upendra N
GitHub Community

“Thank you for the initiative. Just name it S4 — the next version of S3 😅”

GitHub · pgsty/minio #7 · 2026-03-20
Dokploy Templates
Template documentation

“This template uses pgsty/minio, the actively maintained community fork.”

docs.dokploy.com · 2026-07

MAINTENANCE

A deliberately narrow promise

SILO exists for continuity across existing MinIO-compatible deployments—not an unlimited product roadmap.

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

EXPLICIT BOUNDARY

What is not promised

  • A full continuation of the upstream roadmap
  • Historical releases or multiple support branches
  • Untested, item-by-item compatibility guarantees
  • Response, remediation, or release-time SLAs