Skip to content
Tarisu Limited

VPS or a dedicated server: when the whole machine is worth it

Updated: 7 November 2026 67 views

A virtual server is a slice of a machine with a hypervisor underneath it. A dedicated server is the machine. The difference is real but it is narrower than it sounds, and it matters for fewer workloads than the people selling dedicated hardware would like.

What we actually sell

Five KVM plans, all in Istanbul, on hosts we own: 1 to 6 vCores, 2 to 10 GB of memory, 30 to 75 GB of SSD, a 10 Gbit/s port with 4 TB of transfer, one IPv4 address and a console in your client area. You pick the operating system at the order screen from thirteen images, and the server is built automatically when the payment clears.

Dedicated machines are not a price list here. There is no range to scroll through and no configuration to add to a cart: you tell us the cores, memory, storage and location the work needs, and we quote that build with its lead time. That is a slower process on purpose, because a physical machine is ordered, racked, cabled and installed by people.

The four reasons to take a whole machine

  • More of a machine than the virtual range holds. If the measured requirement is past 6 cores and 10 GB, the virtual plans have run out and the question answers itself.
  • Consistent processor, not merely enough of it. A virtual server has its share reserved, but it shares a physical host. Work that cares about the variation rather than the average, real-time processing and some database work, is the honest case for single tenancy.
  • Storage shaped a particular way. A specific disk layout, a RAID level, a quantity of local storage that a virtual plan does not offer.
  • A rule that requires it. Sometimes an auditor, a contract or a licence says single tenancy, and no amount of measurement changes that.

Reasons that are not reasons

"It feels faster." Measure it. A loaded site on a virtual server is usually slow because of something inside the server rather than underneath it, and moving the same configuration onto bare metal moves the problem with it.

"It is more secure." Single tenancy removes one class of risk and changes nothing about the ones that actually cause incidents: an out of date application, a weak password, an open port. Both come with the whole administration job attached.

Measure first

Watch the usage on what you have for a week, under real load rather than at a quiet hour. The figures to write down are the processor at peak, the memory in use when the cache is warm, and how much of the disk is actually touched. If the peak sits under half of a virtual plan's allowance, a bigger plan is the answer, not a different kind of machine. If it is pressed against the ceiling of the largest plan, send us those numbers with the quote request: a build chosen against measurements is cheaper than one chosen against a worry.

What is the same either way

Both hand you root and the whole job with it. Patching, firewalling, monitoring and backups are yours on a virtual server and yours on a physical one. The hardware and the hypervisor are ours, and on a dedicated machine the facility deals with a physical fault, but a repair returns a working machine rather than a working service, so keep a backup target that is not the box.

We use strictly necessary cookies to keep you signed in and remember your preferences. We would also like to measure how the site is used, but only with your agreement. Read our privacy policy