Restarts that tell the truth
A restart is verified in two stages — the container came back, then the game itself
answered. Per-game startup times, a cooldown that stops restart-hammering, and an
activity feed everyone can read.
Deploys that prove themselves
Before anything is created, a preflight holds your settings to the game's own rules. After
it starts, the first boot is followed until the game answers as the name you gave
it — verified, unconfirmed or failed, never a shrug. Slow downloads keep their
patience; crash loops are called what they are.
Tournaments, end to endbeta
Single or double elimination and round robin, for any game. Teams, seeding, check-in,
captain-reported results, and a shareable public page per tournament. For Counter-Strike 2 the
portal builds a server per match and retires it when the result is in.
Any server Steam carries
Deploy from Unraid's Community Applications, or pick any of ~580 dedicated servers on Steam
— GameKeepr composes the container itself on Valve's official steamcmd image, with the start
command from Steam's own app info, shown before anything exists.
It tells you when to restart
Every six hours GameKeepr compares each server's installed Steam build against what Steam
ships now — read from the server's own install receipt, whatever image built it. A newer build
means a badge on the card and, if you like, a message in Discord. On these servers a restart
is the update.
Schedules with manners
Nightly restarts that ask the game if anyone is playing first, never turn a deliberately
stopped server back on, and skip missed runs instead of firing them late.
Backups of what matters
The world and its settings — not the reinstallable gigabytes. Restores only while stopped,
always preceded by a safety copy, applied as an overlay.
Mods, checked honestly
Repository installs with hash verification, archive-safety judging and optional malware
scanning; Steam Workshop declarations for the games that fetch their own. No report ever says
"safe" — it says what was checked.
Three roles, per-server exceptions
Members restart, operators run servers, the owner runs the platform. Any user can be made
operator of one server, member on another, or shown nothing at all — hidden means hidden.
Run it
mkdir gamekeepr && cd gamekeepr
curl -LO https://raw.githubusercontent.com/KenGoossens/Gamekeep/main/docker-compose.yml
curl -Lo .env https://raw.githubusercontent.com/KenGoossens/Gamekeep/main/.env.example
# edit .env: PUBLIC_URL, SESSION_SECRET, TZ
docker compose up -d
On Unraid it is one search away: Apps → “GameKeepr” → Install —
GameKeepr is in Community Applications.
First boot prints a one-time setup token in the container log; open the portal and create the
owner account with it. The
setup guide walks through the rest — including the one honest
warning: the portal holds the Docker socket, and the
security model explains what that means and what is done
about it.