Object storage has quietly become the backbone of modern infrastructure, holding everything from application backups and media libraries to the training datasets behind AI models. For years, teams that wanted an S3-compatible system they could run themselves reached for MinIO, but a shift in that project’s licensing left many of them looking for a new default. RustFS arrived in exactly that gap: an open-source, S3-compatible object storage system written entirely in Rust, released under Apache 2.0, and designed from the start for data lakes, analytics, and AI workloads.

What is RustFS?

RustFS is a distributed object storage system that exposes an S3-compatible API, so existing tools, SDKs, and applications can work with it without code changes. The project was open-sourced in July 2025 and reached its 1.0 general availability release in September 2026, having gathered more than 32,000 GitHub stars and over 10 million Docker Hub pulls along the way. It runs as a single binary on a laptop for testing and scales out to multi-node, multi-disk clusters with erasure coding, self-healing, and site replication in production. Alongside the S3 API it also speaks WebDAV, the OpenStack Swift API, and FTP/FTPS, and it is built specifically to migrate from or coexist with other S3-compatible platforms such as MinIO and Ceph.

Advantages:

1. Full S3 compatibility with a realistic migration path

RustFS implements the S3 API that most storage tooling already speaks, including multipart uploads, versioning, lifecycle rules, and event notifications. Because it is designed to run alongside existing MinIO or Ceph deployments, teams can move data gradually instead of committing to a single risky cutover.

2. Apache 2.0 license with no vendor lock-in

RustFS is released under the permissive Apache 2.0 license rather than a copyleft or source-available model, so organizations can deploy, modify, and embed it commercially without the licensing constraints that pushed many teams away from other object storage projects.

3. Written in Rust for memory safety and predictable latency

Rust gives RustFS memory safety without a garbage collector, which removes the GC pauses that cause unpredictable tail latency in storage systems. The project reports throughput advantages over comparable systems in small-object benchmarks, and the practical benefit for operators is steadier performance under sustained load.

4. Erasure coding, self-healing, and bitrot protection

Reed-Solomon erasure coding spreads data across disks and nodes so a cluster survives drive or server failures without the cost of full replication. Self-healing restores missing shards automatically, and bitrot detection catches silent data corruption before it ever reaches an application.

5. Enterprise-grade security and multi-tenancy

RustFS ships with IAM policies, OIDC single sign-on, KMS integration, server-side encryption, and mTLS, plus multi-tenancy for isolating teams or customers on shared infrastructure. Because it is self-hosted and sends no external telemetry, data stays inside the operator’s own boundaries, which matters for GDPR and similar compliance regimes.

6. Multi-protocol access and built-in observability

Beyond S3, RustFS serves the same data over WebDAV, Swift, and FTP/FTPS, which simplifies onboarding legacy applications that were never written for object storage. Native OpenTelemetry support feeds metrics and traces straight into Prometheus, Grafana, and Jaeger without additional exporters.

7. Deploys anywhere, from edge device to AI data center

RustFS runs on Linux, Windows, and macOS across amd64 and arm64, and it is distributed as standalone binaries, DEB and RPM packages, Docker images, and Kubernetes Helm charts with an Operator. The same lightweight footprint that suits edge and IoT nodes also scales into data lake and AI training clusters, with Apache Iceberg REST Catalog integration and data tiering for analytics workloads.

Conclusion:

RustFS has moved quickly from a new open-source project to a 1.0 release that covers the capabilities teams actually depend on: S3 compatibility, erasure coding, layered security, multi-tenancy, and Kubernetes-native deployment. Its Apache 2.0 license and Rust foundation make it a practical answer for organizations that want self-hosted object storage without licensing uncertainty or garbage collection surprises. Anyone deciding where to keep their backups, media libraries, or AI training data should put RustFS on the shortlist and test it against their own workloads.