· via dev.to (home feed)
GitHub issues show 48 teams replacing MinIO after community repo archived
A dev.to analysis of public GitHub issues found 48 teams documenting moves away from MinIO since its community repository was archived, with SeaweedFS, Cloudflare R2, RustFS and Garage among the destinations.

What the analysis found
At least 48 teams have documented replacing MinIO in their own GitHub issue trackers since the project's community repository was archived, according to an analysis published on dev.to. Rather than scanning forums or comparison posts, the author searched public issues and discussions, on the theory that real migration decisions leave a record in the repositories where the engineering happens.
The cited cases are concrete rather than evaluative. One issue described MinIO container images no longer downloading, which left new development stacks and k3s hosts unable to start. Another said the open-source edition was no longer maintained and had broken the project's Docker builds. A third swapped MinIO out as a backup target, and one of the larger cases involves a national ID platform that runs on-premises for governments and now has to decide which S3-compatible stores to support.
Where teams are going
The author tallied the alternatives named across those 48 cases, noting that teams could list more than one candidate, so the numbers measure consideration rather than final choice:
- SeaweedFS: 16 mentions
- Cloudflare R2: 13
- RustFS: 11
- Garage: 11
- AWS S3: 10
- Ceph: 4
- Backblaze B2: 3
The spread is as interesting as the ranking. Self-hosted clustered file systems, a hyperscaler, a CDN operator's storage service and several smaller S3-compatible projects all appear, suggesting teams are optimising for different constraints, such as operational overhead, data locality or cost, rather than converging on a single successor.
How far to trust the numbers
This is one author's manual count, not a systematic survey. It also comes with a disclosed commercial angle: the post closes by offering to run the same search for vendors, as promotion for a tool the author is building to automate the technique. The pattern still looks credible, since the cited issues are tied to specific build failures, but 48 should be read as a lower bound, because most teams that swap a storage backend never file a public issue about it.
Decisions made quietly
The author's broader observation concerns how infrastructure choices actually get made. When a dependency breaks, teams seldom ask in public what to buy next. They open an issue in their own repo, sketch a few candidates and settle the matter within days. By the time a migration surfaces anywhere louder, such as a changelog or a blog post, the decision is long since closed.
According to the post, a live evaluation has a recognisable shape: an issue title that pairs a competitor's name with a word like "replace" or "migrate", a build or deployment failing because of that competitor, and a shortlist of alternatives in the body. Almost no vendor, the author argues, is watching for it.
Why it matters
For object storage, 48 documented migrations point to a genuine shift rather than ambient grumbling. Teams building on MinIO's open-source edition are re-platforming now, and demand is spreading across a diverse field of S3-compatible alternatives instead of pooling around one winner. The S3 API's status as a de facto standard is what keeps the switching cost low enough for that to happen at all.
For anyone selling developer tooling, the sharper lesson is about where buying signals live. The decisive moment is not a review site or a social thread but an issue in a public-yet-obscure repository, filed by an engineer whose deployment just failed and who needs a working replacement quickly. A vendor that monitors issue trackers for its own name and its competitors' can catch an evaluation in progress and, in principle, take part in it.
- #object-storage
- #minio
- #open-source
- #migration
- #s3