Fixed instances per host
A host takes a set number of game instances and no more, even when the order queue is full. 61% average CPU utilisation is a deliberate ceiling, not a missed opportunity.
Game servers · Voice · 15 locations
Small, fixed-density nodes for communities of five to forty players. You get the memory you pay for, a traffic limit we publish, and backups that restore in minutes rather than in a support thread.
Answered within one business day. No card needed to ask.
Templates
Each template is maintained in the panel and updated when the game pushes a breaking change. Nothing here is a one-off image somebody uploaded once.
Why it costs less
Three decisions that make the price lower without making the server worse.
A host takes a set number of game instances and no more, even when the order queue is full. 61% average CPU utilisation is a deliberate ceiling, not a missed opportunity.
500 GB to 6 TB depending on the plan, counted per instance and visible in the panel. Over the limit the port drops to 20 Mbit/s. No overage invoice, no fair-use clause.
Support is engineers on call, not a call centre reading a script. That is also why accounts are opened in batches after a request rather than through an instant checkout.
Plans
All plans include SFTP, console access, DDoS filtering and a nightly backup. VAT 21% included.
The usual choice for a modded world with a steady group.
6,30 €/ mo
Network
Latency below is measured from this node to the others. A world can move between them without changing its address in the panel.
| Node | Country | Latency | State |
|---|---|---|---|
| LV Riga this node | Latvia | 1 ms | Operational |
| EE Tallinn | Estonia | 9 ms | Operational |
| LIT Vilnius | Lithuania | 9 ms | Operational |
| FI Helsinki | Finland | 11 ms | Operational |
| SWE Stockholm | Sweden | 12 ms | Operational |
| PL Warsaw | Poland | 15 ms | Operational |
| RU Moscow | Russia | 20 ms | Operational |
| RU-MSK Moscow | Russia | 20 ms | Operational |
| RU-02 Moscow | Russia | 20 ms | Operational |
| RU-SH Moscow | Russia | 20 ms | Operational |
| DE Frankfurt | Germany | 28 ms | Operational |
| NL Amsterdam | Netherlands | 29 ms | Operational |
| CHZ Zurich | Switzerland | 32 ms | Operational |
| FR Paris | France | 36 ms | Operational |
| US Ashburn | United States | 139 ms | Operational |
Status
Customers
Stable 20 ms to Tallinn and 30 ms to Warsaw. For our small league that is more than enough.
We moved from a shared panel and the difference is obvious: no lag spikes when another server starts.
Notes
We replaced the storage layer on Riga over one night in a maintenance window. No world data moved between hosts, and no server was offline for longer than four minutes.
Opus stereo is now on by default for voice servers on the Riga node. Mono remains available if your group prefers it.
Why a 3 GB world can produce a 40 GB backup window, and the three settings that keep backups from eating the disk.
A short, unglamorous report on traffic, peak hours and why the node is not packed to the ceiling.
Player count matters less than explored map area. Numbers from servers on our nodes, and why we set the minimum plan where we did.
A faulty optics module, a bad monitoring threshold, and what changed afterwards.
Write a few lines about the game, the player count and the region you need. We answer within one business day with a concrete node and a date.