seaweedfs / seaweedfs

# SeaweedFS
SeaweedFS is a simple and highly scalable distributed file system. There are two objectives:
1. to store billions of files!
2. to serve the files fast!
One `weed` binary serves an S3 object store, a POSIX file system, and a lakehouse with S3 Tables, all over the same data. Each blob is one disk read away, capacity grows by starting another volume server, and cloud storage can be cached or tiered transparently. Both read and write operations have O(1) complexity and can run at the full speed supported by the underlying hardware.
- Download Binaries for different platforms
- Wiki Documentation
- HTTP REST API for the filer, master, and volume servers
- Community: Slack, Twitter, Telegram, Reddit, Mailing List
- SeaweedFS White Paper and introduction slides: 2025.5, 2021.5, 2019.3
Table of Contents
=================
* Quick Start
 * One command
 * Docker
 * Docker Compose
 * Kubernetes with Helm
 * Build from source
 * Scale out
* Why SeaweedFS
 * Fast
 * Scalable
 * The most complete S3 API
 * A data warehouse with S3 Tables
 * A fast cache for cloud storage
 * Active-active replication and more
* Architecture
* Compared to Other Systems
 * Compared to HDFS
 * Compared to GlusterFS, Ceph
 * Compared to MooseFS
 * Compared to Ceph
 * Compared to MinIO, RustFS
* Benchmark
* Enterprise
* License
* Sponsors
# Quick Start #
## One command ##
Download the latest binary from the releases page and unzip the single `weed` (or `weed.exe`) file, or let the install script put it in `/usr/local/bin`:
 [code] 
Then start a ready-to-use S3 object store:
 [code] 
That's it. The S3 endpoint is at http://localhost:8333, `my-bucket` exists, and `admin`/`secret` are valid credentials:
 [code] 
The same process also runs the master, a volume server, the filer, WebDAV, the Iceberg REST catalog, and the Admin UI. Add `S3_TABLE_BUCKET=warehouse` to also create an Iceberg table bucket, or `warehouse:LANCE` for a Lance one. Drop the AWS keys to run without authentication for development.
Without Admin authentication or mTLS, `weed mini` binds the Admin UI/API and its worker gRPC control plane to loopback rather than `-ip.bind`. Set `WEED_ADMIN_PASSWORD` or configure `https.admin` mTLS to keep the network bind. Remote workers must opt in with `-admin.worker.ip= ` and should configure `grpc.admin` mTLS. `-admin.allowInsecureBind` restores the legacy unauthenticated network bind and should only be used on an isolated network.
> macOS: if the binary is quarantined, run `xattr -d com.apple.quarantine ./weed` first.
`weed mini` is auto-tuned for one node and is fine for single-node production, such as an S3 gateway that issues presigned URLs. See [Quick Start with weed mini][WeedMini].
## Docker ##
 [code] 
Same behavior as the `weed mini` command above.
## Docker Compose ##
To run master, volume server, filer, S3, and WebDAV as separate services:
 [code] 
[Docker Compose for S3][DockerComposeS3] adds credentials, and the docker/compose folder has variants for replica