Hosted Control Plane vs Self-Installed Game Server Panel¶
Last reviewed: September 26, 2026.
Both models can run games on hardware you own. The difference is who operates the management layer around those games.
The Short Version¶
A hosted control plane is usually the better fit when you want browser management without maintaining another public web application. You still own the host operating system, container runtime, game data, capacity, power, and local network.
A self-installed panel is usually the better fit when control of the panel, its database, its extensions, and its availability matters more than reducing administrative work. You operate both the management service and the game hosts.
Swarm Hosts uses the first model. Crafty Controller, AMP, and Pterodactyl use the second. See the product decision guide for their different game, operating-system, and licensing approaches.
Who Operates What?¶
| Responsibility | Hosted control plane | Self-installed panel |
|---|---|---|
| Management website and updates | Service provider | You |
| Panel database, certificates, and availability | Service provider | You |
| Host operating system and container runtime | You | You |
| Host uptime and capacity | You | You |
| Player-facing game networking | You, sometimes with a provider relay | You, sometimes with a separate tunnel or relay |
| Panel backup and disaster recovery | Service provider | You |
| Game-data backup and restore testing | You | You |
The table describes responsibility, not physical data location. With Swarm Hosts, game data and local backups remain on your swarm host, while account and management metadata live in the hosted service.
Hosted Control Plane: Benefits And Costs¶
The main benefit is less web infrastructure to operate. There is no panel web server, database, certificate renewal, or public login endpoint to install on your game machine. An outbound agent connection can also make it easier to manage machines across more than one location.
The cost is dependence on another service for management. You need an account, the host needs outbound internet access, and you must trust the provider's authentication and task-delivery boundary. Confirm the provider's supported games and workflows because hosted services commonly control what can be launched.
For Swarm Hosts specifically:
- the agent and game workloads run on your Windows 10/11 or Linux machine;
- the browser control plane runs at Swarm Hosts;
- management requires the agent to reach the hosted service;
- the public catalog is curated; and
- player access uses either a supported managed relay or your own direct network path.
Read how Swarm Hosts works and the installation requirements before connecting a machine.
Self-Installed Panel: Benefits And Costs¶
The main benefit is control. You decide where the panel runs, how it is published, when it updates, how its metadata is backed up, and—subject to its licence—how it is modified or extended. A local-only panel can also keep its management interface inside your network.
The cost is ongoing operations. Depending on the product, that can include:
- installing and updating the panel and its dependencies;
- managing administrator accounts and secrets;
- configuring HTTPS, DNS, a reverse proxy, VPN, or firewall rules;
- backing up both panel state and game data;
- watching security announcements and applying patches; and
- recovering the panel, database, certificates, and game nodes after failure.
Those responsibilities remain even if the initial installer is easy.
Remote Management Is Not Player Connectivity¶
These are separate network paths:
- Management path: your browser reaches the control panel.
- Game path: players' clients reach the game server's TCP or UDP ports.
A hosted control plane can remove the need to expose a panel from your home, but it does not automatically make every game reachable. A self-installed panel can be safely available through a VPN while the game ports are public. Choose and test both paths independently.
For Swarm Hosts, compare managed relay and direct port forwarding.
A Practical Decision Checklist¶
Choose a hosted control plane when most of these are true:
- You want the shortest path from an existing machine to browser management.
- You do not want to patch and back up a management web stack.
- You want to manage hosts at multiple locations through one existing service.
- You are comfortable depending on the provider for management availability.
- The provider's curated game and administration workflows meet your needs.
Choose a self-installed panel when most of these are true:
- You require the panel and its metadata to remain under your administration.
- You need source-level changes, third-party extensions, or custom workloads.
- You need a management interface that can remain local to an isolated network.
- You are comfortable securing a web service and maintaining its dependencies.
- You have a tested backup and recovery plan for both panel state and games.
Keep An Exit Path¶
Do not let any panel be the only place that knows how your server works. Keep independent copies of worlds and configuration, record versions and ports, and periodically restore a backup somewhere disposable. A recoverable game server is more valuable than a convenient panel with an untested backup button.