What Is a VDS and What Is It Used For? A Beginner's Guide

What is a VDS?

VDS stands for virtual dedicated server. A powerful physical server in a data centre is split into several independent virtual machines using virtualisation software, and one of those machines is yours. From the outside it behaves like a separate computer: it has its own IP address, operating system, users and disk. Other customers on the same physical host cannot see your files, and you cannot see theirs.

The difference from shared web hosting is that the whole environment belongs to you. With web hosting you work inside a control panel the provider has set up, limited to the software it supports. With a VDS you start from a clean operating system, install whatever you need and open whichever ports you like. The difference from a dedicated server is that you share the hardware: you get a reserved slice of the machine rather than the whole thing. That makes a VDS a middle ground between flexibility and cost.

How do virtualisation and KVM work?

At the heart of virtualisation is a software layer called a hypervisor. It divides the physical CPU, memory and disks between virtual machines and keeps each one isolated from the others. KVM (Kernel-based Virtual Machine) is a hypervisor built into the Linux kernel that uses the processor's hardware virtualisation features, and it is one of the most common choices among virtual server providers today.

For you as a user, the key consequence of KVM is that every virtual machine runs its own kernel. You can install Windows Server as easily as a Linux distribution, load kernel modules and run tools like Docker without workarounds. With container-based virtualisation, by contrast, all customers share the host's kernel and that flexibility is limited. Our guide comparing VPS, VDS and dedicated servers goes deeper into the two approaches.

Is a VDS the same as a VPS?

Technically both are virtual servers, and internationally the product is generally called a VPS (virtual private server). In Türkiye there is a well-established naming habit: many providers call plans with guaranteed or reserved resources VDS, and plans with more flexible or shared resources VPS. There is no common standard behind this, though, so one company's VDS can have exactly the same specs as another company's VPS.

The sensible approach is to ignore the label and look at the technical details. Ask whether the virtualisation is KVM, whether vCPUs are dedicated or shared, whether RAM is guaranteed and whether the disk is NVMe. On TheCrewHost's site this product lives on the VPS page and runs on KVM, so you can search with either name. We compare the terms in detail in a separate guide; this one focuses on what a VDS is and what it is good for.

What is the difference between dedicated and shared vCPUs?

A vCPU is a virtual processor core assigned to your virtual machine, usually mapping to one thread of the physical processor. With shared vCPUs, the same physical cores are time-sliced between several virtual machines, so when your neighbours are busy your machine can slow down too. That model is economical for websites or test servers that sit idle most of the time and only see occasional load.

With dedicated vCPUs, the cores assigned to you are not shared with another customer, and performance stays far more consistent through the day. For game servers, trading bots and anything that computes continuously, that consistency makes a real difference.

Core speed matters as much as core count. Game servers such as Minecraft or Rust do most of their work on a single main thread, so a processor with strong single-thread performance is worth more than a larger number of slower cores. When comparing plans, look up the actual CPU model rather than trusting the core count alone.

What does root or administrator access give you?

Full control is the biggest advantage of a VDS. As root on Linux or Administrator on Windows, you can reach every corner of the system: install packages, start services, write firewall rules and schedule tasks. You connect to a Linux server over SSH and to a Windows server over Remote Desktop (RDP). Node.js, Python, Java or Go applications, custom databases and long-running background processes that shared hosting would not allow are all fine on a VDS.

That power comes with responsibility. A wrong command can leave the system unbootable, and a forgotten update or a weak password can leave it open to attack. Good habits include using a separate user with sudo rights instead of working as root, logging in with SSH keys and taking a backup before any significant change. For the first security steps on Windows, see our guide to setting up a Windows VDS and connecting over RDP.

What is a VDS used for?

A VDS suits almost any job that needs to stay online around the clock and does not fit within the limits of shared hosting. Unlike a home computer, it is not affected by your power cuts or internet outages, it has a fixed IP address and it benefits from the data centre's network. The table below sums up the most common uses and what matters most for each.

You can also run several jobs on a single VDS: a small website, a Discord bot and a VPN can live together comfortably on one machine. The only thing to watch is the total load. If one job eats the RAM or CPU, the others suffer, so it is usually healthier to keep something heavy, such as a busy game server, on its own machine.

What should you check when choosing a VDS?

Plan tables look alike at first glance, and the details are where they differ. Look beyond the core count to the processor model: a single core of a current-generation chip can outrun two cores of an older server CPU. Check whether RAM is guaranteed, whether the disk is NVMe or SATA SSD, and what the port speed and traffic allowance are.

On the network side, DDoS protection and location stand out. Game servers and public services can become targets, so ask whether protection is included. If most of your users are in Türkiye, a server in Türkiye cuts latency noticeably. TheCrewHost's VDS plans run on KVM in an İstanbul data centre, with Ryzen 9 9950X and Intel Xeon options, Samsung 990 PRO NVMe storage and free DDoS protection, and setup completes automatically after payment.

• CPU model and single-thread performance, not just the number of cores
• Guaranteed RAM and the option to upgrade later
• Disk type: NVMe SSD reads and writes far faster than SATA SSD
• Port speed and monthly traffic allowance
• DDoS protection included in the plan
• Server location and latency to your users
• Operating system options: Linux distributions and Windows
• Snapshot and backup options, and whether they cost extra
• Support channels, hours and language

What is the difference between managed and unmanaged VDS?

With an unmanaged VDS, the provider is responsible for keeping the hardware, network and virtualisation layer running, and everything inside the virtual machine is up to you. Operating system updates, the firewall, software installs, backups and clean-up after a compromise are your job. A managed service takes some of that work off your hands, but the scope varies from company to company, so read exactly what the contract includes.

Which one suits you depends on your skills and your time. If you are comfortable at the Linux command line, an unmanaged VDS gives you the most freedom and the best value. If you do not want to administer a server and all you need is a website, cPanel web hosting is often the better starting point; we cover that decision separately in our web hosting vs VPS guide.

What should you do first after getting a VDS?

Start by updating the system and locking down access. On Linux, install all updates through the package manager, create a user with sudo rights instead of working as root, enable SSH key login and turn off password login. Then use a firewall such as ufw or firewalld to open only the ports you need. On Windows, run Windows Update, set a strong password and restrict who can reach RDP.

Next, set up backups. Use the provider's snapshot or backup service if there is one; if not, write a script that regularly copies important files somewhere off the server, because a backup on the same disk will not help when that disk fails. Finally, learn to watch resource usage. htop and df on Linux, or Task Manager on Windows, are the first tools that tell you a server needs to grow.

• Install all system updates
• Create a separate user with admin rights
• Secure login with SSH keys or a strong password
• Open only the ports you need in the firewall
• Set up backups stored off the server

Frequently Asked Questions