SILO is a MinIO fork maintained by the Pigsty community. It is not affiliated with, endorsed by, or sponsored by MinIO, Inc. “MinIO” is a trademark of MinIO, Inc., used here only to identify the upstream project. See Attribution for source and licensing details.
SILO gives existing MinIO deployments an open release and security-maintenance path while preserving the S3 API, configuration, and operational contracts that make migration practical. This site covers installation, migration, administration, development, releases, and compatibility boundaries.
The commands below pin the current SILO server release. Example credentials are suitable only for a local evaluation.
Exit code 0 means the local server is ready. The probe is built into every SILO binary and does not require a second client inside the container.
Visit http://127.0.0.1:9001 and sign in with the credentials supplied above. Before production use, enable TLS, choose unique credentials, pin a tested image tag or digest, and test backup restoration.
See the container deployment guide for persistent host paths, service management, and production considerations.
Use Download & Install to select the RPM, DEB, APK, or standalone archive for your architecture. Published release assets include SHA-256 checksums and build-provenance attestations.
Native packages install the server as /usr/bin/silo; the service keeps the established MINIO_* environment-variable contract. Review the binary and package compatibility notes before replacing an existing minio package.
Read the migration guide before changing images or binaries. Preserve the data volumes and configuration, stop every node running the old binary, and then start every node on the same pinned SILO release. Do not perform a mixed-binary rolling migration, and never use docker compose down -v on data you intend to keep.
The archived MinIO Operator v7.1.1 can run a SILO Tenant when its image is overridden to pgsty/silo with a tested tag or digest. Follow the Tenant Helm guide and treat that Operator version as a frozen compatibility baseline, not an actively maintained dependency.