# wolveix/satisfactory-server

A Dockerized version of the Satisfactory dedicated server

Repository: https://github.com/wolveix/satisfactory-server
Canonical: https://ross.abutalabs.com/products/satisfactory-server
Homepage: https://hub.docker.com/r/wolveix/satisfactory-server
Language: Shell
License: MIT
License Family: permissive
Last push: 2026-07-11T15:16:15+00:00

## Health v2 (maintenance only)
Score: 78/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 92, release rhythm 48, longevity 100
- inputs: {"age_days": 1968, "days_push": 53, "days_rel": 351, "gap_med": 1, "n_releases_24m": 24}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2055, forks 185 (observed 2026-08-28T04:06:09.855232+00:00)

## What it is
A Dockerized wrapper around the Satisfactory dedicated server that packages the game server, SteamCMD updates, and save/backup handling into a single container image. It exposes environment variables for player limits, memory limits, and Steam beta branches so the server can be run with a single docker run command.

## Use cases
- host a satisfactory dedicated server in docker
- run a satisfactory server on my home linux box
- self host a multiplayer factory game server
- docker image for satisfactory dedicated server
- automatically backup satisfactory saves
- run satisfactory server with steamcmd auto updates
- host a game server for friends without installing steam

## When to choose
- you want a one-command, containerized Satisfactory server with persistent config, saves, and automatic backups
- you run a headless Linux host or NAS and prefer Docker over installing Steam and managing the server manually
- you want easy control over max players, memory limits, and beta branch via environment variables

## When to avoid
- you need a dedicated server for a different game - this image is Satisfactory-specific
- you cannot run Docker or don't want container overhead on the host machine
- your host has very limited RAM, since the game server realistically needs 8-16GB for late-game saves or 4+ players

## Facets
- artifact type: application
- maturity: active
- function: container-runtime, deployment, self-hosted, developer-tools
- domain: gaming-tools, self-hosted
- platform: self-hosted, cross-platform
- tags: game-server, satisfactory, docker-image, dedicated-server, steamcmd, shell-scripting, save-backups, multiplayer, containers, automation, docker, linux

## Member repositories
- wolveix/satisfactory-server (main) score 78

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:06:09.855232+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T02:57:17.525525+00:00, confidence not recorded.
  - readme: https://github.com/wolveix/satisfactory-server (fetched 2026-08-28T04:06:09.855232+00:00, sha fea438e6673c)
  - homepage: https://hub.docker.com/r/wolveix/satisfactory-server (fetched 2026-08-29T10:37:36.012574+00:00, sha d3b86f15c5d8)
  - site_page: https://www.docker.com/docs (fetched 2026-08-29T10:37:36.023546+00:00, sha aeada2272712)
  - site_page: https://docs.docker.com/docker-hub (fetched 2026-08-29T10:37:36.021839+00:00, sha caaa18892709)
  - site_page: https://www.docker.com/company (fetched 2026-08-29T10:37:36.025145+00:00, sha 05ab59b2bc29)
- Data as of 2026-08-30T08:39:29.467469+00:00.