SeaweedFS: Open Source alternative to Amazon S3 in 2026
SeaweedFS is a distributed file system optimized to serve billions of small files quickly, with an included S3 compatibility layer.
βΉοΈ chrislusf/seaweedfs hasn't published a new version tag on Docker Hub since 3.99 (October 2025) β recent registry activity is only cosign signatures, not new consumable releases. 3.99 is the latest real version you can pin to today.
Audit Snapshot
View notes βLicense β Matches GitHub
GitHub β Active
Latest release β 4.48 Β· 14 days ago
Docker Compose β Partial
Production β Not production-tested by AltFreeStack
SeaweedFS vs. Amazon S3
Pros
- Excellent performance with massive volumes of small files
Things to consider
- Less polished documentation than MinIO to get started
- No new version tags since 3.99 on Docker Hub (see note above)
Quick Docker installation guide
Copy this docker-compose.yml, adjust the example passwords and run docker compose up -d on your server. See the full step-by-step guide β
π‘ Official SaaS or self-hosted with AltFreeStack?
- On the official cloud: a recurring monthly fee and usage limits on Amazon S3.
- On your own VPS: 100% free software on your own server, with no artificial row, project or user limits.
version: "3.9"
services:
seaweedfs:
image: chrislusf/seaweedfs:3.99
restart: unless-stopped
ports:
- "9333:9333"
- "8888:8888"
- "8333:8333"
command: server -s3
volumes:
- seaweedfs_data:/data
volumes:
seaweedfs_data:
π Deploy in 1 command
Recommended for beginnersCopy this single command and paste it into your freshly created VPS's console (Vultr, DigitalOcean...). It downloads the script, prints it to your screen so you can see exactly what it's about to do (never a blind direct pipe), and only then installs Docker if needed, writes the files with secrets already generated, and starts everything β no nano, no pasting code blocks.
curl -sSL ".../api/deploy?stack=seaweedfs" -o deploy.sh && cat deploy.sh && bash deploy.shThis docker-compose corresponds to an actively maintained project β last commit today.
This docker-compose not working for you? Report it on GitHub βTechnical profile
- License
- Apache-2.0
- Category
- Storage
- Replaces
- Amazon S3
- Tech stack
- Go
Under the hood
Database
None / Object storage
Language
Go
Platforms
Web
Key features
- Optimized for small files at scale
- Included S3 compatibility layer
- Configurable replication and erasure coding
Preview
Public image provided by SeaweedFS on its own website.
πΎ Backups in 3 steps (Day 2)
As long as the ./data folder (the "volume" mapped into the container) exists on your server, your data survives any restart or container update β that's the only thing you need to back up.
1. Create a compressed backup on the server
tar -czvf backup-$(date +%F).tar.gz ./data2. Download it to your computer
From your computer's terminal (not your server's):
scp root@YOUR_IP:~/app/backup-*.tar.gz ./3. Restore in case of emergency
tar -xzvf backup-file.tar.gzπ Connect your domain with free SSL
Step 1 β Set up the DNS
In your domain registrar's dashboard (Cloudflare, Namecheap, GoDaddy...), create a record:
- Type
- A
- Name/Host
- @ (root domain) or a subdomain, e.g. app
- Content/Value
- Your server's public IP
Wait 5 to 15 minutes for the record to propagate across the internet.
Step 2 β Automatic reverse proxy with Caddy
One single file, no Nginx config or manual certificates β Caddy issues and renews Let's Encrypt HTTPS on its own.
Create a file called Caddyfile:
yourdomain.com {
reverse_proxy localhost:9333
}Start Caddy with this command (pulls the image and runs it in the background):
docker run -d -p 80:80 -p 443:443 --name caddy --restart always -v $PWD/Caddyfile:/etc/caddy/Caddyfile -v caddy_data:/data caddy