SeaweedFS has a great IAM/STS/policy layer as well. It can support a secretless auth flow similar enough to AWS IRSA with it's OIDC integration
Alternatives to MinIO for single-node local S3
61–70 of 112 posts
Re: Alternatives to MinIO for single-node local S3
#62Are any of these truly alternatives? MinIO is built for scale and not small projects. Ceph is maybe closest.
as per the title the scope here is single-node local S3
Re: Alternatives to MinIO for single-node local S3
#63[deleted]
Re: Alternatives to MinIO for single-node local S3
#64I had previously used seaweedfs, which has more moving parts but seems more feature-rich. It was overkill for a homelab, so I went to garage. Garage is very stable, but the metadata engine / file MUST live on NVMe. Otherwise it gets slow on small files. It also lacks features like per bucket retention settings and stuff. It really is "just" a S3 bucket.
The very first thing Garage did after I installed it on a test three-node cluster is get corrupted and lose files.
No thanks.
Re: Alternatives to MinIO for single-node local S3
#65I had previously used seaweedfs, which has more moving parts but seems more feature-rich. It was overkill for a homelab, so I went to garage. Garage is very stable, but the metadata engine / file MUST live on NVMe. Otherwise it gets slow on small files. It also lacks features like per bucket retention settings and stuff. It really is "just" a S3 bucket.
[deleted]
Re: Alternatives to MinIO for single-node local S3
#66A notable mention should also be Versity GW, https://github.com/versity/versitygw/
Use it for my homelab too, super nice and stable. Support also delivering static website/asset.
https://github.com/versity/versitygw/#static-website-hosting
Re: Alternatives to MinIO for single-node local S3
#67> 2026-03-02: Ruohang Feng has forked MinIO to pgsty/minio and is promising to maintain a stable, CVE-patched, distribution. This is what I went with. I use it in end to end tests as an S3 simulator that starts and stops instantly and reads & writes to a local directory, - as you'd expect it's great in that role. No complaints. Given the fork's maintainer puts their real name on it & stakes their reputation, you'd as…
According to https://github.com/pgsty/silo it's pgsty/silo now: > Renamed from pgsty/minio to pgsty/silo, default branch master → main, on 2026-08-06
Neat!
I had switched some projects to SeaweedFS's Docker image. It worked well. This is good to know there is a successor open source project that would require no code changes to use. Will evaluate.
Re: Alternatives to MinIO for single-node local S3
#68Are any of these truly alternatives? MinIO is built for scale and not small projects. Ceph is maybe closest.
Define scale.
When I tried minio 5 years ago it choked pretty quick on storing billions of objects
Re: Alternatives to MinIO for single-node local S3
#69> 2026-03-02: Ruohang Feng has forked MinIO to pgsty/minio and is promising to maintain a stable, CVE-patched, distribution. This is what I went with. I use it in end to end tests as an S3 simulator that starts and stops instantly and reads & writes to a local directory, - as you'd expect it's great in that role. No complaints. Given the fork's maintainer puts their real name on it & stakes their reputation, you'd as…
Right.
It's nice to hear about other products, but OP made it sound like Minio disappeared and was not an option. Neither are true. Yes the company moved on but the old source is sitting there and that version is pretty good as-is. We're still using it in prod, no issues for us. The old container images are floating around and you're free to copy them to wherever.
If you need support or newer features, fork it or use ^ this fork.
Re: Alternatives to MinIO for single-node local S3
#70Really happy with my own https://deltaglider.com/
- Filesystem backend - Encrypted S3 backend - Compressed S3 backend (Saving a ton of money here) - Cross backend replication - Full IAM - Full GUI with OIDC auth