Alternatives to MinIO untuk local S3 single-node
Oleh Zai · Let's Make It Easy
Dipublikasikan 2026-09-15
Perbandingan pengganti MinIO untuk Docker Compose, demo data, dan CI dengan fokus pada S3 compatibility, setup, dan governance.
MinIO has been the default answer whenever a local project needed an S3-compatible object store. That default got shakier after the company behind MinIO changed direction, leaving demos and CI pipelines looking for a replacement. A recent comparison by Robin Moffatt focuses on a narrow but common job: one-node local S3 for Docker Compose projects, not production storage at scale.
1. What the comparison actually tests
The useful constraint is simplicity. Each candidate should have a Docker image, expose an S3-compatible API, be free to use, and work without a large cluster. The test setup uses DuckDB, an Iceberg REST Catalog, and object storage. A shell smoke test writes a small Iceberg table, reads it back through DuckDB, and checks the resulting Parquet, Avro, and metadata files in the bucket.
That is a much more practical test than comparing feature checklists. A tool can be excellent for distributed storage and still be a poor replacement for a three-container demo.
2. Which alternatives look practical
Moffatt's shortlist includes S3Proxy, RustFS, SeaweedFS, Zenko CloudServer, Garage, Apache Ozone, and Ceph Object Gateway. His conclusions are specific to local development. SeaweedFS and S3Proxy are the easiest fits for the tested setup. CloudServer also looks plausible, although its relationship with the wider Zenko and Scality tooling adds some cognitive overhead. RustFS is interesting but was still described as an alpha release, with a security issue noted in the comparison.
SeaweedFS has a separate S3 gateway and its project documentation describes using the S3 API with its filer and volume services. That makes it a reasonable candidate when a team wants local object storage without preserving MinIO itself.
3. The choice is about governance too
The comparison is not a claim that one replacement wins everywhere. It calls out licence changes, project governance, community health, and the bus factor. A project with a convenient Docker image can still become another migration problem if its maintainers disappear or its licence changes.
For a local demo, start with the smallest setup that passes your real test. For a production object store, evaluate durability, upgrades, security fixes, backup, and operational support separately. The same S3 API can hide very different trade-offs underneath.
The practical takeaway is simple: keep the storage interface stable, but make the implementation replaceable. Put the choice behind Compose variables and run the same smoke test against every candidate before your project grows around one vendor.
Referensi: https://rmoff.net/2026/01/14/alternatives-to-minio-for-single-node-local-s3/