GameDash is a control panel for game server hosting. It gives you one place to run game servers across a fleet of machines — provisioning them, starting and stopping them, moving files around, watching resource use — whether those machines run Linux or Windows.
It is built for two kinds of operator: hosting companies selling game servers to customers, and communities running their own infrastructure. The same panel serves both; what changes is how many nodes you point it at.
Most panels support a fixed list of games, and adding one means waiting for the vendor. GameDash treats game support as a plugin problem instead. Every game is a module written against the SDK, and a module is something you can read, fork, or write yourself. If a game runs as a server process on a machine GameDash can reach, a module can run it.
That is also why the platform is host-agnostic. The daemon that runs on each node abstracts the operating system, so a module written once works on Debian, Ubuntu, Red Hat and Windows without knowing which it is running on.
A GameDash installation has a central panel and one or more nodes. The panel holds the database, serves the web interface and the API, and decides what should happen. Each node runs a small agent — the daemon — that carries those decisions out on the host: containers, processes, files, packages.
Architecture walks through the parts and how they talk to each other. If you would rather get something running first, Requirements is the place to start.