FileBrowser
Upload, organize, and share files from a clean web UI - a 30 MB Go binary with share links and user scopes.
One-click deploy, from $5/mo on a Miget plan.
Sometimes the requirement is exactly this small: a place to put files, a UI to browse them, and a link to share one. FileBrowser is that tool with no ceremony - a single Apache-2.0 Go binary with previews, an editor, per-user scopes, and public share links, running non-root with a built-in healthcheck.
This template is the catalogue’s simplest stateful deploy: one container, a files volume, an admin login from env. Released near-daily upstream and small enough that the $5 plan carries it with room to spare.
Scope honesty: it shares and serves files, it does not host websites (Miget’s native static hosting does that) and it is volume-backed by design - the S3-backed manager lane belongs to Filestash.
Upstream project: FileBrowser
#what you get
- Browse, upload, preview, edit - fast and keyboard-friendly
- Public share links with optional expiry
- Per-user accounts with scoped directories
- Non-root container, built-in healthcheck, ~30 MB
- Deterministic admin bootstrap from env
- Apache-2.0, very actively maintained
#topology
| Service | Role | Public |
|---|---|---|
| filebrowser | web UI + share links (:5000) | yes |
#miget sizing
// this stack needs
256 MiB RAM · 9 GB disk · 1 service
The binary idles around 30 MB; the files volume is the only real resource. Resize it as the library grows.
Hobby - recommended fit
$5/mo
1 vCPU · 512 MiB · 10 GiB disk
Headroom for your own apps: 1 GiB at $7/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 (256 MiB RAM, 9 GB disk, 1 container) elsewhere, from published June 2026 rates.
| Platform | Est. monthly | Notes |
|---|---|---|
| Miget ★ | $5 flat | compose stacks first-class: one deploy, dedicated vCPU, managed Postgres/Valkey, volumes and TLS all included in the plan |
| Heroku | ~$13 | no volumes; nothing between 1 GB ($50) and 2.5 GB ($250) dynos - 2 GB containers cost far more than shown |
| DO App Platform | ~$10 | no persistent volumes - stateful containers need managed DBs/Spaces (base $5 Spaces included here) |
| Render | ~$9 | per-service instances (0.5 GB $7, 2 GB $25) - every container is its own paid service |
| Railway | ~$4 | usage-based ($10/GB RAM-mo); vCPU billed separately at $20/vCPU-mo on top |
| Fly.io | ~$3 | 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
filebrowser -
Set the required variable:
FB_USERNAME / FB_PASSWORD, admin login
- 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/filebrowser
docker compose up -dSame files, same behavior. The template README covers connection strings and scaling notes.
#faq
FileBrowser or Filestash - which one?
FileBrowser for volume-backed personal/team file sharing with the least setup. Filestash when the backend should be S3 (Miget Buckets). For serving a whole website, use Miget’s native static hosting. Different jobs, different tools.
Can people without accounts receive files?
Yes - share links are public URLs (optionally time-limited) served from your domain. For inbound uploads from outsiders, SFTPGo’s share-upload links are the stronger tool.
Is it safe to expose?
It sits behind its own auth over the platform’s TLS, runs non-root, and has no system access beyond its volumes. Use a strong admin password and scoped users for anything shared.
Ship FileBrowser today
One compose stack, 256 MiB of RAM, from $5/month flat, and it runs on your laptop with the same files.