SFTPGo
The upload portal for Miget Buckets - per-user S3 storage, share-upload links for outsiders, optional SFTP.
One-click deploy, from $5/mo on a Miget plan.
Every agency and consultancy has the same recurring problem: getting large files FROM clients. SFTPGo solves it elegantly - create a share-upload link (password, expiry, usage caps) and the client uploads straight into a Miget Bucket folder, no account, no WeTransfer.
Underneath is a serious multi-protocol file server: each user’s filesystem can BE an S3 bucket (custom endpoint, forced path-style, per-user key prefix to confine them to a folder), fronted by a web client, and optionally real SFTP over a custom TCP port or WebDAV.
A single AGPL Go binary at ~50 MB, with a proper admin UI and REST API for automation - the smallest template in the catalogue that replaces an entire category of file-exchange SaaS.
Upstream project: SFTPGo
#what you get
- Per-user S3 backends: bucket + endpoint + key prefix per user
- Share links: read AND write (upload) with password/expiry/caps
- Web client for users; admin UI + REST API for you
- Optional SFTP (custom TCP port) and WebDAV fronts
- Env-bootstrapped admin; SQLite state on a small volume
- ~50 MB Go binary, actively maintained, AGPL
#topology
| Service | Role | Public |
|---|---|---|
| sftpgo | web admin + client (:5000); SFTP :2022 project-internal | web yes; SFTP via optional custom TCP port |
#miget sizing
// this stack needs
512 MiB RAM · 6 GB disk · 1 service
The binary is tiny; uploads stream through to the bucket. The home volume only matters for users you deliberately keep volume-backed.
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 (512 MiB RAM, 6 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 | ~$25 | no volumes; nothing between 1 GB ($50) and 2.5 GB ($250) dynos - 2 GB containers cost far more than shown |
| DO App Platform | ~$11 | 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 | ~$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
sftpgo -
Set the required variable:
ADMIN_PASSWORD, admin login at /web/admin
- 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/sftpgo
docker compose up -dSame files, same behavior. The template README covers connection strings and scaling notes.
#faq
How do client uploads work without accounts?
Create a user mapped to a bucket prefix, then issue a write-enabled share link with a password and expiry. The client opens the link in a browser and drops files - they land in your bucket folder, and the link can self-expire after N uses.
Can I offer real SFTP?
Yes - SFTPGo listens on :2022 inside the project; add a public custom TCP port on the app and map it, and classic SFTP clients connect with per-user credentials while reading/writing the same buckets.
How is each user wired to a Miget Bucket?
In the admin UI: filesystem provider "AWS S3 (compatible)", bucket name, the bucket’s S3 endpoint, keys, force-path-style on, and an optional key prefix to confine the user to a subfolder. Scriptable via the REST API for onboarding automation.
Ship SFTPGo today
One compose stack, 512 MiB of RAM, from $5/month flat, and it runs on your laptop with the same files.