Deploy Static Bucket Server + GUI
Allow public GET on your buckets + and private file management.
static
Just deployed
Deploy and Host Static Bucket Server + GUI on Railway
An S3-compatible bucket file server with a password-protected web GUI for uploading, downloading, deleting, and managing files across multiple buckets. Includes a public file proxy, rate limiting, and friendly bucket name mapping.
About Hosting Static Bucket Server + GUI
Hosting the Static Bucket Server + GUI involves running a Node.js/Bun Express application that connects to an external S3-compatible storage provider. The server handles authentication, session management, and rate limiting in-memory by default, with optional Redis support for distributed deployments. Railway provides the compute environment, while your S3-compatible provider (Railway, AWS S3, MinIO, DigitalOcean Spaces, etc.) stores the actual files. Configuration is done entirely through environment variables, making Railway's variable management a natural fit.
Common Use Cases
- Hosting a self-service file management portal for teams that need to upload and organize assets in S3 buckets
- Serving public static files (images, documents, media) via a CDN-friendly proxy with 1-year cache headers
- Providing a simple, password-protected UI for non-technical users to manage files without direct S3 console access
Dependencies for Static Bucket Server + GUI Hosting
- An S3-compatible storage provider (AWS S3, MinIO, DigitalOcean Spaces, Cloudflare R2, etc.)
- Redis (optional, for distributed rate limiting across multiple instances)
Deployment Dependencies
- Configure a Railway bucket service or a bucket on another platform.
- Optional Redis service can be used (recommended if creating replicas to help manage cross-replica rate-limits)
Why Deploy Static Bucket Server + GUI 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 Static Bucket Server + GUI 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.
Template Content
static
signalor/staticREGION
Region where the bucket is stored.
ENDPOINT
The S3-compatible endpoint that the bucket is served at.
BUCKET_NAMES
The names of the buckets you want to server/access. Separate by comma like "bucket1,bucket2"
ACCESS_KEY_ID
Access Key ID for the bucket.
PRIVATE_TOKEN
Password to gain access to the GUI. Should be >32 characters long.
SECRET_ACCESS_KEY
Secret Access Key for the bucket