Getting started
The panel runs on your own servers: one machine for the panel itself (Master) and any number of nodes where game servers run in Docker containers. This guide is the short path from an empty server to the first game server for a customer.
The path
- Check the requirements below.
- Install the panel with the command from Downloads.
- Sign in for the first time: create the administrator and activate a license or a 10-day trial.
- Connect a node with the one-line command the panel shows.
- Create your first game server: a game from the catalog, a plan, a server — the Panel setup checklist on the panel's Overview page walks you through it as well.
- Save backups of the installation and plan updates.
Something went wrong — see Troubleshooting or open a ticket in Support.
Requirements
Panel server
- Linux x86_64 or arm64 with Docker Engine and the
docker composeplugin. On Debian/Ubuntu the installer installs them itself; on other distributions install them first. - 2 CPU cores, 2 GB RAM and 20 GB of disk are enough to start.
- A domain (for example
panel.example.com) whose A/AAAA record points to this server. - Incoming ports: 80/tcp (Let's Encrypt and the redirect to HTTPS), 443/tcp (the panel), 4222/tcp (nodes connect here, mutual TLS).
- Root access and outbound HTTPS to this portal (license renewal).
Nodes
- Any Linux with systemd and Docker. On Debian/Ubuntu the node installer installs Docker and OpenSSH itself.
- Incoming 22/tcp (SFTP for your customers) and the ports your games use.
- Outbound access to the panel:
https://<panel domain>and port 4222. The panel never connects to a node, so nodes can sit behind NAT.
Optional
- S3-compatible storage for backups and add-on files (AWS S3, MinIO, Backblaze B2…). The panel can also run a built-in MinIO.