RustFS
RustFS is an open-source, S3-compatible object store written in Rust.
Platform availability
Available on 6 of 10 platforms
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
89/100 Excellent
- Maintained
- 100last commit 2 days ago
- Popular
- 9136,297 GitHub stars
- Easy to install
- 856 install platforms, install notes, Docker image
- Light to run
- 602 GB minimum RAM, runs on ARM
Availability: platform listings confirmed today, links checked 10 days ago
- GitHub stars
- 36,297
- Open issues
- 89
- Last commit
- 2026-11-19
- Latest release
- 1.0.6
- License
- Apache-2.0
- Activity
- steady
Checked 2 days ago - source: GitHub (rustfs/rustfs)
Resources & Compatibility
Minimum requirements: 2 GB RAM. ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Start RustFS in Docker or Podman Run the Docker or Podman command with port 9000 exposed and a /data folder mapped in. Port 9000 is where you connect to RustFS to store and fetch files, and /data is the folder that actually holds your data, so keep that folder backed up. source
- Use the one-click installer On a single server, download and run the rustfs.com install script instead of copying files by hand. It sets up the base RustFS installation for you, which avoids missing pieces that stop it from running. source
- Set the binary and config paths Copy the rustfs program to /usr/local/bin and the config file to /etc/rustfs, then set ownership to the rustfs user and group. If ownership or permissions are wrong, RustFS may fail to start or be unable to read its settings. source
- Running RustFS on Unraid Run the container as uid/gid 99:100 so it can write to a nobody:users share (the image's built-in uid 10001 fails at startup with 'Permission denied'), and set the access key and secret as required — otherwise RustFS falls back to a built-in default account. source
Fetched 37 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Which folder should I back up?
Map and back up the /data folder, because that is the folder that actually holds RustFS data.
Which port should I expose for S3 clients?
Expose port 9000, which is where you connect to RustFS to store and fetch files.
Why might a binary install fail to start because of permissions?
Copy the rustfs program to /usr/local/bin and the config file to /etc/rustfs, then set ownership to the rustfs user and group. Wrong ownership or permissions can prevent RustFS from starting or reading its settings.
What does the Access key setting do in the RustFS app?
It acts more like the admin user and is used for the initial UI login.
Can I migrate from MinIO or run RustFS alongside another S3-compatible store?
RustFS supports migration and coexistence with other S3-compatible platforms such as MinIO and Ceph.
Answers sourced from forums.truenas.com, github.com, github.com, github.com
Community
- Reddit (reddit)
- RustFS | Cloudron Forum (forum)
- Rustfs "Access key" confgiuration box - forums.truenas.com (forum)
Collected 54 days ago - public community threads