{"id":170868,"date":"2025-06-01T14:44:18","date_gmt":"2025-06-01T14:44:18","guid":{"rendered":"https:\/\/linuxiac.com\/?p=170868"},"modified":"2025-06-01T16:32:11","modified_gmt":"2025-06-01T16:32:11","slug":"minio-steering-users-toward-paid-subscriptions","status":"publish","type":"post","link":"https:\/\/linuxiac.com\/minio-steering-users-toward-paid-subscriptions\/","title":{"rendered":"Is It Still Open Source? MinIO Steering Users Toward Paid Subscriptions"},"content":{"rendered":"\n

Let me start by saying this: MinIO is fantastic software, and I genuinely like it. I\u2019ve used it in several projects, and the results have always been excellent. But for those who might not be familiar with it, here\u2019s a quick overview without going deeper into boring technical details.<\/p>\n\n\n\n

MinIO<\/a> is a high-performance, open-source object storage server with one big, fundamental highlight\u2014it’s fully compatible with Amazon S3, AWS’s service for storing files online, such as photos, videos, documents, backups, and more.<\/p>\n\n\n\n

So, like S3, MinIO lets you store and manage large amounts of unstructured data using a simple web or API interface. As you guessed, it’s also primarily used in cloud-native environments and supports scalability, redundancy, and data protection features. And here\u2019s its biggest advantage over S3 \u2014 it\u2019s free and open-source (AGPLv3 license).<\/p>\n\n\n\n

Thanks to this and its powerful features, all directly available and manageable via sleek UI, MinIO has earned a solid reputation as the go-to choice for DevOps teams, cloud engineers, data engineers, data scientists, and software developers as a reliable, enterprise-grade solution that\u2019s free to use and offers S3-compatible (and often even better) functionality.<\/p>\n\n\n\n

So, everything was going just fine\u2026 until a few days ago, when a PR titled \u201cImplemented AGPL MinIO Object Browser simplified Console<\/a>\u201d finally got merged. That\u2019s when the truth behind this so-called \u201csimplification\u201d \u2014 and the real intent driving it \u2014 started to come into focus.<\/p>\n\n\n\n

Here are two screenshots (provided by a Reddit user<\/a>) comparing the MinIO admin console before and after the change to give you a better idea of what this \u201csimplification\u201d actually looks like in practice.<\/p>\n\n\n\n

\"MinIO<\/a>
MinIO Admin Console (Before)<\/figcaption><\/figure>\n\n\n\n
\"MinIO<\/a>
MinIO Admin Console (After)<\/figcaption><\/figure>\n\n\n\n

Wow! That’s what I call a true “simplification.” You don\u2019t need to be a tech genius to notice the glaringly obvious \u2014 all the essential MinIO admin features have quietly vanished from the web console<\/strong> (except the object browser).<\/p>\n\n\n\n

For those who love diving into the numbers, here\u2019s the breakdown: the PR in question touched 1,086 files, with 66,208 lines added and a whopping 191,451 lines removed. In simple words, that\u2019s 125,243 lines of code cleaned up.<\/p>\n\n\n\n

And just when you’re scratching your head thinking, “Wait, what\u2019s going on here?”<\/em>, you stumble across a MinIO developer’s comment explaining that if you want the full-featured, user-friendly console back, well… you\u2019ll just need to upgrade to the paid offering. Shortly after, the discussion thread gets locked. No more questions, no more comments.<\/p>\n\n\n\n

Just for information, their commercial licensed version<\/a> appears to start at $96,000\/year (even for 1TiB capacity).<\/p>\n\n\n\n

But let\u2019s not be too gloomy about it. I\u2019ll give credit where it\u2019s due\u2014those features are<\/em> still around<\/a>. The catch? They\u2019re now only accessible through the mc admin<\/code> – a command-line tool used for administrative tasks on MinIO servers. So, it\u2019s time to roll up your sleeves, say goodbye to the luxury of point-and-click admin UIs, and get your hands dirty in the command line\u2014just like real IT pros do.<\/p>\n\n\n\n

\"MinIO<\/a>
MinIO deprecations in the new version.<\/figcaption><\/figure>\n\n\n\n

Is MinIO Still Open Source? Not Really.<\/h2>\n\n\n\n

Like it or not, the first thing that comes to mind when looking at this situation is last year\u2019s Redis drama. At least in their case, they had the guts to be upfront\u2014they officially changed their license, which meant stepping out of the open-source world<\/a>.<\/p>\n\n\n\n

As you can guess, this move sparked an immediate and inevitable response; the community launched the Valkey project<\/a> as a drop-in replacement, which even improved Redis in some ways. A little later, major Linux distros started removing Redis from their repos and offering the new alternative, Valkey, as its replacement.<\/p>\n\n\n\n

Somewhere in that moment, the company realized that chasing a short-term win had cost them the bigger picture. About a year later, recognizing their mistake, they reversed course and returned to an open source license<\/a>. Sadly, what\u2019s done is done.<\/p>\n\n\n\n

I’m sure MinIO has carefully analyzed the situation, weighed the risks, and decided to take a more strategic route\u2014one that, on the ethical side, clashes with all the values of open source. In short, they\u2019re saying: We\u2019re not changing the license, and yes, we\u2019re still technically open source. But if you want to unlock our software’s full power and convenience, you must pay for it.<\/p>\n\n\n\n

However, I’m not sure that MinIO would be where it is today without the voluntary work of open-source developers who helped shape and improve the software alongside the company’s own team. So, MinIO\u2014are you really confident this move is right and not follow in Redis’s footsteps, because\u2026<\/p>\n\n\n\n

Open Source > Money. Always.<\/h2>\n\n\n\n

Every great open-source project has earned its place by building trust within the developer community. It\u2019s not just about the technical work or the time and skills devs generously contribute, though those matter a lot. What really sets a project apart is something even more valuable: visibility<\/strong>.<\/p>\n\n\n\n

When a project gains traction and starts reaching thousands \u2014 even millions \u2014 of developers and open source enthusiasts, that kind of exposure becomes a powerful form of promotion. And the best part? It\u2019s completely organic, free, and more effective than anything even the biggest tech companies could buy.<\/p>\n\n\n\n

However, the consequences can be difficult to foresee if you lose this visibility and trust. The open-source community is truly one of a kind \u2014 it fiercely supports the ideas and projects it believes in. But once that trust is broken, it’s a point of no return \u2014 or if there is, the road is incredibly tough. It\u2019s happened before, and history has shown just how real that risk is.<\/p>\n\n\n\n

So, MinIO, I have no doubt that in the short term, your carefully crafted strategy\u2014put together by some sharp financial minds\u2014will pay off. You’ll likely see a bump in paid subscriptions, and that’s a win on paper. But I also expect something else\u2014something I hope you’ve taken into account: the emergence of an alternative.<\/p>\n\n\n\n

When open-source supporters pull back, they tend to leave a gap, and gaps don\u2019t stay empty for long. There\u2019s always someone ready to fill the space, often with something just as good, if not better. Take Redis, for example: it took only ten days for Valkey<\/a> to step up after their announcement. Honestly, I wouldn\u2019t be surprised if a similar thing happens here. Or, maybe, I could be wrong. Let\u2019s wait and see how it all plays out.<\/p>\n\n\n\n

MinIO Alternatives<\/h2>\n\n\n\n

Just to add for our readers, if you’re looking for MinIO alternatives, on the S3 compatibility side, some options currently include Garage<\/a>, Ceph<\/a>, SeaweedFS<\/a>, OpenIO<\/a>, JuiceFS<\/a>, and Apache Ozone<\/a>.<\/p>\n\n\n\n

That said, it’s important to note that while these are all open-source, software-defined storage platforms, they don\u2019t offer a replacement for how MinIO works, its full range of features, or how you’re probably used to it. They just offer identical functionality.<\/p>\n\n\n\n

Out of the options listed above, among recent community comments, Garage – a lightweight geo-distributed data store that implements the Amazon S3 object storage protocol, seems like the most natural choice for replacing MinIO.<\/p>\n\n\n\n

The downside is that the software lacks a web-based admin interface (for now\u2014initial work has already started in this direction). Luckily, another open-source project called Garage Web UI<\/a> steps in to fill that gap.<\/p>\n\n\n\n

\"Garage<\/a>
Garage Web UI<\/figcaption><\/figure>\n\n\n\n

Moreover, keep in mind that Garage doesn\u2019t support object versioning and retention. So, if those aren\u2019t deal-breakers for you, it\u2019s definitely worth considering. However, I highly recommend first looking here<\/a> for a detailed comparison between platforms and checking the compatibility sheet if you’re considering migrating.<\/p>\n\n\n\n

Bottom Line<\/h2>\n\n\n\n

The MinIO story isn’t the first and probably won’t be the last. It follows a familiar pattern: a project launches with the open-source flag held high, grounded in the values of FOSS. It finds success, builds a strong community, and eventually catches the attention of enterprise players.<\/p>\n\n\n\n

As business demand grows, the project introduces paid subscriptions\u2014something many companies are willing to pay for. That, in turn, drives the need for more funding, more development, and a more structured business model. Over time, the project hits a tipping point: it\u2019s popular, widely adopted, and well-positioned in the market.<\/p>\n\n\n\n

At that point, the original FOSS spirit starts to take a backseat. When there\u2019s real money on the table, continuing to give everything away for free becomes harder to justify. So, the focus shifts. Paid subscriptions move front and center. The open-source foundation helped it grow, but now financial goals are calling the shots.<\/p>\n\n\n\n

Does MinIO have the right to do this? Absolutely. It\u2019s their software, and they\u2019re free to do with it as they see fit. But is the approach they\u2019ve taken questionable\u2014morally and ethically\u2014especially in the context of the open-source community? Without a doubt, yes.<\/p>\n\n\n\n

So, is MinIO still open source? Technically, yes\u2014it’s licensed under AGPLv3. However, given their recent actions, which go against FOSS’s ethical and moral values, continuing to call it feels both sad and ironic.<\/p>\n\n\n\n

As I said earlier, trust and visibility are everything in the FOSS world. With this move, MinIO has lost the former, and the latter is at risk once that’s gone. I genuinely wish them success in the business-focused direction they\u2019re pursuing. They\u2019ll need it. Because from this point on, the road back to the FOSS community looks less like a path and more like a mirage.<\/p>\n","protected":false},"excerpt":{"rendered":"

MinIO removes key web console features, nudging users toward its paid offering. Is this still open-source, or is it just an AGPLv3 on paper?<\/p>\n","protected":false},"author":10,"featured_media":171168,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7,5],"tags":[6372,3585],"class_list":["post-170868","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-software","category-news","tag-minio","tag-storage"],"blocksy_meta":[],"_links":{"self":[{"href":"https:\/\/linuxiac.com\/wp-json\/wp\/v2\/posts\/170868","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/linuxiac.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/linuxiac.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/linuxiac.com\/wp-json\/wp\/v2\/users\/10"}],"replies":[{"embeddable":true,"href":"https:\/\/linuxiac.com\/wp-json\/wp\/v2\/comments?post=170868"}],"version-history":[{"count":0,"href":"https:\/\/linuxiac.com\/wp-json\/wp\/v2\/posts\/170868\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/linuxiac.com\/wp-json\/wp\/v2\/media\/171168"}],"wp:attachment":[{"href":"https:\/\/linuxiac.com\/wp-json\/wp\/v2\/media?parent=170868"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/linuxiac.com\/wp-json\/wp\/v2\/categories?post=170868"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/linuxiac.com\/wp-json\/wp\/v2\/tags?post=170868"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}