@jankatins
Hey, thanks for the question! The comparison was very focused on our specific scenario - two DCs, rather mediocre network storage and high availability on the read path (can tolerate one DC going down, but no quorum for writes).

By the time I strip all the company specifics, there will be barely anything left worth reading.

A very short summary of some alternatives I looked into:
- ceph - a beast to operate just for S3. 
- rook - easier but our network storage is (still) inadequate.
- Seaweedfs: didn't test, looked solid (features!), some aspects gated behind enterprise; and procurement is tons of pain here.
- RustFS - I better not comment on that one publicly.

Other than clustering, other factors included:
- issue count / commit activity
- focused solution vs offering everything
- projects with far too much "development activity" and features in relation to the age

There are a ton of new and hot alternatives and I am not betting on the ability of random people to use LLMs in moderation. So several candidates were not considered at all.