When MinIO's community repo was archived, I wanted to know how teams actually react. Not on Reddit or in "best alternatives" blog posts, but in their own work.
So I searched public GitHub issues and discussions. Since the archive, I've found 48 teams writing about replacing MinIO in their own repos.
What they wrote wasn't "looking for a MinIO alternative". It was things like:
- "MinIO images no longer download, so new dev stacks and k3s hosts cannot start"
- "MinIO OSS no longer maintained" (it broke their Docker builds)
- "Replace MinIO as the backup target"
- a national ID platform that runs on-premise for governments, deciding which S3 stores to support next
These are teams with a broken build, a deadline and a decision to make right now.
What they're choosing between
A team can name more than one:
- SeaweedFS: 16
- Cloudflare R2: 13
- RustFS: 11
- Garage: 11
- AWS S3: 10
- Ceph: 4
- Backblaze B2: 3
The lesson, if you sell a dev tool
Your buyers often aren't shopping out loud. When a dependency breaks, they don't post "recommend me X". They open an issue in their own repo, list the options, and decide in a few days. If you're one of those options, that issue is where the decision happens, and almost no vendor is reading it.
Three things to look for:
- An issue title that mentions a competitor and "replace", "remove" or "migrate".
- A build or deploy that fails because of that competitor.
- A short list of alternatives in the body. That's an evaluation in progress.
Free offer
I'm building a tool that runs this search automatically. If you sell a dev tool, comment with your product and the competitor you'd like to win users from. I'll run the same search for the first 10 and reply with what I find, for free.
Top comments (0)