
Your webshop, booking system, automations and the database behind them need a proper server, and an IT partner, a customer's security questionnaire or a forum thread tells you a dedicated server is the professional choice. A VPS usually costs less and grows in steps. The real differences sit below the operating system: who shares the hardware, who handles a failed disk, how you grow and how much admin you take on. Here they are, with the questions to ask a provider before you sign.
Quick answer: A VPS is a virtual machine with its own operating system on a physical server that other customers share; a dedicated server is a physical machine only you use. Unless you pay for management, updates, security and backups are yours on both. On a VPS, hardware faults are the provider's problem and you grow by moving to a bigger plan. On a dedicated server, nobody shares your CPU, but you watch the disks, a failed part means a technician and often some downtime, and growing can mean a new machine. Start on a VPS unless you can name the reason for dedicated hardware: CPU contention you have measured, a workload bigger than the largest plans, a licence counted per physical core or socket, or a contract that requires single-tenant hardware.
What You Get With Each
| VPS | Dedicated server | |
|---|---|---|
| Hardware | A share of one physical server | The whole physical server |
| Shared with other customers | CPU cores and caches, disks, network | Nothing inside the machine |
| A failed disk or power supply | The provider's job | The provider swaps the part, you repair the system |
| More capacity | A bigger plan | Extra parts if the model allows, or a new server |
| Updates, security, backups | You, on a self-managed plan | You, unless you buy management |
Isolation and Resources
A KVM VPS is full hardware virtualization with its own kernel, unlike a container, which shares the host's kernel (the systemd-detect-virt manual lists both kinds). The hypervisor keeps your memory and files apart from those of other customers, but the hardware is shared. Your vCPUs take turns on the host's cores, so a busy neighbour can make them wait, which shows up as steal time; our shared vCPU guide shows how to log it. Disk and network capacity are shared too.
Sharing a processor has a security side as well, because some CPU flaws cross the line between virtual machines. The kernel's L1TF documentation describes one in a wide range of Intel processors (the same page lists AMD processors as not affected): "a malicious guest running on one Hyperthread" can attack data from "a different guest" on the sibling thread of the same core. The fixes are the host's job and can cost performance, such as switching off SMT or "confining guests to dedicated cores". On a dedicated server, no other customer's code runs on your CPU, so that class of risk is gone. The rest of the security work, from SSH keys to updates, is the same on both.
Not sure which one you have? This prints the virtualization technology, such as kvm, or none on a physical server:
systemd-detect-virt
When Hardware Fails
Disks, power supplies and memory fail sooner or later. What differs is who does what.
On a dedicated server, the provider owns the parts and you own the system on them. OVHcloud's responsibility table for its dedicated servers (checked 31 October 2026) lists "Replace the defective hardware elements of the Dedicated Server" as OVHcloud's task, while the customer has to "request the replacement of defective hardware" and owns the backup jobs, "data continuity and sustainability" and the disaster recovery plan. Hetzner's guide to replacing a disk in a software RAID (checked 31 October 2026) shows what a swap involves: you book it with support, "The support team will need to take the server off-line for a short time", and afterwards you give the new disk "the exact same partitioning" as the healthy one, add it back to the array with mdadm and install the boot loader on it.
So on a dedicated server, watching the disks is your job. On Ubuntu 24.04 and Debian 12, install smartmontools, list the disks and ask each one for its health:
sudo apt install smartmontools
lsblk -d
sudo smartctl -H /dev/sda
sudo smartctl -H /dev/nvme0n1
cat /proc/mdstat
Replace the device names with the ones lsblk -d prints: sda, sdb and so on for SATA disks, nvme0n1 and up for NVMe. On SATA and NVMe drives, smartctl -H prints SMART overall-health self-assessment test result: PASSED, or FAILED! when the drive reports a problem. In /proc/mdstat, [UU] means both disks of a mirror are in the array, while [U_] or [_U] means one is missing or defective. The package's smartd daemon polls the drives every 30 minutes by default, logs problems to syslog and can email warnings once you configure it.
On a VPS, the host's disks, power supplies and fans are the provider's to monitor and replace. What happens to your VPS during a failure depends on the platform. AWS documents its approach for EC2 (automatic instance recovery, checked 31 October 2026): it "will attempt to move your instance from the host with the underlying hardware or software issue to a different host", which looks to the server like "an unplanned reboot", and "data stored in volatile memory (RAM) will be lost". Ask your provider what it does when a host fails.
Either way, a backup on the same server goes down with it. Keep copies off the server and test restoring them; our disaster recovery checklist covers the plan around them.
Upgrades and Growth
A VPS grows in steps: when monitoring shows you are short of memory, CPU or disk, you move to a bigger plan. Our upgrade guide covers which signals to trust first. A dedicated server is a fixed machine. At Hetzner (checked 31 October 2026), the current AX servers have fixed hardware: "You cannot order additional hardware; instead, you must upgrade to a different server model to obtain more drives or RAM." Its upgrade guide describes the standard route: order the new server, receive a new IP address, migrate your data and cancel the old one, and "we will invoice you for both servers as long as they exist in parallel". So with a dedicated server you buy for the peak you expect over its lifetime and pay for capacity you don't use yet.
Costs and Admin Time
The monthly price is only part of the bill. Compare these lines:
- The machine. A VPS bills a slice of a server; a dedicated server bills the whole machine, busy or idle.
- One-off and term costs. Ask about setup fees, minimum terms and what a remote console or an extra part costs.
- Your hours. The operating system work is the same on both, and a dedicated server adds the hardware jobs. Hetzner's AX page puts it plainly: "You as the customer are responsible for all normal system administration tasks (software, monitoring, RAID configuration, backups, security, etc.)".
| Job | Self-managed VPS | Dedicated server |
|---|---|---|
| OS updates and security | You | You |
| Backups and restore tests | You | You |
| Disk health checks and repair after a disk swap | The provider | You |
| Replacing failed parts | The provider | The provider, after your request |
| More capacity | A plan change | New parts or a new server, then a migration |
Put a value on those hours before you compare prices. Our VPS price checklist helps you compare offers line by line.
Compliance Questions to Ask
Neither server type makes you compliant on its own. The GDPR asks for security that fits the risk: the European Commission's summary of the obligations says the measures "need to be adjusted to the likelihood and severity of the risk", with examples such as encryption and the "ability to restore the availability and access to data in a timely manner (cases of physical or technical incident)". A host that stores personal data for you usually acts as your processor: the Commission calls "offering IT solutions, including cloud storage" a typical processor activity. Ask any provider, VPS or dedicated:
- Will you sign a data processing agreement? Processing on your behalf needs "a contract or other legal act", and the contract "must indicate what happens to the personal data once the contract is terminated".
- Which other companies are involved? A processor "cannot subsequently appoint another processor without a prior, specific or general written authorisation" from you. Ask about the data center operator, backup storage and support tools.
- Where are the server and the backups, and is any of it handled outside the EEA? Transfers out of the EEA need special safeguards "to ensure that the protection travels with the data".
- How fast can you restore service after a hardware failure, and who does the work? That is the restore ability the Commission lists.
- Does anyone require single-tenant hardware? A customer contract, an auditor or a licence might. AWS presents its Dedicated Hosts (checked 31 October 2026) as an option to run applications "on a single tenant infrastructure to meet any specific corporate compliance and regulatory requirements". If a contract says single tenant, a VPS doesn't qualify, however well you secure it.
Signs You Need Dedicated Hardware
- Your CPU waits, and you have measured it. Steal time climbs whenever your app slows down, or your work keeps every core busy for hours. A VPS with dedicated cores is the step before a whole server.
- You have outgrown the largest plans, even after fixing leaks, runaway logs and repeated work.
- A licence counts sockets or physical cores. AWS's Dedicated Hosts exist partly for licences "that are bound to VMs, sockets, or physical cores". Ask the vendor whether a VPS is allowed and how it counts.
- A contract requires single-tenant hardware (question 5 above).
- You need hardware a VPS plan doesn't offer, such as a GPU or a lot of local disk space.
Why Most Small Businesses Start on a VPS
A website, a booking or CRM tool, a few automations and a small database are general purpose workloads, and AWS notes in its burstable instance guide that "Many general purpose workloads are on average not busy". A slice of a modern server fits that, so you pay for what you need now instead of a machine sized for later. Hardware faults stay with the provider, so nobody on your team watches disks or books technicians. Updates, security and backups are yours on either type, so you learn that work on the cheaper one. And nothing locks you in: the same Linux runs on a dedicated server, so moving later is a normal server migration.
Which One Fits
- A VPS if your apps are mostly idle, you want hardware faults handled by the provider and nobody requires single-tenant hardware. Most small businesses fit here.
- A VPS with dedicated cores if you have measured CPU contention but the rest of the VPS model suits you.
- A dedicated server if a contract or licence requires one, you have outgrown the largest plans or you need hardware a VPS doesn't offer, and someone on your team can watch disks and rebuild a server.
Still on shared hosting? Our VPS vs shared hosting guide covers that step first, and our guide for hosting resellers looks at the move from a reseller's side. Our own VPS plans are KVM virtual machines with full root access, dedicated RAM and shared vCores in an EU data center, from 2 vCores and 2 GB of RAM up to 12 vCores and 48 GB, and you move to a bigger plan from the client area. They are self-managed, so if you want help running the server, ask support about the scope before you order.
FAQ
Is a dedicated server more secure than a VPS? It removes one risk: other customers' code on your CPU. It doesn't install your updates, guard your SSH keys or make your backups. That work is yours on both, and a well-kept VPS is safer than a neglected dedicated server.
Does the GDPR require a dedicated server? No. It asks for security that fits the risk, a contract with your processor and safeguards for transfers outside the EEA, and none of that names a server type. A customer contract or an auditor can still require single-tenant hardware, so check yours.
What happens to my VPS when its physical server fails? That depends on the provider. AWS tries to move an affected instance to another host, which looks like an unplanned reboot; ask your provider what it does, and keep backups off the server either way. On a Space-Node VPS, backups are not included in the plan price, but you can arrange them through a support ticket.
Is a VPS with dedicated vCPUs the same as a dedicated server?
No. Dedicated vCPUs reserve processor time for you, but the server is still a virtual machine on a shared host: disks, network and the rest of the hardware are shared, and systemd-detect-virt still prints a virtualization technology such as kvm.
Can I move from a VPS to a dedicated server later? Yes. Both run the same Linux distributions, so it is a normal server move: set up the new machine, copy the data, test, then switch DNS. Our migration guide covers each step.
Sources
All opened on 31 October 2026:
- Hetzner Docs: Exchanging hard disks in a Software-RAID, AX Server, Upgrading dedicated servers
- OVHcloud: Shared responsibility for Dedicated Servers
- AWS: Automatic instance recovery, Amazon EC2 Dedicated Hosts FAQs, Burstable performance instances
- European Commission: Application of the GDPR, Obligations, Rules on international data transfers
- Linux kernel: L1TF, L1 Terminal Fault
- systemd: systemd-detect-virt manual, systemd-detect-virt(1) for Ubuntu 24.04, source files virt.c (v255) and virt.c (v252)
- smartmontools: smartctl(8) and smartd(8) for Ubuntu 24.04, packages for Ubuntu 24.04 and Debian 12, source files ataprint.cpp and nvmeprint.cpp
- util-linux: lsblk(8) for Ubuntu 24.04 and Debian 12