HARDWARE
Our infrastructure Built for your world
Our own hardware, two compute nodes and a separate management layer. See what runs your server, from the processor to the control panel.
- NODES
- 02
- REGION
- US Central
- PLATFORM
- Ubuntu 26.04 LTS · bare metal
Hardware per compute node
- CPU
- Intel Core i9-10980XE
- 18C / 36T · up to 4.8 GHz
- MEMORY
- 256 GB
- STORAGE
- 5 TB NVMe
- NETWORK
- 1 GbE uplink
These are the host specifications. Your server's memory, CPU allocation and storage are defined by the plan you choose.
A closer look at our hardware
Photographs of our own rack: its front, its interior and the equipment mounted inside.
Behind your server
One platform. Separate responsibilities
The website, control panel and game workloads have distinct roles. Open a topic to see how they fit together.
Compute Game workloads on compute nodes
Game servers run on compute nodes, separately from the public website. The Pterodactyl-based control panel manages the workload; the game itself runs on the node.
Memory Memory limits set by your plan
The memory selected in your plan is applied to your server instance. A node's total RAM and the memory allocated to your server are different figures.
Storage World data on local NVMe storage
World files are stored locally on the node running the game. Infrastructure backups are kept separately from the servers they came from.
Network Public access, separate internal services
The website, game nodes and supporting services are separated. Internal components communicate over private paths; players connect to the public game endpoints.
Database A separate state store for the panel
The control panel stores its state in a central MariaDB service, separate from the web application and game nodes. Schema migrations are part of the panel deployment process.
Deployment Repeatable container deployments
The control panel is delivered as a container image. Releases recreate the container and apply the required migrations through the deployment process.
Server allocation A game instance on a compute node
When a server is created, the management layer selects a game node and applies the resources from the chosen plan. The game runs there, separately from the website.
Reliability and operations Maintenance by service and role
The website, database and game workloads have separate infrastructure roles. This separation lets maintenance target an individual service without treating the entire platform as one application.
Choose a home for your next world
Compare the plans or request a test server before choosing your configuration.