• Distributed Architecture: Scalable and fault-tolerant design suitable for large-scale deployments.

• S3 Compatibility: Seamless integration with existing S3-compatible applications and tools.

• Data Lake Support: Optimized for high-throughput big data and AI workloads.

• Open Source: Licensed under Apache 2.0, encouraging unrestricted community contributions and commercial usage.

• User-Friendly: Designed with simplicity in mind for easy deployment and management.

RustFS vs MinIO Performance

Stress Test Environment:

| Type | Parameter | Remark |
|---------|-----------|----------------------------------------------------------|
| CPU | 2 Core | Intel Xeon (Sapphire Rapids) Platinum 8475B, 2.7/3.2 GHz |
| Memory | 4GB | |
| Network | 15Gbps | |
| Drive | 40GB x 4 | IOPS 3800 / Drive |

<https://github.com/user-attachments/assets/2e4979b5-260c-4f2c-ac12-c87fd558072a>

RustFS vs Other Object Storage

| Feature | RustFS | Other Object Storage |
| :--- | :--- | :--- |
| Console Experience | Powerful Console<br>Comprehensive management interface. | Basic / Limited Console<br>Often overly simple or lacking critical features. |
| Language & Safety | Rust-based<br>Memory safety by design. | Go or C-based<br>Potential for memory GC pauses or leaks. |
| Data Sovereignty | No Telemetry / Full Compliance<br>Guards against unauthorized cross-border data egress. Compliant with GDPR (EU/UK), CCPA (US), and APPI (Japan). | Potential Risk<br>Possible legal exposure and unwanted data telemetry. |
| Licensing | Permissive Apache 2.0<br>Business-friendly, no "poison pill" clauses. | Restrictive AGPL v3<br>Risk of license traps and intellectual property pollution. |
| Compatibility | 100% S3 Compatible<br>Works with any cloud provider or client, anywhere. | Variable Compatibility<br>May lack support for local cloud vendors or specific APIs. |
| Edge & IoT | Strong Edge Support<br>Ideal for secure, innovative edge devices. | Weak Edge Support<br>Often too heavy for edge gateways. |
| Risk Profile | Enterprise Risk Mitigation<br>Clear IP rights and safe for commercial use. | Legal Risks<br>Intellectual property ambiguity and usage restrictions. |

Staying ahead

Star RustFS on GitHub and be instantly notified of new releases.

<img src="https://github.com/user-attachments/assets/7ee40bb4-3e46-4eac-b0d0-5fbeb85ff8f3" />

Quickstart

To get started with RustFS, follow these steps:

1. One-click Installation (Option 1)

  curl -O https://rustfs.com/install_rustfs.sh && bash install_rustfs.sh

The RustFS container runs as a non-root user rustfs (UID 10001). If you run Docker with -v to mount a host directory, please ensure the host directory owner is set to 10001, otherwise you will encounter permission denied errors.

 # Create data and logs directories
 mkdir -p data logs
 # Change the owner of these directories
 chown -R 10001:10001 data logs
 # Using latest version
 docker run -d -p 9000:9000 -p 9001:9001 -v $(pwd)/data:/data -v $(pwd)/logs:/logs rustfs/rustfs:latest
 # Using specific version
 docker run -d -p 9000:9000 -p 9001:9001 -v $(pwd)/data:/data -v $(pwd)/logs:/logs rustfs/rustfs:1.0.0-alpha.76

You can also use Docker Compose. Using the docker-compose.yml file in the root directory:

docker compose --profile observability up -d

NOTE: We recommend reviewing the docker-compose.yaml file before running. It defines several services including Grafana, Prometheus, and Jaeger, which are helpful for RustFS observability. If you wish to start Redis or Nginx containers, you can specify the corresponding profiles.

3\. Build from Source (Option 3) - Advanced Users

For developers who want to build RustFS Docker images from source with multi-architecture support:

# Build multi-architecture images locally
./docker-buildx.sh --build-arg RELEASE=latest
Build and push to registry

./docker-buildx.sh --push
Build specific version

./docker-buildx.sh --release v1.0.0 --push
Build for custom registry

./docker-buildx.sh --registry your-registry.com --namespace yourname --push

The docker-buildx.sh script supports:
\- Multi-architecture builds: linux/amd64, linux/arm64
\- Automatic version detection: Uses git tags or commit hashes
\- Registry flexibility: Supports Docker Hub, GitHub Container Registry, etc.
\- Build optimization: Includes caching and parallel builds

You can also use Make targets for convenience:

make docker-buildx                    # Build locally
make docker-buildx-push               # Build and push
make docker-buildx-version VERSION=v1.0.0  # Build specific version
make help-docker                      # Show all Docker-related commands

> Heads-up (macOS cross-compilation): macOS keeps the default ulimit -n at 256, so cargo zigbuild or ./build-rustfs.sh --platform ... may fail with ProcessFdQuotaExceeded when targeting Linux. The build script attempts to raise the limit automatically, but if you still see the warning, run ulimit -n 4096 (or higher) in your shell before building.

4\. Build with Helm Chart (Option 4) - Cloud Native