Runtime and processes
Check a self-managed game-control panel on a VPS, not a managed DotMoose game-server product, with panel security, daemon ports, storage, backups, and resource isolation owned by the customer.
Game panel VPS
Install and maintain your own panel on a Linux VPS. This is a self-managed server, not a DotMoose managed game-hosting service.
This is not a managed game-server product. You install and maintain the panel and applications on a self-managed VPS.
Hosting options
Self-managed virtual servers with administrator access, NVMe disks, shared vCPU, dedicated IPv4 and IPv6. RAM uses ballooning. Backups are sold separately.
See VPS hosting →02Canadian SFTP storage for your backup software. Check physical separation from your source server before treating a copy as off-site.
See Backup storage →03Register or transfer a domain and manage DNS. Registration and renewal prices depend on the extension.
See Domains →04Tell us what you need to host and when it needs to be ready.
See Ask about your project →Your requirements
Check a self-managed game-control panel on a VPS, not a managed DotMoose game-server product, with panel security, daemon ports, storage, backups, and resource isolation owned by the customer.
Identify databases, uploads, volumes, configuration and secrets that cannot be rebuilt from the application code. Back them up and test a restore.
List the ports that must be public and those that should remain private. Configure authentication, TLS and firewall rules before accepting traffic.
Check how the service starts after a reboot, where logs are stored and who applies updates. Test a deployment and rollback without changing live customer data.
Field guide
This page covers a self-managed setup: you install a game control panel such as Pterodactyl or a similar tool on a DotMoose VPS with administrator access, and you run it yourself. It is not a managed game server product, so panel updates, game server configuration, and player facing support are your responsibility.
A panel deployment has two layers with different needs: the web panel, which is light, and the daemon or wings component that runs the game servers, which consumes the memory and CPU each game title demands. Open only the panel and game ports you use, give each game server its own resource limits, and back up world data regularly.
List the panel port, the daemon port, and each game server's port before configuring the firewall. Panels allocate game ports from a range, and a blocked range shows up as servers that start but cannot be joined.
Set memory and CPU limits per game server inside the panel. One runaway server or memory leak should not starve the panel and every other server on the machine.
Back up world and configuration data with the game server stopped or with the game's own save commands flushed first. Live copies of world files can restore as corrupt worlds.
Planning
Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.
Use the detailed checklist to plan setup, access, migration and recovery with your team.
Download PDF →Send us the software you use, your storage needs and your launch or moving date.
Ask about hostingYour current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.