RustFS for S3-Compatible Object Storage

Open-source object storage is in flux right now, so infrastructure teams are re-checking their options. RustFS is worth a close look because it aims for the operational simplicity people liked in MinIO while leaning on Rust for memory safety and performance. The project is trending on GitHub today, which makes this a good time to evaluate where it fits.

What is RustFS?

RustFS is a distributed object storage system written in Rust. The project positions itself as S3-compatible, open-source under Apache 2.0, and suitable for AI, data lake, and general infrastructure workloads. It also exposes an OpenStack Swift API and supports Keystone authentication, which makes it more flexible than many newer object stores.

For SRE teams, the appeal is straightforward. You get a modern storage service with a web console, container images, Helm-based Kubernetes deployment, and a documented path to observability through Prometheus, Grafana, and Jaeger profiles in the provided compose setup.

Key Features

• S3-compatible API: useful for backup pipelines, artifact storage, logs, and internal platform tooling that already speaks S3
• Apache 2.0 license: attractive for teams avoiding restrictive licensing surprises
• Rust implementation: memory safety and predictable performance matter when storage becomes critical infrastructure
• Multiple deployment paths: single-node, Docker, Compose, Helm, source builds, and even Nix
• Built-in operator ergonomics: web console on port 9001 plus docs for TLS and distributed deployment

Installation

The official README shows a quick Docker path for local evaluation:

mkdir -p data logs
chown -R 10001:10001 data logs

docker run -d \
  -p 9000:9000 \
  -p 9001:9001 \
  -v $(pwd)/data:/data \
  -v $(pwd)/logs:/logs \
  rustfs/rustfs:latest

If you want the broader demo stack with observability components, the project also ships a compose file:

docker compose --profile observability up -d

For Kubernetes environments, RustFS provides Helm-based installation through its chart docs.

Usage

After startup, open http://localhost:9001 and log in with the default credentials rustfsadmin / rustfsadmin. From there you can create a bucket and start uploading objects through the console or any S3-compatible client.

A practical first test for platform teams is simple: point a non-critical backup job or CI artifact workflow at a pilot RustFS instance and validate the exact S3 calls your tooling makes. That matters because "S3-compatible" can still hide edge-case differences in policy behavior, multipart uploads, lifecycle rules, or event integrations.

Operational Tips

Treat RustFS as a candidate for staged adoption, not a blind drop-in replacement. Start with single-node or lab environments, enable observability from day one, and test restore workflows instead of only upload paths. If you mount host volumes in Docker, remember the container runs as UID 10001, so ownership must match or writes will fail.

Also review the project status table before production rollout. The RustFS README lists some features, including lifecycle management and distributed mode, as under testing. That is not a deal-breaker, but it should shape how aggressively you deploy it.

Conclusion

RustFS looks like one of the more interesting object storage projects to watch in 2026. The combination of Apache 2.0 licensing, Rust implementation, S3 compatibility, and cloud-native packaging gives it a real chance with teams that want an alternative in this category. Just validate your workload carefully and keep the rollout disciplined.

Looking for an AI-powered platform to enhance your SRE workflows? Check out Akmatori, an open-source AI agent designed for infrastructure teams. Built on Gcore infrastructure for reliable global performance.