Compatibility
Current Console: v2.4.1, with mcli 20260916 and pkg v3.14.1. See the component matrix and password-policy migration.
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, the mcli client notes, and the console notes. The Feature Notes subsection covers the opposite direction: design records for capabilities Silo adds beyond upstream.
Component Versions
Published SILO releases, source fixes verified on September 16, and coordinated upgrade requirements.
Password Permissions
Version boundaries and migration for the ChangeMyPassword and CreateUser policy split.
Access-Tiering Removal
Why the opt-in GET-frequency pool-tiering feature was removed, how to migrate builds that contained it, and what the upgrade acceptance did and did not prove.
Migrate from MinIO to Silo
What changes, what stays, and how to switch a container deployment. Package installations are covered in Native Package Migration.
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
Compatibility, behavior changes, installation, and the current pgsty/mc release
Native Package Migration
How the silo RPM/DEB packages differ from the minio packages: file layout, service account, takeover semantics, and caveats.
Console Compatibility Notes
Differences between SILO Console and the upstream MinIO Console
Feature Notes
Design notes for capabilities Silo adds beyond upstream MinIO — written down before they ship.