<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Gligorco Gligorov</title>
    <description>The latest articles on DEV Community by Gligorco Gligorov (@gligorcogligorov).</description>
    <link>https://dev.to/gligorcogligorov</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4196406%2Fe8c75855-f148-44a6-bdf2-2932ffbda1c4.jpeg</url>
      <title>DEV Community: Gligorco Gligorov</title>
      <link>https://dev.to/gligorcogligorov</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/gligorcogligorov"/>
    <language>en</language>
    <item>
      <title>48 teams publicly replaced MinIO. They didn’t announce it on forums. They filed issues.</title>
      <dc:creator>Gligorco Gligorov</dc:creator>
      <pubDate>Wed, 18 Nov 2026 16:03:27 +0000</pubDate>
      <link>https://dev.to/gligorcogligorov/48-teams-publicly-replaced-minio-they-didnt-announce-it-on-forums-they-filed-issues-4ajg</link>
      <guid>https://dev.to/gligorcogligorov/48-teams-publicly-replaced-minio-they-didnt-announce-it-on-forums-they-filed-issues-4ajg</guid>
      <description>&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;So I searched public GitHub issues and discussions. Since the archive, I've found &lt;strong&gt;48 teams&lt;/strong&gt; writing about replacing MinIO in their own repos.&lt;/p&gt;

&lt;p&gt;What they wrote wasn't "looking for a MinIO alternative". It was things like:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;"MinIO images no longer download, so new dev stacks and k3s hosts cannot start"&lt;/li&gt;
&lt;li&gt;"MinIO OSS no longer maintained" (it broke their Docker builds)&lt;/li&gt;
&lt;li&gt;"Replace MinIO as the backup target"&lt;/li&gt;
&lt;li&gt;a national ID platform that runs on-premise for governments, deciding which S3 stores to support next&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;These are teams with a broken build, a deadline and a decision to make right now.&lt;/p&gt;

&lt;h2&gt;
  
  
  What they're choosing between
&lt;/h2&gt;

&lt;p&gt;A team can name more than one:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;SeaweedFS: 16&lt;/li&gt;
&lt;li&gt;Cloudflare R2: 13&lt;/li&gt;
&lt;li&gt;RustFS: 11&lt;/li&gt;
&lt;li&gt;Garage: 11&lt;/li&gt;
&lt;li&gt;AWS S3: 10&lt;/li&gt;
&lt;li&gt;Ceph: 4&lt;/li&gt;
&lt;li&gt;Backblaze B2: 3&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The lesson, if you sell a dev tool
&lt;/h2&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;Three things to look for:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;An issue title that mentions a competitor and "replace", "remove" or "migrate".&lt;/li&gt;
&lt;li&gt;A build or deploy that fails because of that competitor.&lt;/li&gt;
&lt;li&gt;A short list of alternatives in the body. That's an evaluation in progress.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Free offer
&lt;/h2&gt;

&lt;p&gt;I'm building a tool that runs this search automatically. If you sell a dev tool, &lt;strong&gt;comment with your product and the competitor you'd like to win users from&lt;/strong&gt;. I'll run the same search for the first 10 and reply with what I find, for free.&lt;/p&gt;

</description>
      <category>marketing</category>
      <category>opensource</category>
      <category>devops</category>
      <category>startup</category>
    </item>
  </channel>
</rss>
