Set it up once.
It runs.
Persistent worlds need consistent tick rates, zero noisy neighbours, and hardware that doesn't get migrated or rebooted at someone else's convenience. Dedicated bare metal solves all three. No surprises at 3am when your world is active.
What we run
Always-on worlds, long-running survival maps, community servers that have been running for months. No world resets, no downtime windows, no per-player caps.
Why persistent worlds need dedicated hardware
It's not about raw performance. It's about consistency — the thing shared hosting fundamentally cannot guarantee.
FAQ
What uptime can I expect?
99.9% on the hardware side. The machine doesn't go down unless there's a hardware failure or scheduled maintenance — both of which you'd hear about in advance. We don't reboot nodes without notice and we don't migrate your server to balance load the way shared hosts do.
Do you do backups?
Ask us and we'll set up automated world backups. Frequency and retention are up to you. We keep a copy offsite so a disk failure doesn't mean a lost world.
Why does a persistent server randomly lag at 3am?
On shared hosting, other tenants on your node are more active at certain times — backups, restarts, traffic spikes. Your 3am lag is someone else's peak hour. On dedicated bare metal there are no other tenants. Your server at 3am performs identically to your server at peak.
Can I run multiple worlds on one allocation?
Yes. If the allocation has the RAM and CPU headroom, run as many world processes as you want. We don't charge per world — you pay for compute.
Other server types
Tell us what you need to run.
Game, expected load, how long you've been running the world. Real quote, usually same day.
[email protected]