£2 Metin 2 VM
A first test world
£2.00/mo
£2.00/mo
excl. VAT (UK clients only)
- 2vCore @ 3.6Ghz
- 2GB DDR4
- 20GB Gen 4 NVMe SSD
- 5Gbps Networking
Plans
Pick the machine your world will fit on
Every plan is the same platform: dedicated 3.6GHz cores, Gen 4 NVMe, 5Gbps networking and DDoS filtering. The only thing that changes is how much of it is yours. Paying yearly halves the monthly rate from VM 1 upwards.
On every plan
Full root access
KVM/VNC console
Free OS reinstalls
Daily offsite backups
Manual snapshots
Windows Server licence included
Metin 2 VM 1
A small private world for friends
£5.99/mo
£2.99/mo
excl. VAT (UK clients only)
Save 50%, paid yearly- 2vCore @ 3.6Ghz
- 4GB DDR4
- 60GB Gen 4 NVMe SSD
- 5Gbps Networking
Metin 2 VM 2
A growing server with regular PvP
£9.99/mo
£4.99/mo
excl. VAT (UK clients only)
Save 50%, paid yearly- 4vCore @ 3.6Ghz
- 8GB DDR4
- 120GB Gen 4 NVMe SSD
- 5Gbps Networking
Metin 2 VM 3
Busy sieges and a live database
£15.99/mo
£8.49/mo
excl. VAT (UK clients only)
Save 50%, paid yearly- 6vCore @ 3.6Ghz
- 12GB DDR4
- 180GB NVMe SSD
- 5Gbps Networking
Metin 2 VM 4
Several channels on one machine
£20.99/mo
£10.49/mo
excl. VAT (UK clients only)
Save 50%, paid yearly- 8vCore @ 3.6Ghz
- 16GB DDR4
- 240GB Gen 4 NVMe SSD
- 5Gbps Networking
Metin 2 VM 5
A large world plus a test realm
£23.99/mo
£11.99/mo
excl. VAT (UK clients only)
Save 50%, paid yearly- 10vCore @ 3.6Ghz
- 20GB DDR4
- 300GB Gen 4 NVMe SSD
- 5Gbps Networking
Metin 2 VM 6
Multi-channel plus a web front end
£25.99/mo
£12.95/mo
excl. VAT (UK clients only)
Save 50%, paid yearly- 12vCore @ 3.6Ghz
- 24GB DDR4
- 300GB Gen 4 NVMe SSD
- 5Gbps Networking
Metin 2 VM 7
The whole cluster on one box
£29.00/mo
£14.50/mo
excl. VAT (UK clients only)
Save 50%, paid yearly- 16vCore @ 3.6Ghz
- 32GB DDR4
- 300GB Gen 4 NVMe SSD
- 5Gbps Networking
Prices exclude VAT and are shown per month. Metin 2 VM 7 is ordered from the UK VPS 7 Elite product page. Need more than 32GB, or bare metal for a full cluster? Our dedicated servers start where this range stops.
Built for Metin2
What a Metin2 world actually needs from a server
Metin2 is not one process. It is a game core, several channel processes, a database and usually a web front end, all on the same box and all reaching for the same disk. These are the things that decide whether a siege holds together.
-
Disk latency, not disk size
Channel switches, item drops and every database write hit the disk. Gen 4 NVMe on every plan is why a busy dungeon does not stutter while MySQL flushes.
-
Single-thread speed
Game cores lean heavily on one thread, so clock speed matters more than core count. Every plan runs on 3.6GHz cores allocated to you rather than shared out of a pool.
-
Filtering that knows the traffic
A popular private server is a target. EdgeProt applies application-level rules and gives you attack reports, instead of null routing your IP until the attack stops.
-
Root, because sources vary
No game panel and no locked filesystem. Compile your own binaries, install the exact library versions your source expects, and keep the startup scripts you already have.
-
A way back from a bad update
Daily offsite backups run automatically. Take a manual snapshot before a rate rebalance or a source change, then roll back from the panel if the community hates it.
-
Headroom without a rebuild
CPU, memory and NVMe space grow on the same machine, so a server that outgrows its plan keeps its IP address, its files and its players.
Server visibility
Why a cached query makes a server look alive
A server browser ranks partly on how fast you answer it. Answer from one machine in the UK and a player in Warsaw waits for the full round trip. Answer from an edge node near them and the same server sorts higher in the same list.
Scroll the diagram sideways to see both paths
-
01
The query never reaches your rack
Server browser lookups are answered from the edge node closest to the player, so a listing refresh does not spend your machine's CPU or your uplink.
-
02
Latency is part of what the browser sorts on
Answer in 10 to 30 milliseconds across Europe and North America and your server can appear above one that answers in triple that, at the same player count.
-
03
Query floods stop being an outage
Query reflection attacks are absorbed at the edge alongside the rest of the EdgeProt filtering, so a spike in lookups does not take the world offline.
Related: DDoS protection UK VPS hosting Remote MySQL hosting All game servers
Day to day
The machine, and the button to rebuild it
You get the VirtFusion panel, not a support queue. Console access, OS reinstalls, snapshots and traffic graphs are all self-service, which matters when a source update goes sideways at two in the morning.
-
KVM and VNC console
Reach the machine even when a firewall rule or a broken network stack has locked you out of SSH.
-
Free OS reinstalls
Debian, Ubuntu, CentOS, AlmaLinux, Fedora, Arch, and Windows Server 2019, 2022 or 2025, in a couple of minutes at no extra cost.
-
Snapshots on demand
Take one before a risky change and roll back from the panel if it did not land. Daily offsite backups run underneath regardless.
-
Traffic and load graphs
See what the box is doing over 30 minutes to a week, so a slow channel shows up as a shape rather than a guess.
-
Firewall manager
Open only the ports your source and your channels actually use, from templates rather than from memory.
Getting started
How to create a Metin2 private server
The hosting part is ours, the world is yours. This is the order most people work in, and our team will help with the server side of any of it.
-
01
Size the machine
Pick a plan with room for the game core, your channels and MySQL together. 4GB is enough to learn on; 8GB to 16GB is where most live servers settle.
-
02
Prepare the environment
Deploy Debian or Ubuntu for stability, connect over SSH, update the system, then install the dependencies your source expects, including MySQL and the libraries it links against.
-
03
Upload the server files
Copy your Metin2 source across, set file permissions and ownership, then import the SQL dumps so the account, player and item databases exist before the core starts.
-
04
Match the configuration
Point the config at your database credentials, set your rates, item tables and player limits, then run the startup scripts and confirm each channel is listening.
-
05
Build and hand out the client
Edit your client files so they connect to the machine's IP and ports, then distribute the packaged client to your community.
-
06
Keep it standing
Snapshot before changes, keep the firewall tight, patch the operating system, and watch the graphs. The backups run themselves; community management is the hard part.
We supply the server, the network and the protection. Sourcing your game files, and any rights or licensing questions attached to them, are yours. Our acceptable use policy sets out where that line sits.
UK data centre
Where it runs
Our own hardware, in our own building
These are not resold cloud instances. We build the nodes and we own the UK facility they sit in, which is why an engineer can stand next to your machine rather than raise a ticket with a landlord.
-
UK routing into London
Onward transit and peering from London, so European players get a short path in. Check it yourself on our Looking Glass.
-
Filtered before it arrives
Every machine sits behind the same always-on EdgeProt filtering as the rest of the platform, with attack reports in your panel.
-
Support from the people who own it
24/7, in house, and reachable on Discord as well as by ticket. Not an outsourced first line.
Paying for it
Pay your way
Card and PayPal are handled at checkout. If the method you use is not here, open a ticket and we will tell you what else we can take.
