If you are following along with our Build your own homelab series, we have two separate tutorials to get a Minecraft server up and running. The first is a dedicated Minecraft server via Crafty Controller (running in an LXC container in our Proxmox instance). The second was with Turnkey Linux's Gameserver, which can run a lot more than just a Minecraft server - it provides a catalog of LinuxGSM-supported game servers. Although Crafty Controller offers us an interface we can use, it is only for Minecraft. TurnKey offers other games through its appliance and LinuxGSM tools. Pterodactyl adds a dedicated multi-game browser panel with user permissions and interactive server consoles. So today we look at a new solution called Pterodactyl (https://pterodactyl.io) that we can use that can offer us both.
What Is Pterodactyl?
Pterodactyl is a web-based control panel that lets you manage game servers through a visual interface. Think of it like the dashboard of a car - it lets you control and monitor everything without entering every routine server-management command manually. Installing and maintaining the host still requires Linux administration. It is a free and open-source game server management panel that makes it easy to create and manage game servers on your own hardware. Whether you're a hobbyist or running a community, Pterodactyl helps you do it in a clean, secure, and user-friendly way.
With Pterodactyl, you can:
- Create and delete game servers.
- Assign users to manage servers.
- View server stats and logs.
- Start, stop, and restart servers easily.
And the best part? It supports dozens of games, from Minecraft and Counter-Strike 2 (CS2) to ARK and Valheim.
How Does Pterodactyl Work?
Pterodactyl is made up of two main components:
- Pterodactyl Panel – This is the web-based interface where you manage your servers.
- Pterodactyl Wings – This is the backend daemon that actually runs the game servers on your machine.
They work together like this:
- You log into the Panel to create a server.
- The Panel tells Wings to start that server on your machine.
- Wings handles all the behind-the-scenes work—starting the server, managing resources, and applying the configured container boundaries and resource limits.
Everything is built using modern web technologies and Docker containers, so each game server runs in its own container. Containers share the host kernel; their isolation does not make a compromised game or an outdated host harmless.
Key Features of Pterodactyl
Here are some of the main reasons people use Pterodactyl:
- Free and Open-Source – The Pterodactyl software is free and open source under the MIT license. Hardware, electricity, storage, connectivity and any game-specific requirements still cost time or money.
- Web-Based Interface – Manage servers from any browser.
- Multi-User Support – Give access to friends or staff with specific permissions.
- Docker-Based Isolation – Separates server processes and resources, subject to the host and container configuration.
- Built-in SFTP Access – Upload and manage files securely.
- Easy Game Server Support – Tons of game server "eggs" ready to go.
- Security First – Includes permission and isolation features; updates, appropriate access and recoverable backups remain the administrator’s responsibility.
What Is Pterodactyl Wings?
Pterodactyl Wings is the "engine" that powers everything behind the scenes. While the Panel handles the pretty interface, Wings does the heavy lifting by:
- Running the game servers.
- Monitoring resource usage (CPU, memory, disk).
- Handling commands from the Panel (start, stop, restart).
- Managing networking and file systems securely.
Wings is installed on each node (machine) that will host game servers.
So, if you're hosting servers on your own PC or a VPS (Virtual Private Server), you install Wings there. It connects securely to your Panel to receive instructions.
How Do Wings and the Panel Work Together?
To make it super simple:
- Pterodactyl Panel is the control center.
- Pterodactyl Wings is the worker.
The Panel sends commands. Wings does the work.
You can even install Wings on multiple machines, and manage them all from a single Panel. This is great for communities that want to split servers across different locations or systems.
Use Cases for Pterodactyl
Here are a few ways Pterodactyl is used:
- Gamers – Easily host Minecraft or other servers for friends.
- Server Hosts – Manage many servers for paying customers.
- Community Admins – Let moderators access certain servers or features.
- Developers – Quickly spin up testing environments for custom game mods.
It works on dedicated servers, cloud VPS instances, or even a powerful home computer.
Installing Pterodactyl
Installing Pterodactyl is quite an extensive task, especially seeing as one needs to install both Pterodactyl Panel and Pterodactyl Wings. We will be installing both as part of our Build your own homelab series, running them inside our Proxmox installation and exposing the server to the world wide web so our friends can join. Going into detail to get these two services up and running is outside of the scope of this article as the article would take forever to read, but if you prefer to get it up and running by yourself, feel free to follow the install instructions:
Pterodactyl Panel - https://pterodactyl.io/panel/1.0/getting_started.html
Pterodactyl Wings - https://pterodactyl.io/wings/1.0/installing.html
Conclusion
Pterodactyl is a powerful yet beginner-friendly way to manage your own game servers. With its sleek Panel and robust Wings system, you can control multiple game servers with ease—whether you're a casual gamer or running a full-blown hosting business.
To recap:
- Pterodactyl Panel is your control dashboard.
- Pterodactyl Wings runs the game servers.
- Together, they provide a consistent interface for several servers, with configuration and maintenance responsibilities that grow with the deployment.
If you're tired of paying monthly fees or just want to have more control over your game hosting, give Pterodactyl a try!
Nodes, Allocations and Eggs
A node is the Linux machine running Wings and Docker. It can be physical hardware or a suitably configured VM. The Panel may run on the same machine or elsewhere; one Panel can manage several nodes. The Panel's web dependencies and Wings' container requirements are separate, so installing only the website does not create a working game-server host.
An allocation identifies a node address and port that a server can use. A game's actual requirements decide which ports and protocols need to be reachable. Some games need additional query or management allocations. Opening the Panel's HTTPS port alone does not make a game reachable: players connect to the game service on its assigned ports, not through the Panel's login page.
An egg describes a server type: its container image, startup command, installation procedure and configuration handling. In Pterodactyl 1.x, nests group eggs. The 2.0 prerelease documentation uses tags in place of nests, so follow the documentation for the version you actually install instead of mixing the two administration models.
The existing Pelican / Pterodactyl Eggs repository is an archived collection. Keep it as a historical reference, and consult the current Pterodactyl egg directory for maintained options. An egg is not a game license or a guarantee of compatibility with every mod and update. Read its image, install script and required variables before importing it.
Planning a First Node
For the stable 1.x Panel, the current instructions list PHP with specific extensions, a supported MySQL or MariaDB database, Redis, Composer and a web server. Wings needs Linux with the kernel facilities required to run Docker. Its documentation does not support a native Windows deployment. Check the dependencies and Panel/Wings compatibility before choosing a host image.
In a Proxmox homelab, a Linux VM is a straightforward place to evaluate Wings' requirements. Running Docker inside LXC depends on the container configuration and available kernel facilities. The Panel and Wings pages contain different levels of caution about LXC, so confirm your actual environment rather than treating an existing Crafty LXC guide as proof that every Wings setup will work the same way.
Start with one expendable server and one trusted test user. Allocate enough memory and disk for the game's requirements, leaving capacity for the operating system, Panel services and backups. A container memory limit caps consumption; it does not make the host capable of running all servers at their maximum simultaneously. Game performance may depend strongly on CPU behavior and player activity, so measure the actual workload before adding more worlds.
Set permissions around what a friend needs to do. Someone who should restart a game does not necessarily need to delete backups, reinstall the server or change every file. Use separate accounts and check the available subuser permissions rather than sharing the administrator password. Preserve a way to access the underlying host when the Panel itself is unavailable.
Networking and Recovery
Plan three distinct routes: browser access to the Panel, management/console and SFTP access to Wings, and player access to each game. The browser also connects directly to the node for console and file operations. Reachable node names, suitable certificates and reverse-proxy settings matter; an HTTPS Panel paired with an unreachable or incorrectly secured Wings endpoint can still leave the console broken.
Publishing a game port is different from exposing every management endpoint. Open only the game's required allocations to the intended players, and keep administrative access appropriately restricted. Home routers, double NAT and CGNAT can affect outside access. Test from outside the home network as well as from a local device before blaming the egg or game software.
Back up game data and also the Panel's database and application configuration. Keep the application encryption key with the recovery materials: restoring files without the associated key can break encrypted settings. Store an independent copy outside the game node and test restoring a small world before important progress depends on it.
When upgrading, read both Panel and Wings release notes and the required version relationship. Schedule downtime, preserve data and confirm the game, console, SFTP and backup paths afterward. Do not assume that a green container status proves players can join or that saved worlds are recoverable.
Choosing a Management Style
| Option | Useful fit | Decision to check |
|---|---|---|
| Pterodactyl | Multi-game browser management with per-server permissions and Wings nodes | Panel dependencies, Docker-capable Linux nodes and maintained eggs |
| Crafty Controller | A Minecraft-focused browser interface, including Java and Bedrock | Whether Minecraft-focused management meets your needs |
| LinuxGSM / TurnKey GameServer | Linux game-server administration with a different appliance and command-line workflow | The selected game and the administration approach you prefer |
| CubeCoders AMP | A commercial multi-game management product | Current supported games, host platforms and license terms |
Pelican is a separate project that began as a Pterodactyl fork. Its publisher lists the Panel under AGPLv3 rather than Pterodactyl's MIT license, and it has its own development and compatibility guidance. Shared ancestry and eggs should not be read as an assurance that every addon or future release is interchangeable. Compare the actual projects before planning a migration.
Pterodactyl remains an appealing route for the friend-group and community use described here. Its friendly day-to-day interface does not remove the work of operating the server underneath. Begin with the current stable Panel instructions and current Wings instructions; the older links above remain as part of this article's original references.
