After MinIO's Abandonment: The Local-S3 Successors, and the Filesystem-vs-S3-API Fight
rmoff's bake-off post (front-paged at 159 points) opens with the fact that set this migration in motion: "In late 2025 the company behind MinIO decided to abandon it to pursue other commercial interests" — killing the web UI and leaving a decade of demos, CI pipelines, and homelabs stranded on a dead-end dependency. The post evaluates six single-node S3 stand-ins against a fixed bar (Docker image, S3 API compat, OSI license, active backing): S3Proxy, RustFS, SeaweedFS, Zenko CloudServer, Garage, Apache Ozone.
The discussion is effectively a field report on where the refugees actually went:
- RustFS — markab21: "We use RustFS in a production system with no issues. We switched over after MinIO license changes... We have heavy concurrent usage, and we haven't had a single issue yet." Counterpoint from PunchyHamster: "Hit bug after bug after bug in RustFS. Current version seems to work fine for now but it's definitely 'new project'" — though maintainers "react very fast on any bug I submitted."
- Versity GW — the sleeper hit: "switched to versity for homelab, been simple and stable as a rock. Point at a directory per bucket and done" (nodoodles); swills: "it's a shame it's not more well known."
- Ecosystem proof MinIO is really out: pritambaral notes Incus ripped out its bundled MinIO — the PR is literally titled "Replaced because minio is dead".
The philosophical split underneath: sdcfgy: "Just use the damn file system. Why does everyone have to put HTTP between everything?" — met by four separate "Because..." replies, the sharpest from xienze: "Because you might be running something that only talks S3 and want to point it at something local," and Tostino: "Because you want to mock the tools you are going to use in production locally or in CI." Jedd adds the sharpest technical critique of the post itself: "The title is 'for single node local S3' but what they actually mean is 'for minio-compatibility', which is an entirely different question."
Why it matters: MinIO was the default local-S3 for a decade, and its AGPL-to-commercial pivot plus effective abandonment is fragmenting rather than consolidating the successor landscape — RustFS is 6 months old with 19.7k stars, Garage is AGPL, Ozone is a Hadoop-scale beast. Anyone pinning CI or demos to a "MinIO replacement" is now choosing a horse; the S3-compatibility matrix is about to matter again.