OPEN-SOURCE S3/MINIO-COMPATIBLE OBJECT STORAGE
PGSTY SILO is a MinIO fork maintained by PGSTY Provides packages, container images, Console, and CVE fixes.
ERASURE SET // DISTRIBUTED DISKS
KEY METRICS
Every number here comes from a public source. Check yourself.
VALUE PROPOSITION
MinIO's OSS edition gutted its console, stopped shipping binaries, and archived its security updates. Silo restores all these — on the same codebase, with CI/CD pipelines, packages, and security maintenance.
ADMIN CONSOLE
Manage buckets, identity, monitoring, and replication in the browser
The console upstream took away, back in your browser
SECURITY PATCHES
Advisories published next to the code that fixes them
Security that keeps moving
RELEASE ARTIFACTS
Packages you can install without building anything
Download it and run it
COMPATIBILITY
Keep data volumes; check version-specific requirements
SILO stack supported; upstream compatibility is best effort
S3 INTERFACE
Same S3 APIs, MINIO_* settings and metric names. Check release notes before upgrading.
OPERATIONS
We restored the full administration console, added a ten-language UI with Arabic RTL, and redesigned the visuals.
THIRD-PARTY REPORTS
Public posts from January to November 2026, quoted verbatim.
“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“The argument for pgsty is that it is as close to minio as possible.”
GitHub · ClickHouse #120474 · 2026-10-08“Branches can use silo instead: https://github.com/pgsty/silo/. This is a plain fork for continuity.”
GitHub · scylladb #31495 · 2026-10-05“We started using https://hub.docker.com/r/pgsty/silo in Velox. Any reason not to use that for simplicity?”
GitHub · prestodb/presto #28551 · 2026-10-20“Hi, thanks for maintaining Silo and keeping the MinIO community codebase alive.”
GitHub · pgsty/silo #224 · 2026-10-30“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“Ruohang Feng has forked MinIO to pgsty/minio and is promising to maintain a stable, CVE-patched, distribution.”
Blog · rmoff.net · 2026-01-14“I use it in end to end tests as an S3 simulator that starts and stops instantly and reads & writes to a local directory, - as you'd expect it's great in that role. No complaints.”
Hacker News · #49710683 · 2026-09-21“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“Silo is a MinIO fork that keeps the S3 API, the MINIO_* configuration names, the health endpoints and the on-disk format, so the swap is confined to the binary path and the image reference.”
GitHub · grafana/loki #25393 · 2026-10-20“This has end-to-end value: the old quay.io image is unavailable, so the existing S3 integration suites cannot start; the new image keeps the server /data command, root-credential environment variables, port 9000, readiness path, and S3/STS behavior those fixtures require.”
GitHub · apache/paimon #10167 · 2026-10-16“One line in MinIOContainer.java — image name only. All ports, env vars, startup commands, class names, and test configuration are unchanged.”
GitHub · prestodb/presto #28551 · 2026-10-21“It keeps the S3 API, MINIO_* env vars, /minio/health/ready route and server /data command unchanged, so it is a drop-in image swap.”
GitHub · apache/pekko-connectors #1943 · 2026-10-20“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-07“silo continues that code base, keeps the MINIO_* deployment variables and /minio/* routes the suites and the proxy use, and publishes signed images, so the backend becomes a digest-pinned silo image and nothing else in the suites has to change.”
GitHub · s3s-project/s3s #969 · 2026-10-18“Silo keeps the S3 API, the MINIO_* variables, the server /data --console-address command, the /minio/health/live route, the bundled mc client (so mc ready local healthchecks keep working) and the on-disk format unchanged, so an existing data volume is reused as is.”
GitHub · FiligranHQ/xtm-docker #43 · 2026-10-21“I've created a FreeBSD ports overlay containing the Silo, Silo Client, and Silo Console.”
GitHub · pgsty/silo #219 · 2026-10-17“Switch to mcli from pgsty/mc (https://github.com/pgsty/mc), the Silo-maintained fork of the MinIO client. It is fully compatible with mc and works with both minio and silo S3 endpoints.”
GitHub · RamenDR/ramen #2893 · 2026-10-19“We’ve switched the quickstart and Compose setups to Silo in #13074; existing MinIO installations are unchanged.”
GitHub · ente/ente #12850 · 2026-10-22“Silo won as the only option that needs no code, config or data migration. It is the MinIO codebase: same S3 API, env vars, ports, console and health endpoints.”
GitHub · alexanderwanyoike/the0 #349 · 2026-10-20“Silo keeps the fully open-source (AGPLv3) MinIO alive with continued maintenance, binary releases, and security backports. This is essentially a drop-in replacement for anyone who needs the full-featured open-source MinIO.”
GitHub · NixOS/nixpkgs #525650 · 2026-08-29“公式アーカイブ時点のコードベースをベースに、RPM/DEB/Docker イメージの配布パイプラインを再構築、削除されていた Admin Console (Web GUI) を復活…「公式が止めた供給網を埋める」ことを目的とした、保守的なフォーク”
DevelopersIO · Classmethod · 2026-10-16“Silo 是 Pigsty 社区在 MinIO 官方停止维护后的社区分支，提供高性能、S3 兼容的对象存储服务，可视为原 minio 应用（已在 #9858 移除）的替代。”
GitHub · 1Panel-dev/appstore #9955 · 2026-10-20“To ensure continued support, security updates, and maintainability for our storage layer, this Pull Request migrates the project from MinIO to the actively maintained open-source fork pgsty/silo (including the pgsty/mc client).”
GitHub · Lair-ai/lair #25 · 2026-10-22“Changed only the image of minio and minio-createbucket to docker.io/pgsty/silo:RELEASE.2026-10-18T00-00-00Z, on the same minio-data volume: the mc ready local healthcheck and the bucket-creation entrypoint work unchanged… files written before the swap are still readable.”
GitHub · supabase #51927 · 2026-10-26“For OSCAR this means that the change is limited to the container image. Edit the MinIO deployment and change the image name to pgsty/silo:RELEASE.2026-09-16T00-00-00Z, keeping the same root credentials and the same persistent volumes, which are reused in place.”
Docs · docs.oscar.grycap.net · 2026-10“The S3 API, the MINIO_* settings and the on-disk format are unchanged; Pigsty adds security fixes and keeps the full web console.”
Unraid Community Apps · 2026-10-21“Minio was abandoned and the download failed with a 410 Gone error. silo is a community fork https://github.com/pgsty/silo”
GitHub · crate/crate #20183 · 2026-10-08“可用的兼容替代是 pgsty/silo。它是 Pigsty 社区维护的 MinIO 分支，保留 S3 API、MINIO_* 环境变量、server /data --console-address :9001 命令行契约和磁盘格式。”
GitHub · pdl-openair/OpenAIR #3 · 2026-10-2481 community contributors · View full record
Issues, pull requests, and security reports all count. · 2026-11-12
MAINTENANCE
SILO exists to keep existing MinIO deployments running, nothing broader.
MAINTAINED SURFACE
OUT OF SCOPE
FAQ
Short answers. The details are behind the links.
Upstream wound down its community edition: the web console was cut back to a stub, prebuilt binaries stopped, and the server repository was archived. Pigsty runs its own PostgreSQL backups on this code, so it needed a maintainer either way. Everything else follows from that. The reasoning is written out in the PGSTY SILO Manifesto.
It keeps existing MinIO-compatible deployments running: versioned binaries and packages you can download, security fixes with public advisories, and the full web console. No build step and no commercial license. This is maintenance work, not a new product.
A short list, kept short on purpose. AGPLv3 with no CLA: contributions come in under DCO sign-off, so copyright stays with each author. No paywalls, no registration walls, no telemetry. A release every one to two months, at most a quarter apart. A public advisory for every security fix we ship. The Manifesto also lists what we refuse to promise, such as fix-time SLAs.
One person, named. The fork is maintained under the PGSTY organization by Ruohang Feng (Vonng), who wrote the Pigsty PostgreSQL distribution. He has deployed and run a 25 PB MinIO cluster, and does the packaging and releases here. Article 9 of the Manifesto says in advance what happens if that arrangement ends.
Most of the code, and most of the first-pass review, is written by coding agents. A human reads every diff, decides the trade-offs, and merges; nothing lands without CI and that review. We keep the agents' working notes and trade-off write-ups, because when a fix turns out to be wrong, the reasoning behind it is the thing you want. The security advisories and release notes are what this arrangement produces in public. Judge it on those.
The .minio.sys and object-layout identifiers are retained; migration does not require renaming data. Metadata behavior, replication format gates and rollback limits are recorded per version. Check component versions and compatibility notes before upgrading. Upstream interoperability is best effort, not a guarantee that arbitrary versions can be mixed.
Common deployments can retain their S3 clients, MINIO_* configuration names, minio_* metric names and existing data directories. Check the source and target SILO versions against the compatibility notes, validate permission, configuration and metadata changes in a test environment, then follow the migration guide to switch images or packages and rehearse rollback. Retained interface names do not guarantee a direct replacement for every upstream version.
SILO provides versioned artifacts and Pigsty deployment integration, with public third-party adoption records on this page. Review current release and security status, pin a version, validate your workload and rehearse rollback. A repository merge, public release and deployment to a particular production environment are separate events.
Silo carries AGPLv3, the same license as the upstream it forked. Our position (a position, not legal advice) is that using Silo through its S3 API does not make your application a derivative work, and we will not use the license as a threat or a sales instrument. We also could not relicense it if we wanted to: there is no CLA, contributions come in under DCO, and copyright stays spread across everyone who wrote a line. Article 3 of the Manifesto has the full statement.
Released artifacts and documentation are meant to stay up, and we will keep them up as long as we can. The build is documented and provenance-attested, so anyone can rebuild equivalent artifacts from source without us. That part does not depend on us being around. If active maintenance stops for six months, we will say so publicly and archive the project rather than let it go quiet. Article 9 of the Manifesto has the exit plan.
DOWNLOAD
Select a component, then choose your platform and installation method.
DATA SERVICE
Server binaries, container images, Linux packages, source, and Pigsty Ansible automation.
ADMIN CLI
The mc-compatible command-line client for buckets, objects, identity, and cluster administration.