MinIO repository is no longer maintained

3r7j6qzi9jvnve wrote: post #2

See https://news.ycombinator.com/item?id=46136023 - MinIO is now in maintenance-mode It was pretty clear they pivoted to their closed source repo back then.

Maintenance-mode is very different from "THIS REPOSITORY IS NO LONGER MAINTAINED".

Re: MinIO repository is no longer maintained

#6

Post by jychang » Fri, Feb 13, 2026, 8:59 AM UTC

paulkre wrote: post #5

3r7j6qzi9jvnve wrote: post #2

See https://news.ycombinator.com/item?id=46136023 - MinIO is now in maintenance-mode It was pretty clear they pivoted to their closed source repo back then.

Maintenance-mode is very different from "THIS REPOSITORY IS NO LONGER MAINTAINED".

Yes, the difference is the latter means "it is no longer maintained", and the former is "they claim to be maintaining it but everyone knows it's not really being maintained".

Re: MinIO repository is no longer maintained

#7

Post by embedding-shape » Fri, Feb 13, 2026, 9:01 AM UTC

paulkre wrote: post #5

3r7j6qzi9jvnve wrote: post #2

See https://news.ycombinator.com/item?id=46136023 - MinIO is now in maintenance-mode It was pretty clear they pivoted to their closed source repo back then.

Maintenance-mode is very different from "THIS REPOSITORY IS NO LONGER MAINTAINED".

Given the context is a for-profit company who is moving away from FOSS, I'm not sure the distinction matters so much, everyone understands what the first one means already.

Re: MinIO repository is no longer maintained

#8

Post by courtcircuits » Fri, Feb 13, 2026, 9:03 AM UTC

PhilippGille wrote: post #3

They point to AIStor as alternative. Other alternatives: https://github.com/deuxfleurs-org/garage https://github.com/rustfs/rustfs https://github.com/seaweedfs/seaweedfs https://github.com/supabase/storage https://github.com/scality/cloudserver https://github.com/ceph/ceph Among others

From my experience, Garage is the best replacement to replace MinIO *in a dev environment*. It provides a pretty good CLI that makes automatic setup easier than MinIO. However in a production environment, I guess Ceph is still the best because of how prominent it is.

Re: MinIO repository is no longer maintained

#9

Post by merpkz » Fri, Feb 13, 2026, 9:04 AM UTC

I just bit the bullet last week and figured we are going to migrate our self hosted minio servers to ceph instead. So far 3 server ceph cluster has been setup with cephadm and last minio server is currently mirroring its ~120TB buckets to new cluster with a whopping 420MB/s - should finish any day now. The complexity of ceph and it's cluster nature of course if a bit scary at first compared to minio - a single Go binary with minimal configuration, but after learning the basics it should be smooth sailing. What's neat is that ceph allows expanding clusters, just throw more storage servers at it, in theory at least, not sure where the ceiling is for that yet. Shame minio went that way, it had a really neat console before they cut it out. I also contemplated le garage, but it seem elasticsearch is not happy with that S3 solution for snapshots, so ceph it is.

Re: MinIO repository is no longer maintained

#10

Post by dijit » Fri, Feb 13, 2026, 9:04 AM UTC

PhilippGille wrote: post #3

They point to AIStor as alternative. Other alternatives: https://github.com/deuxfleurs-org/garage https://github.com/rustfs/rustfs https://github.com/seaweedfs/seaweedfs https://github.com/supabase/storage https://github.com/scality/cloudserver https://github.com/ceph/ceph Among others

Would be cool to understand the tradeoffs of the various block storage implementations.

I'm using seaweedfs for a single-machine S3 compatible storage, and it works great. Though I'm missing out on a lot of administrative nice-to-haves (like, easy access controls and a good understanding of capacity vs usage, error rates and so on... this could be a pebcak issue though).

Ceph I have also used and seems to care a lot more about being distributed. If you have less than 4 hosts for storage it feels like it scoffs at you when setting up. I was also unable to get it to perform amazingly, though to be fair I was doing it via K8S/Rook atop the Flannel CNI, which is an easy to use CNI for toy deployments, not performance critical systems - so that could be my bad. I would trust a ceph deployment with data integrity though, it just gives me that feel of "whomever worked on this, really understood distributed systems".. but, I can't put that feeling into any concrete data.