Versity's posix backend was the one that stuck for us, multipart uploads land as real files on disk so you can inspect them with ls when a test fails.
Alternatives to MinIO for single-node local S3
31–40 of 112 posts
Re: Alternatives to MinIO for single-node local S3
#32Running Sentry on prem, I had to swap out their default SeaweedFS setup for Garage because the former kept failing under concurrent writes. I tried digging around for a bit, but found that the swap was easier and faster, Garage has also worked great for single node use cases (e.g. tested up to around 10 TB of data). I still think that SeaweedFS is a cool project, might have been a config issue or something, wasn’t worth tweaking.
The setup for Garage sucks, especially cause their Docker image doesn’t automatically create keys or buckets and permissions for you like for example various RDBMS images do. Doing that the first time manually was annoying, but their docs are pretty nice and an AI agent can build you your own Docker image with custom init in about 15 minutes.
Worst with it I’ve had were issues with hooking up WinSCP to it directly to browse saved satellite data, initial connections would hang for some reason, not sure what the problem was either.
Also used Zenko but kinda got the feeling that the project wasn’t as healthy and straight up felt abandoned (e.g. the outdated container images and such), though there is some activity.
Re: Alternatives to MinIO for single-node local S3
#33Often just spinning up `localstack` works well, even if only for S3. Gives you other AWS services if you ever need them.
Re: Alternatives to MinIO for single-node local S3
#34> 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…
I might have to try this. I’m currently pinned on the last non-crippled version of minio
Re: Alternatives to MinIO for single-node local S3
#35Just use the damn file system. Why does everyone have to put HTTP between everything?
I like how you got 4 different comments all starting with "Because..." hah!
Re: Alternatives to MinIO for single-node local S3
#36My https://github.com/uroni/hs5 is designed for this use case.
One notable thing is that compared to MinIO (and others) it does not store the objects as individual files. I also have DuckDB directly integrated.
The readme has a comparison to Garage, seaweedfs, RustFS and Ceph.
Re: Alternatives to MinIO for single-node local S3
#37Rustfs, works pretty well for me
Yup, same. We use RustFS in a production system with no issues. We switched over after MinIO license changes and after evaluating a few different stacks.
We have heavy concurrent usage, and we haven't had a single issue yet.
Re: Alternatives to MinIO for single-node local S3
#38> 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
Re: Alternatives to MinIO for single-node local S3
#39Just use the damn file system. Why does everyone have to put HTTP between everything?
Because AFAIK the filesystem is at the same time a huge API and designed for a different use case. I can think of the following examples:
- very flat structures: storing hundred of thousands of files in a single directory will fail
- designed for local disks and NFS is a leaky abstraction:
- running a system using on locks will fail
- cache behaviors work fine for the "humans browsing files" usecase but not so much for other casesRe: Alternatives to MinIO for single-node local S3
#40Is there any "local"/minio-esque object store properly implements the full conditional GET/PUT/DELETE spec, ETag, etc.? I have struggled to find this in the past.