Migrate from MinIO to Silo
What changes, what stays, and how to switch a container deployment. Package installations are covered in Native Package Migration.
Compatibility
Where Silo matches MinIO and where it deliberately differs — server, client, and console.
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 (scope and Docker), native package migration (RPM/DEB), the server compatibility audit, and the mcli client notes. The Feature Notes subsection covers the opposite direction: design records for capabilities Silo adds beyond upstream.
Silo vs. MinIO Server Compatibility
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
Differences between the pgsty/mc and upstream minio/mc
Native Package Migration
How the silo RPM/DEB packages differ from the minio packages: file layout, service account, takeover semantics, and caveats.
Feature Notes
Design notes for capabilities Silo adds beyond upstream MinIO — written down before they ship.