Factorio Server
A headless Factorio server - the factory grows while everyone sleeps, for $13/month.
One-click deploy, from $13/mo on a Miget plan.
Factorio multiplayer deserves a server that never sleeps with someone’s laptop. The community-standard image runs the official headless server: a map generates on first boot, the latest save loads ever after, autosaves roll on the volume, and mods can update themselves on restart.
It is one of the lightest game servers there is - 2 GB of RAM carries factories far past the point where the real bottleneck is your friends’ ability to agree on bus layouts. $13/month flat, no slot pricing.
Factorio speaks UDP: after deploy, add a public custom UDP port to the app and share host:port. Server name, password, and admins live in server-settings.json on the volume.
Upstream project: factoriotools/factorio
#what you get
- Official headless server via the community-standard image
- Auto map generation, latest-save loading, rolling autosaves
- Mods on the volume with optional auto-update on start
- Server settings as a JSON you actually control
- One UDP port, 2 GiB RAM - the lightest game server here
- Version pinning via image tags (stable/experimental)
#topology
| Service | Role | Public |
|---|---|---|
| factorio | headless server (UDP :34197) | via custom public UDP port |
#miget sizing
// this stack needs
2 GiB RAM · 5 GB disk · 1 service
2 GiB handles large factories; UPS (the game’s tick rate) is CPU-bound at megabase scale - the next plan buys cores, not just memory.
Hobby - recommended fit
$13/mo
1 vCPU · 2 GiB · 50 GiB disk
Headroom for your own apps: 2 GiB at $19/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 (2 GiB RAM, 5 GB disk, 1 container) elsewhere, from published June 2026 rates.
| Platform | Est. monthly | Notes |
|---|---|---|
| Miget ★ | $13 flat | compose stacks first-class: one deploy, dedicated vCPU, managed Postgres/Valkey, volumes and TLS all included in the plan |
| Heroku | ~$100 | no volumes; nothing between 1 GB ($50) and 2.5 GB ($250) dynos - 2 GB containers cost far more than shown |
| DO App Platform | ~$29 | no persistent volumes - stateful containers need managed DBs/Spaces (base $5 Spaces included here) |
| Render | ~$26 | per-service instances (0.5 GB $7, 2 GB $25) - every container is its own paid service |
| Railway | ~$21 | usage-based ($10/GB RAM-mo); vCPU billed separately at $20/vCPU-mo on top |
| Fly.io | ~$13 | 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
factorio - No required variables - deploy as-is
- 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/factorio
docker compose up -dSame files, same behavior. The template README covers connection strings and scaling notes.
#faq
How do players connect?
Add a custom public UDP port on the app (internal 34197) and share host:port - players use "Connect to address". For the in-game public server browser, set visibility and your factorio.com token in server-settings.json.
How do saves and mods work across redeploys?
Everything lives on the /factorio volume: saves, mods, settings. Redeploys load the latest autosave; UPDATE_MODS_ON_START=true keeps mods current with the server version.
Why is this cheaper than the Minecraft template?
No JVM: Factorio’s headless server is lean native code. 2 GiB and one UDP port is genuinely the whole footprint until your factory reaches megabase scale - at which point the upgrade is CPU, and you will know.
Ship Factorio Server today
One compose stack, 2 GiB of RAM, from $13/month flat, and it runs on your laptop with the same files.