How pterodactyl/panel works
Pterodactyl Panel is a PHP game-server management application: users and administrators manage accounts, server configuration, and runtime controls, while game servers run in isolated Docker containers. The visible request path begins at the PHP entry point and Laravel routing; client API routes dispatch to account and server-control controllers. Server, node, egg, allocation, backup, database, schedule, and user models provide the domain state, with a repository base as an internal persistence layer. The README establishes the product capabilities; several runtime integrations and route groups are not sampled, so those links are omitted or marked unverified.
Main entry points: Server.php Server state · Model.php Validated model base · Database.php Server databases · api-client.php Client API routes
Components 23
Application entry
- PHP entry point
public/index.php - Application bootstrap
bootstrap/app.php - Route configuration
app/Providers/RouteServiceProvider.php
Client API
- Client API routes
routes/api-client.php - Account API
app/Http/Controllers/Api/Client/AccountController.php - Server control API
app/Http/Controllers/Api/Client/Servers/PowerController.php - Admin server management
app/Http/Controllers/Admin/ServersController.php
Server domain
- Server state
app/Models/Server.php - User accounts
app/Models/User.php - Compute nodes
app/Models/Node.php - Egg configurations
app/Models/Egg.php - Network allocations
app/Models/Allocation.php - Server backups
app/Models/Backup.php - Server databases
app/Models/Database.php - Server schedules
app/Models/Schedule.php - Server permissions
app/Models/Subuser.php - Permission definitions
app/Models/Permission.php
Persistence and activity
- Validated model base
app/Models/Model.php - Repository base
app/Repositories/Repository.php - Model identity contract
app/Contracts/Models/Identifiable.php - Activity logging facade
app/Facades/Activity.php
Other components
- Panel user
- Wings game-server agent
Connections 23
- Panel user → PHP entry point: requests panel
- PHP entry point → Application bootstrap: loads
public/index.php - Client API routes → Account API: dispatches account
routes/api-client.php - Client API routes → Server control API: dispatches power
routes/api-client.php - Server state → Validated model base: extends
app/Models/Server.php - User accounts → Validated model base: extends
app/Models/User.php - Egg configurations → Validated model base: extends
app/Models/Egg.php - Server backups → Validated model base: extends
app/Models/Backup.php - Server databases → Validated model base: extends
app/Models/Database.php - Network allocations → Validated model base: extends
app/Models/Allocation.php - Server state → Server databases: relates to
app/Models/Server.php - Server state → Compute nodes: relates to
app/Models/Server.php - Server state → Egg configurations: relates to
app/Models/Server.php - Server state → Network allocations: relates to
app/Models/Server.php - Server state → Server backups: relates to
app/Models/Server.php - Server state → Server schedules: relates to
app/Models/Server.php - Server state → Server permissions: relates to
app/Models/Server.php - Server databases → Server state: belongs to
app/Models/Database.php - Repository base → Validated model base: uses model
app/Repositories/Repository.php - Server state → Model identity contract: implements
app/Models/Server.php - User accounts → Model identity contract: implements
app/Models/User.php - Server control API → Wings game-server agent: controls runtime
- Admin server management → Wings game-server agent: manages runtime