11 engineers on Hacker News describe using MinIO first-hand: 3 endorse it, 5 regret it, 0 are mixed.
“We switched over after MinIO license changes and after evaluating a few different stacks.”
regret · production · markab21 · 2026-09-15 · source ↗ · wrong label?“I've been using minio for local dev but that version is unmaintained now.”
regret · personal · igor47 · 2025-12-19 · source ↗ · wrong label?“running our own minio clusters in the same datacenter as the tools that generate and consume that data is a lot faster and cheaper than using S3”
endorse · production · cortesoft · 2025-12-03 · source ↗ · wrong label?“It also fixed all of the performance problems we had on MinIO.”
regret · production · wczekalski · 2025-10-22 · source ↗ · wrong label?“Issues we have seen have mostly been related to reliability of our on prem Minio cluster which is used to store the data.”
regret · production · 0.5 yr · pjp1981 · 2025-07-19 · source ↗ · wrong label?“We replaced it with our custom storage service... the api documentation for minio were shit. and its not open source anymore”
regret · production · selfdb_io · 2025-06-13 · source ↗ · wrong label?“MinIO clusters (via the operator) are not that tricky to operate as long as you follow the well trodden path.”
endorse · production · adamcharnock · 2024-12-02 · source ↗ · wrong label?“if we get 80% out of it, it is good enough. Pricing is far better with that amount of data if you self-host.”
endorse · production · chrisandchris · 2022-11-03 · source ↗ · wrong label?“substitute Docker containers for RDS and MinIO for S3 without deviating too far from our production configuration”
neutral · production · 18nleung · 2025-10-04 · source ↗ · wrong label?“We run s3 (minio rook ceph on k8s) locally so the network latency is a cluster latency.”
neutral · production · gigatexal · 2019-10-05 · source ↗ · wrong label?