The best open-source game server panel was released in 2015. Its developers have moved on. Its community maintains it through forks and fragile extensions. Every hosting provider you know is running some private variant of it, held together with duct tape and hope.

The Game Panel is a ground-up replacement, built on the Engine layer, a bespoke PHP framework with no dependency on any existing web framework. The Engine layer and the core modules live together in a single project, built by FrankenPHP into one binary that runs in worker mode with Caddy underneath and points at a PostgreSQL database. It is Wings-compatible from day one – your existing nodes, eggs (v1 and v2), and infrastructure stay exactly where they are.

Key Features

Modular architecture – core features (Files, Backups, Schedules, Databases) are built as first-class modules using the same extension points available to third parties; modules own their own migrations and cannot break the core schema
Granular RBAC – hierarchical, dot-delimited permissions with wildcard support at any level, across three structurally separate contexts: platform (admin), account (client), and server; roles are composable and assignable per-server per-user
Server-rendered frontend – HTML with hypermedia interactions rather than a client-side SPA; each of the three contexts exposes its own API alongside it
Advanced token system – a single tokens table covers both session and API tokens, distinguished by prefix; API tokens carry independently nullable permission and server-scope columns; refresh token rotation with theft detection
Three-context API – Account, Platform, and Server contexts are structurally separate with their own auth guards and routing; mixing token types fails before a database query is made
Single-binary distribution – one binary from your package manager, running as a service; no PHP-FPM to tune, no webserver to configure, no queue worker to daemonise, and no cron entry to forget
Wings compatibility – daemon integration is abstracted to support alternative Wings-compatible daemons in the future without architectural changes

Possible Post-Launch

Egg Registry – a community registry for browsing, versioning, and importing eggs directly into the panel
Minecraft Suite Module – plugin management, version switching, modpack deployment, world management
Billing Module – WHMCS, Blesta, and Stripe integration with automated provisioning
Subdomain Management – Cloudflare DNS integration per server
Reverse Proxy Management – NGINX and Let's Encrypt automation per server
Theming and Branding – hosting provider white-labelling of the Account Panel