Filestash
A polished web file manager over Miget Buckets - browse, preview, and share what lives in S3.
One-click deploy, from $7/mo on a Miget plan.
Buckets are where files live; Filestash is how humans use them: a fast web manager with previews (images, video, office documents), editing, and share links - over any S3-compatible backend, with path-style addressing always forced so Miget Buckets just work.
The admin console pre-configures the connection (endpoint + keys, optionally pre-filled) so users land directly in the bucket. AGPL, very actively maintained, and famously light - the docs quote 128 MB.
It completes a three-tool storage lane with distinct jobs: filebrowser (volume-backed simplicity), filestash (the bucket UI), sftpgo (the upload portal).
Upstream project: Filestash
#what you get
- S3-compatible backends with forced path-style - buckets just work
- Previews: images, video, PDFs, office docs; in-browser editing
- Share links with password, expiry, and domain restriction
- Admin-preconfigured connections - users land in the bucket
- Pluggable auth (htpasswd/LDAP/OIDC) when you need it
- ~128 MB, AGPL, shipped weekly
#topology
| Service | Role | Public |
|---|---|---|
| filestash | file manager (:8334, no port env) | no |
| web | nginx :5000 -> filestash:8334 | yes |
#miget sizing
// this stack needs
640 MiB RAM · 1 GB disk · 2 services
State is just config (1 GB volume) - the files stay in the bucket. Big uploads stream through the proxy unbuffered.
Hobby - recommended fit
$7/mo
1 vCPU · 1 GiB · 25 GiB disk
Headroom for your own apps: 2 GiB at $13/mo
Professional - production
$22/mo
1 vCPU · 2 GiB · 10 GiB disk
Dedicated resources, production SLOs - plan details
One Miget plan is a fixed pool of compute - the whole stack (managed databases included) deploys inside it, and anything left over runs your other apps. No per-service or per-seat math.
#vs. other PaaS
Estimated monthly cost of running this exact stack (640 MiB RAM, 1 GB disk, 2 containers) elsewhere, from published June 2026 rates.
| Platform | Est. monthly | Notes |
|---|---|---|
| Miget ★ | $7 flat | compose stacks first-class: one deploy, dedicated vCPU, managed Postgres/Valkey, volumes and TLS all included in the plan |
| Heroku | ~$31 | no volumes; nothing between 1 GB ($50) and 2.5 GB ($250) dynos - 2 GB containers cost far more than shown |
| DO App Platform | ~$15 | no persistent volumes - stateful containers need managed DBs/Spaces (base $5 Spaces included here) |
| Render | ~$14 | per-service instances (0.5 GB $7, 2 GB $25) - every container is its own paid service |
| Railway | ~$6 | usage-based ($10/GB RAM-mo); vCPU billed separately at $20/vCPU-mo on top |
| Fly.io | ~$4 | cheapest sticker price - but burstable shared CPUs (1/16 core; dedicated vCPUs cost ~2-3×), no compose deploys (one app per container, manual wiring), managed DBs billed extra |
Estimates assume RAM fully allocated at published on-demand rates - and sticker price isn't the whole comparison: the cheaper rows buy burstable shared CPUs, per-service wiring instead of a compose deploy, and managed databases billed separately. Heroku and DO App Platform have no persistent volumes at all - stateful stacks like this one need workarounds there.
#deploy it
On Miget
- Create a Compose Stack in app.miget.com pointing at the templates repository
- Set the stack path to
filestash -
Set the required variable:
(none), claim /admin on first visit, then configure the S3 connection there
- Deploy. Miget layers
compose.miget.yaml(RAM, privacy, volumes, managed services) automatically
Locally first?
Every template is portable, vanilla Docker Compose - the Miget overrides are ignored locally:
git clone https://github.com/deployable-sh/stacks
cd miget-compose-templates/filestash
docker compose up -dSame files, same behavior. The template README covers connection strings and scaling notes.
#faq
How does this relate to Miget’s own bucket UI?
The platform UI is for operating buckets; Filestash is for the humans who use the files daily - previews, editing, and share links you can hand to a client. Same bucket underneath, different audience.
Filestash, FileBrowser, or SFTPGo?
Filestash when the data lives in buckets and people need a rich UI over it. FileBrowser for the simplest volume-backed sharing. SFTPGo when outsiders must upload into buckets (share-upload links, per-user prefixes, SFTP). All three are $5-7/month.
What is the first-deploy checklist?
Visit /admin immediately (the first visitor sets the admin password), add the S3 connection with your bucket endpoint and keys, and set APPLICATION_URL to your domain. Two minutes, documented in the README.
Ship Filestash today
One compose stack, 640 MiB of RAM, from $7/month flat, and it runs on your laptop with the same files.