Technology

RustFS

A high-performance, Rust-based, S3-compatible object storage server positioned as a truly open-source alternative to MinIO.

Current as of 2026-10-25 · v1.0.4

10 connections5 resources7 posts

Summary

What it is

A high-performance, Rust-based, S3-compatible object storage server positioned as a truly open-source alternative to MinIO.

Where it fits

Following the MinIO community repository archival in 2026, RustFS emerged as one of the leading candidates for self-hosted S3 workloads. It targets the performance tier — organizations needing MinIO-like throughput with a permissive license and no single-vendor governance risk.

Misconceptions / Traps
  • The 2.3× small-object headline is only on small objects. Independent benchmark (GitHub Issue #73, mid-2025) showed MinIO leading on 20 MiB sequential reads — 53 Gbps vs 23 Gbps throughput, 24 ms vs 260 ms TTFB. The RustFS team acknowledged the gap and added "Big File Optimization" to the roadmap. Verdict: small-object champion today, large-file story still in progress.
  • "Production-ready" is the project's own label. RustFS hit 1.0 GA on September 16, 2026 (32,000+ GitHub stars) and now calls the core engine production-ready — but that's a self-assertion, not a third-party audit, and operational maturity (replication, backups, recovery testing) is still on you. The pre-1.0 alpha/beta/RC builds also carried CVEs that don't reflect on the GA line.
  • "Drop-in MinIO replacement" is true at the binary + bucket layout level, but enterprise features (OPA policy, RDMA, GPU Direct Storage) are roadmap items, not shipped — if your MinIO deployment uses any of these you can't swap yet.
  • Decentralized-metadata architecture is a structural advantage but it shifts ops thinking — there is no metadata server to back up or upgrade independently. Consistent hashing handles failover; cluster topology changes need rebalancing.
  • Built on Tokio async runtime; ~2 GB RAM minimum even for a single-node deployment, which surprises operators porting from Ceph or larger stacks.

Performance posture: Cluster scale up to 323 GB/s read and 183 GB/s write in evaluation testing — Rust ownership/ARC eliminates GC pauses that hurt MinIO under sustained millions-of-small-files workloads (the dominant AI dataset access pattern).

Key Connections
  • implements S3 API — S3-compatible object storage
  • solves Vendor Lock-In — open-source alternative to AWS S3 and MinIO
  • solves AGPL Licensing Risk — Apache 2.0 license removes the AGPLv3 exposure that drove migration off MinIO
  • competes_with MinIO — direct replacement target

Definition

What it is

A high-performance, Rust-based, S3-compatible object storage server positioned explicitly as a drop-in MinIO binary replacement — same on-disk bucket layout, same admin verbs, swap the executable. Apache 2.0 licensed. Reached 1.0 GA on September 16, 2026 (1.0.4 as of late October) after a 2026 beta→RC run, carrying heavy ecosystem momentum out of the MinIO archival. Project-published benchmarks claim ~2.3× faster performance for 4 KB small-object payloads vs MinIO and peak read throughput up to 323 GB/s on saturated NVMe arrays (vendor-side numbers — independent 2026 benchmarks show MinIO still well ahead on reads) — Rust's memory-safe, ARC/ownership model eliminates the GC-pause latency tail that plagues Go-based storage engines under millions of small files (the dominant access pattern in AI data preparation pipelines). The community has begun pushing for an NFS-mount feature request (rustfs/rustfs#2481) that would parallel AWS S3 Files semantics — a signal that the post-MinIO market expects POSIX-on-object as table stakes, not a hyperscaler luxury.

Why it exists

Following the December 2025 MinIO maintenance-mode pivot and the April 25, 2026 main-repo archival, the self-hosted S3 ecosystem needs truly open-source alternatives. RustFS targets the migration path most aggressively — same binary footprint, same data layout, no re-architecture required.

Primary use cases

Drop-in MinIO replacement, self-hosted S3-compatible storage for data lakes, organizations needing long-term licensing predictability, high-performance object storage for AI/ML pipelines.

Connections10

Outbound7
scoped_to2
S3Object Storage
implements1
S3 API
enables1
Lakehouse Architecture
solves2
Vendor Lock-InAGPL Licensing Risk
competes_with1
MinIO
Inbound3
competes_with2
MinIOAlarik
enables1
Godwit Sync

Resources5

GitHubHigh
github.com/rustfs/rustfs

Source repository for RustFS, the Rust-based S3-compatible server designed as an open-source MinIO alternative. 23k+ stars, 104 contributors, alpha-stage.

GitHub IssueHigh
github.com/rustfs/rustfs/issues/73

The independent large-file benchmark thread — MinIO leads on 20 MiB sequential reads (53 Gbps vs 23 Gbps, 24 ms vs 260 ms TTFB). Required reading before adopting RustFS for video / pre-training-corpus workloads.

GitHub IssueHigh
github.com/rustfs/rustfs/issues/2481

Community NFS-mount feature request — the post-MinIO market expecting POSIX-on-object as table stakes parallels the AWS S3 Files architectural shift.

BlogMedium
www.infoq.com/news/2025/12/minio-s3-api-alternatives/

Analysis of post-MinIO S3 alternatives including RustFS, covering architecture, performance, and licensing comparisons.

BlogMedium
iomete.com/resources/blog/evaluating-s3-compatible-storage-f...

Comprehensive evaluation of S3-compatible storage options for data lakehouses including RustFS, SeaweedFS, and Garage.

Featured in

2026-10-20What Fits on One Box NowA practical pass at the local-first stack: what you can actually run on a single machine with your own object storage in late 2026, which layer to pick at each decision, and where one box genuinely stops being enough. October moved the line — Polars 2.0 turned out-of-core spill on by default and Milvus 3.0 rebuilt on lake-native storage — so workloads that needed a cluster last quarter no longer do. This is the decision path, with the guides that go deeper at each step.2026-06-06Storage Grew an Agent InterfaceThe S3 API made storage programmable for applications. In a six-week stretch of 2026, the storage layer grew a second interface — for agents. Weaviate, Pinecone, and RustFS all shipped built-in MCP servers; cheap inference and agentic retrieval made it inevitable; and the Apache Polaris CVE cluster showed the security bill that comes due. This is the discoverability inflection for self-hosted AI data infrastructure.2026-05-16When AI Memory Became an Architecture: KV-Cache Persistence, MCP, and the Night S3 Got Its Memory TierStateful agents needed stateful storage. Tonight 33 new nodes joined the index: Mem0, Zep, LMCache, SGLang, Mooncake, MCP, cuObject, BlueField-4, Animesis CMA. The architectural thesis: AI memory infrastructure crystallized around object storage in 2026, and the persistence layer the industry settled on is S3.2026-05-08When the Index Gained 13 Nodes: A Field Guide to the May 2026 WaveOn May 7 the index added 13 new nodes — five technologies, six pain points, one architecture, one standard. Each answers a specific question engineers building on object storage are asking right now: what is China's S3 stack, why are GPUs starving, what replaced MinIO, what are the three data gravity wells, and a few more. This post walks through them by question rather than by node type, because that's how the questions actually arrive in production.2026-05-07When DeepSeek Made Storage Strategic: The China Direction Reshaping the S3 EcosystemDeepSeek's $5.6M training run didn't just reset model architecture. It made object storage performance-critical, made silicon export controls a storage decision, and pushed Aliyun OSS, Tencent COS, and Huawei OBS from regional curiosities into the global S3 vocabulary. This index added 13 nodes to track what changed.2026-05-01What Survived MinIO: The Post-Archive S3 Server Landscape, May 2026On April 25, 2026, MinIO archived its main GitHub repository. This index has tracked Vendor Lock-In as a first-class pain point since launch. Here is what the post-MinIO Apache-2.0 server set actually looks like — Alarik, RustFS, SeaweedFS, Garage — and what the fragmentation tells us about what we believed open-source meant.2026-03-21The Shift to Local Intelligence: How Local S3 and Edge Inference Are Replacing Cloud LatencyThe economics and architecture behind the migration from cloud inference to local-first AI — covering the Local S3 semantic storage pattern, CXL memory expansion, specialized inference silicon, and why 80% of AI inference is moving to the edge.