Documentation

Using the panel

Once a server exists, most of the day-to-day work is in the client dashboard. Admins also manage nodes, users, eggs, and settings.

Client area

/ lists the servers you can access. The first account on a new panel is admin and can see everything. Later users only see servers they own or were invited to.

A game server

Console — live output and power (start / stop / restart / kill). Websocket through the panel, proxied to the daemon.
Files — browse, edit, upload. Default upload ceiling is 250 MB (configurable).
Databases — database users tied to the server, when a database host is configured.
Schedules — cron jobs (power, command, backup) on the node.
Users — subusers with per-server permissions.
Backups — snapshots stored on the node.
Network — allocations assigned to this server.
Startup — egg variables and the launch command.
Settings — rename, reinstall, delete.

Admin

Locations — geographic or logical groups of nodes
Nodes — daemons, allocations, configuration token
Nests / eggs — how games install and start
Servers — create and assign owners
Users — roles, invites
Settings — branding, SMTP, in-panel updates

Account → Security: change password (minimum 10 characters) and enable TOTP. Account → Sessions lists signed-in sessions. Account → Appearance is theme. Invites use a token URL; optional email verification if SMTP is configured.

Mail and branding

Admin → Settings. Upload a logo (PNG, JPEG, WebP, or GIF, max 2 MB) and set the site name. SMTP can be stored in the database or fall back to SMTP_* in .env. Use StartTLS on 587 unless your provider requires implicit TLS.