# Compatibility

> Where Silo matches MinIO and where it deliberately differs — server, client, and console.

---

LLMS index: [llms.txt](/llms.txt)

---

Silo is a community fork of MinIO. This section records what Silo keeps from MinIO, where it deliberately differs, and what either means when moving between them.

Contents, in reading order: the [migration guide](/compatibility/migration/) (scope and Docker), [native package migration](/compatibility/binary/) (RPM/DEB), the [server compatibility audit](/compatibility/server/), and the [mcli client notes](/compatibility/mcli/). The [Feature Notes](/compatibility/feature/) subsection covers the opposite direction: design records for capabilities Silo adds beyond upstream.

---

Section pages:

- [Migrate from MinIO to Silo](/compatibility/migration/): What changes, what stays, and how to switch a container deployment. Package installations are covered in Native Package Migration.
- [Silo vs. MinIO Server Compatibility](/compatibility/server/): A code-verified compatibility audit of the Silo server fork: binaries, configuration, S3 and admin behavior, storage internals, packaging, containers, and Helm.
- [MCLI Client Compatibility Notes](/compatibility/mcli/): Differences between the pgsty/mc and upstream minio/mc
- [Native Package Migration](/compatibility/binary/): How the silo RPM/DEB packages differ from the minio packages: file layout, service account, takeover semantics, and caveats.
- [Feature Notes](/compatibility/feature/): Design notes for capabilities Silo adds beyond upstream MinIO — written down before they ship.