What Is a VPS? How Virtual Private Servers Work

How does a VPS work?

Virtualization

A physical server runs a hypervisor, software that splits the machine into isolated virtual machines. Nodesty uses KVM, the virtualization built into the Linux kernel. Each KVM virtual machine has its own kernel and operating system, so what happens in one VPS (a crash, a misconfiguration, a heavy process) does not affect the others.

Allocated resources

Each VPS gets a defined share of the host:

• RAM is reserved for your server. If your plan has 8 GB, 8 GB is yours.
• Storage is a fixed-size virtual disk. On modern platforms this sits on NVMe SSDs, which matters a lot for databases and game worlds.
• vCPU cores are scheduled on the host's physical cores. On most VPS platforms, including Nodesty's, processor time is shared fairly between servers and covered by a fair use policy, so sustained 100% CPU around the clock is not what a VPS is designed for. If you need guaranteed full-time CPU, a dedicated server is the better fit.
• Network: your VPS gets its own public IP address and a share of the host's network port.

Isolation

Because each VPS has its own operating system, you can choose the distribution, kernel settings and software without asking anyone. Your files and processes are not visible to other customers on the same host.

Linux or Windows?

Most VPS run Linux. Distributions such as Ubuntu, Debian and AlmaLinux are free, use little memory and are what most server software is documented for. Windows Server makes sense when your software only runs on Windows, for example some game server tools or .NET applications, or when you prefer to manage the server through Remote Desktop. Windows uses noticeably more RAM on its own, so plan for at least 4 GB.

Managing your VPS: the first steps

A VPS is usually unmanaged: the provider keeps the hardware, network and virtualization running, and you look after everything inside the server. On a fresh Linux VPS, these first steps make a big difference:

1. Update the system with your distribution's package manager, for example apt update && apt upgrade on Ubuntu or Debian.
2. Create a normal user with sudo rights instead of working as root all the time.
3. Use SSH keys and disable password logins, which stops the automated password-guessing that every public server sees within minutes.
4. Turn on a firewall such as ufw and open only the ports you actually use, for example 22 for SSH and 80/443 for a website.
5. Enable automatic security updates, so known vulnerabilities are patched even when you are busy.
6. Set up backups. Provider backups protect against hardware failure and mistakes; keep an extra copy of important data somewhere else as well.

None of this is complicated, but it is your responsibility. If you would rather not manage a server at all, shared hosting is the better fit.

VPS vs shared hosting vs dedicated server

The easiest way to understand a VPS is to compare it with the alternatives:

Shared hosting such as cPanel or DirectAdmin web hosting is ideal when you only need to run websites and do not want to manage a server. A dedicated server makes sense once you consistently need the full power of a machine. A VPS covers almost everything in between.

What is a VPS used for?

• Websites and web applications that have outgrown shared hosting, or that need a specific runtime such as Node.js, Python, Go or Docker.
• Game servers for Minecraft, FiveM, Rust and similar games, where you need full control over the server software and plugins.
• Bots and automation, for example Discord or Telegram bots and scheduled jobs that must run around the clock.
• Databases and APIs that back a mobile app or an online shop.
• Development and staging environments that mirror production without touching it.
• Internal tools for a team, such as a wiki, monitoring dashboard or file sync service.

Because a VPS is exposed to the internet with its own IP address, it can also be a target for attacks. Our guide What is a DDoS attack? explains what that means and how protection works.

What to check when choosing a VPS

Not all VPS plans are equal, even when the RAM and price look similar. These are the points that make the biggest difference in practice:

• Processor. Single-core speed decides how responsive game servers, PHP sites and many databases feel. A high-clock CPU such as the AMD Ryzen 9 9950X (up to 5.7 GHz) is the better choice there. Many-core server CPUs such as the AMD EPYC 7763 are strong for parallel workloads and usually give you more RAM for the money.
• RAM. Size it for your peak, not your average. Running out of memory is the most common cause of a VPS slowing down or crashing.
• Storage type. NVMe SSDs are many times faster than SATA SSDs for random reads and writes. Ask what the disk actually runs on.
• Location and latency. Choose a data center close to your users. Frankfurt, for example, gives low latency across Europe and around 30–50 ms from Istanbul.
• DDoS protection. Check whether it is included, which layers it covers and whether it is always on.
• Operating systems. Make sure the distributions or Windows Server versions you need are available, and whether Windows costs extra.
• Backups. Find out whether backups are included, how often they run and how long they are kept.
• Upgrade path and support. You should be able to move to a bigger plan without migrating, and reach support around the clock.

At Nodesty, the AMD Ryzen 9 9950X VPS is built for single-core speed and runs in Frankfurt and New York, while the AMD EPYC 7763 VPS offers more RAM for the price in Frankfurt. Both include NVMe storage, nShield DDoS protection and your choice of Linux or Windows Server at no extra cost.