Weave Code
Panel Laravel Package
pterodactyl/panel
Pterodactyl is a free, open-source game server management panel built with Laravel. It isolates servers in Docker containers and provides a secure admin UI, user management, APIs, and scalable control for communities and hosting providers.
Pterodactyl Panel is a free, open-source game server management panel built on Laravel and PHP. It provides a secure, modern web interface for deploying and managing game servers in isolated Docker containers, with support for multiple games and multi-node scaling.
- Docker isolation for secure, reproducible server environments
- Multi-node architecture to scale across machines
- Powerful admin controls for users, servers, and allocations
- REST API for automation and integrations
Frequently asked questions about Panel
- How do I install Pterodactyl Panel with Composer?
- Pterodactyl is distributed as a full Laravel application and a tagged Docker image, not as a library you add to an existing Laravel app with Composer. Use the official new-install guide for the 2.0 beta, which covers dependencies, database setup, queue workers, and scheduled tasks. For production-like deployments, pin the explicit beta tag or image digest such as ghcr.io/pterodactyl/panel:v2.0.0-beta.2 instead of a floating tag.
- What Laravel and PHP versions does Pterodactyl 2.0 require?
- The provided release context does not specify the exact Laravel and PHP version requirements for the 2.0 line, so check the official documentation and the composer.json for the beta tag you pin. Because the panel is a conventional Laravel app, confirm required PHP extensions and database versions against your supported platform matrix. Treat version requirements as potentially moving during the open beta.
- Does exporting an egg in Pterodactyl work for re-import?
- In v2.0.0-beta.2, exporting an egg from the admin area now downloads a file that can be re-imported, fixing a round-trip integrity defect. Eggs exported on earlier betas could look valid and fail only at import time, so treat those artifacts as untrusted until they are re-exported and re-validated on beta.2. Re-export your egg library and import it into a scratch panel as an acceptance test.
- How do I upgrade Pterodactyl from 1.x to 2.0?
- The 1.x to 2.0 upgrade has a separate documented guide and is explicitly flagged upstream to be tested on a copy of the panel first. Copy the database, run the upgrade against the copy, then verify authentication, node and daemon connectivity, server start and stop, and egg import before touching production. Beta-to-beta updates such as beta.1 to beta.2 are lower ceremony and appropriate for a staging pilot.
- Is Pterodactyl 2.0 beta stable enough for production?
- The 2.0 line is an open beta, so interfaces, database schema, and the egg file format may still move between betas. This release is a single-defect fix and does not signal feature completeness or an API freeze. Stand up a staging panel on beta.2 from a production copy and validate your real eggs and operational surface before considering production use.
- What are the system requirements for Pterodactyl Panel?
- The panel needs the usual Laravel operational dependencies: a relational database, a queue worker, scheduled tasks, and persistent storage for server data. It also orchestrates Docker on managed nodes, so a panel misconfiguration can affect game-server workloads, not just the web tier. Confirm exact PHP, database, and Docker versions against the official docs for the beta you pin.
- How does Pterodactyl isolate game servers?
- Pterodactyl runs all game servers in isolated Docker containers on managed nodes while the Laravel panel provides the administrative UI and API. This separation means the panel controls Docker workloads, so node registration and daemon connectivity are critical operational checks. Validate node registration and server start and stop in staging before production.
- Does Pterodactyl have an API for automation?
- The panel exposes an API and a fine-grained permission model for managing users, nodes, resources, and servers. The context flags an open question about whether 2.0 introduces API or permission-model changes that could break existing automation. Test your automation against a staging beta.2 panel before upgrading production.
- What is the security policy for Pterodactyl?
- The project is designed with security in mind and runs game servers in isolated Docker containers. The provided context does not include the security disclosure policy or advisory history, so review the project repository and official channels for the current policy. Include that review in your evaluation before production use.
- What alternatives to Pterodactyl should I consider?
- The provided context does not name direct alternatives, focusing instead on Pterodactyl's fit for a Laravel and PHP estate. Evaluate alternatives against the same criteria: Laravel stack fit, Docker isolation, API and permission model, egg format stability, and upgrade path. Pterodactyl's differentiator here is that it is a conventional Laravel app with a Docker-orchestration blast radius.
Weaver
How can I help you explore Laravel packages today?