Deploy and Host SeaweedFS on Railway

SeaweedFS is a fast distributed storage system for blobs, objects and files. It stores billions of files with constant-time lookups, and exposes an S3-compatible API, a filer with directories, WebDAV and FUSE mounts. It works on one small server and scales out to many volume servers later.

About Hosting SeaweedFS

This template runs the official chrislusf/seaweedfs:4.47 image in weed mini mode: master, volume server, filer, S3 gateway, WebDAV and the admin UI in one service. The S3 API is on the first Railway domain with generated access keys, and the admin UI is on a second domain behind a generated password; anonymous and wrong-key requests get 403. The filer, master and WebDAV ports have no auth and are only reachable on the private network. Data lives on a Railway volume at /data, so objects survive redeploys. It fits the Hobby plan; size the volume for your data. Telemetry is off.

Common Use Cases

An S3-compatible bucket store for app uploads and backups
Replacing MinIO for small and medium object storage
Storing many small files (images, thumbnails, logs) efficiently

Dependencies for SeaweedFS Hosting

chrislusf/seaweedfs:4.47 (official image)
A Railway volume at /data

Deployment Dependencies

Implementation Details

Service	Source	Networking	Storage
seaweedfs	`chrislusf/seaweedfs:4.47`	S3 domain on 8333, admin UI domain on 23646, filer/master/WebDAV private	volume at `/data`

The service has two domains: the one on port 8333 is the S3 endpoint and the one on 23646 is the admin UI (see Settings → Networking).

aws --endpoint-url https:// s3 mb s3://my-bucket
aws --endpoint-url https:// s3 cp file.txt s3://my-bucket/

Variable	Default	Purpose
`AWS_ACCESS_KEY_ID`	generated	S3 access key (admin identity)
`AWS_SECRET_ACCESS_KEY`	generated	S3 secret key
`SEAWEEDFS_ADMIN_USER`	`admin`	Admin UI username
`SEAWEEDFS_ADMIN_PASSWORD`	generated	Admin UI password

Notes:

Use path-style requests and any region name (for example us-east-1).
The bind address is [::] so the private network works over IPv6.

This is a community-maintained deployment package and does not imply affiliation with or endorsement by the SeaweedFS project.

Why Deploy SeaweedFS on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying SeaweedFS on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.