About Silo on SILO

License

Mon, 01 Jan 0001 00:00:00 +0000

Silo carries two separate licenses. The software and the documentation are distributed under different terms, and each inherits the license its upstream work already used.

What	License	Where
`silo` server	GNU AGPLv3	`pgsty/minio`
`mcli` client	GNU AGPLv3	`pgsty/mc`
This documentation	CC BY 4.0	`pgsty/silo-docs`

Software: AGPLv3

Silo is a fork of MinIO, which has been distributed under the GNU Affero General Public License v3.0 since 2021. That license is irrevocable for code already released under it — the legal basis on which this fork exists. Silo keeps the same license: no relicensing, no added restrictions, no open-core carve-outs.

Trademark Notice

Mon, 01 Jan 0001 00:00:00 +0000

Warning

Every appearance of the MinIO name in this documentation is descriptive use, and implies no commercial relationship.

Silo is a fork maintained independently by the PIGSTY community. It is not affiliated with, endorsed by, or sponsored by MinIO, Inc.

What the project does to avoid confusion

The fork is published under its own name, Silo, not under MinIO’s.
Every page of this site carries a trademark disclaimer in the footer.
It is labeled a community fork across every distribution channel — repositories, container images, release artifacts, and this documentation.
No claim of affiliation, endorsement, certification, or commercial relationship with MinIO, Inc. is ever made.

Why the name still appears in this documentation

A license grants rights in copyright; it says nothing about names. AGPLv3 gives anyone the right to fork and redistribute the MinIO codebase, but trademark law is a separate matter that a license does not settle.

Attribution

Mon, 01 Jan 0001 00:00:00 +0000

Copyright

Both layers apply at once. A translated or modified page carries MinIO’s copyright in the underlying expression and the Silo project’s copyright in the translation and the changes; neither replaces the other.

Security Policy

Mon, 01 Jan 0001 00:00:00 +0000

Security maintenance is the reason this fork exists. Upstream minio/minio is archived; Silo tracks CVEs against the codebase, backports or writes the fixes, and publishes what it found.

Reporting a vulnerability

Report undisclosed high-severity vulnerabilities through a private channel, not in a public issue.

Silo server and mcli client — preferably as a private report through GitHub Security Advisories on pgsty/minio.
This documentation — open an issue on pgsty/silo-docs; if the content itself discloses a weakness, use a private channel instead.

Include the affected release, a description of the impact, and reproduction steps if you have them — this helps us confirm the issue faster.