Your game servers, your machines, one panel.

How it fits together

Nodes dial out. Nothing dials in.

NGCP has two parts. The panel serves the web interface and the REST API and keeps everything in PostgreSQL. A small agent on each game-server machine opens a mutual-TLS connection out to the panel.

• Nodes can sit behind NAT. There is no inbound management port to open.
• Windows and Linux nodes are both first-class.
• Game servers run as native processes. No Docker needed.
• Restart the panel whenever you like: game servers keep running and the agents reconnect by themselves.

Read the concepts

Games

Four games ship with it. Yours is a YAML file away.

• ArmA 3Headless clients, Steam Workshop mods with the -mod line built for you, BattlEye RCON.
• Counter-Strike 2SteamCMD installs and updates, Source RCON.
• Minecraft JavaPaper server and its Java runtime, downloaded for you, Minecraft RCON.
• ValheimAnonymous SteamCMD install, player counts from the game's status query.

Shipped games and what is tested

A game definition is one YAML file: install steps, ports, startup variables, config forms, the console and status query, and what to back up.

install:
  linux:
    - {type: steamcmd, name: Valheim server, app_id: 896660, login: anonymous, validate: true}

ports:
  - {role: game, proto: udp, default: 2456, offset: 0}
  - {role: query, proto: udp, default: 2457, offset: 1}

variables:
  - {key: server_name, label: Server name, type: string, default: "My Valheim Server", user_editable: true}
  - {key: password, label: "Password (5+ characters, not part of the name)", type: password, generate: true}

processes:
  - role: main
    linux: {exe: valheim_server.x86_64}
    ready_regex: "Game server connected"

query: {type: a2s, port: "{port.query}"}
backup:
  include: ["saves/**"]