DEV Community

Cover image for VPS vs VDS vs Colocation: which one does your workload actually need?
Michael
Michael

Posted on

VPS vs VDS vs Colocation: which one does your workload actually need?

"Should I get a VPS, a dedicated server or just colocate my own box?"

I work at a hosting company that sells all three, and this is the question we hear most. The honest answer is that none of them is better. They solve different problems. Here's how to tell which one is yours

The one-line version

  • VPS: a virtual server with shared CPU time. Cheapest. Good when your load comes in bursts.
  • VDS (virtual dedicated server): a virtual server with physical cores reserved for you. Steady performance under constant load.
  • Colocation: your own hardware in someone else's data center. You bring the server; they provide space, power, network and physical security.

VPS: shared vCPU

A VPS splits a physical host into virtual machines. Your RAM and disk are yours, but the processor time is shared with the other VMs on the same host. When your traffic spikes, you can borrow idle CPU. When your neighbours spike at the same time, you wait (that waiting shows up as st, "steal", in top).

Good for:

  • websites, blogs, small APIs
  • staging and dev environments
  • bots, cron jobs, internal tools
  • Docker or Coolify hosts for small projects

Watch out for:

  • performance that varies with time of day
  • confusing "more vCPUs" with "more guaranteed CPU": a bigger shared plan still has neighbours

Cost shape: lowest monthly price, no hardware to buy, online in minutes.

VDS: dedicated cores

Same idea as a VPS (virtual machine, root access, images, snapshots), but the physical cores behind your vCPUs are reserved for you. No other customer runs on them, so a request that takes 40 ms at 3 a.m. still takes about 40 ms at peak hours.

Good for:

  • databases under steady load
  • CI runners, builds, video encoding
  • game servers (players notice latency spikes before anything else)
  • ERP, CRM and business apps where "slow today" is a support ticket

Watch out for:

  • paying for dedicated cores your workload never uses. If your CPU graph is flat at 5% all day, a VPS is fine.

Cost shape: several times the per-core price of a VPS, still no hardware to buy, still online in minutes.

Colocation: your hardware, their building

With colocation you own the server. You ship it (or drive it) to the data center. They rack it, connect power and network, and keep the building secure and cooled. You manage everything from the OS up.

Good for:

  • workloads that run 24/7 for years, where owning the hardware is cheaper than renting it
  • specific hardware: lots of disks, GPUs, special NICs, or a server you already own
  • compliance or data-residency reasons for knowing exactly where the hardware sits
  • moving a server out of an office closet that keeps losing power or overheating

Watch out for:

  • Power. Plans come with a fixed amperage (1–2 A for a single server is common). Check your server's real draw, especially with GPUs.
  • Rails. Rack plans usually require a rails kit. Order it with the server.
  • Remote access. If a bad network change locks you out, you need a way back in that doesn't involve a truck. Look for an out-of-band console option (IPMI, iDRAC or iLO over a separate network).
  • Spare parts. Your hardware, your failed disk. Keep a spare drive and PSU in mind.

Cost shape: you buy the hardware once, then pay a monthly fee for space, power and network.

Side by side

VPS VDS Colocation
Who owns the hardware Provider Provider You
CPU Shared vCPU Dedicated cores Whatever you install
Performance under load Varies with neighbours Steady Steady (it's your box)
Time to get online Minutes Minutes Days (shipping and racking)
Upfront cost None None The hardware
Scaling Resize the plan Resize the plan Add servers or rack space
You manage OS and up OS and up Hardware, OS and up
Best when Load comes in bursts Load is constant Load is constant for years, or the hardware is special

Five questions that decide it

  1. Is your CPU busy most of the day, or in short bursts? Bursts → VPS. Busy → VDS or colocation.
  2. Does a slowdown cost you money or users? Yes → dedicated cores (VDS) or your own hardware.
  3. Do you already own the server, or need specific hardware? Yes → colocation.
  4. Will this workload exist, unchanged, in two years? Yes → do the rent-vs-own maths below.
  5. Who fixes it at 2 a.m.? If nobody on your team wants to handle hardware, stay virtual (VPS or VDS), or use colocation with a provider that offers out-of-band access and hands-on support.

Rent vs own: the maths

The break-even point is simple:

months to break even = hardware cost / (monthly rental price − monthly colocation fee)
Enter fullscreen mode Exit fullscreen mode

Hypothetical example: you rent a dedicated-core server for $160/month. A comparable server you buy costs $1,500, and a 1U colocation slot costs $69/month.

1500 / (160 − 69) = 1500 / 91 ≈ 16.5 months
Enter fullscreen mode Exit fullscreen mode

After about a year and a half, owning is cheaper, provided the workload stays the same and you're fine handling hardware. If the workload might change or disappear in a year, renting wins. Put your own numbers in. That's the whole point.

Where Avant fits

Disclosure first: this is the company I work for. The prices below are what's on our site today.

VPS: shared vCPU (Flint, MI in USD, or Sofia, Bulgaria in EUR excl. VAT)

Plan vCPU RAM SSD Monthly 12 months upfront
VPS-1 1 2 GB 40 GB $5 $36
VPS-2 2 4 GB 80 GB $8 $57.60
VPS-4 4 8 GB 160 GB $16 $115.20
VPS-8 8 16 GB 320 GB $32 $230.40

Larger tiers go up to VPS-32 (32 vCPU, 64 GB, $128/mo).

VDS: dedicated cores (Flint or Sofia)

Plan Cores RAM SSD Monthly 12 months upfront
VDS-2 2 8 GB 100 GB $40 $288
VDS-4 4 16 GB 200 GB $80 $576
VDS-8 8 32 GB 400 GB $160 $1,152

Larger tiers go up to VDS-32 (32 cores, 128 GB, $640/mo)

Both include full root access, one public IPv4, and free Linux images (Ubuntu, Debian, AlmaLinux, Rocky), with Docker, Coolify and CloudPanel ready to go. Windows Server is $5 per vCPU or core per month.

How you pay (same on VPS and VDS, discounts don't stack):

  • Monthly: every 4th month is free while the subscription stays active
  • 6 months upfront: 30% off, and it renews at that rate
  • 12 months upfront: 40% off, and it renews at that rate

Colocation (Phoenix, Flint, Ashburn, Sofia; Singapore coming soon)

  • Mini PC $35/mo, Tower $65/mo, Full Tower $75/mo in Flint (Sofia: €34, €64, €74)
  • 1U $69/mo, 2U $79/mo, 4U $99/mo (all US sites)
  • Private racks: quarter, half and full. In Flint these are $330, $530 and $930/mo; Phoenix and Ashburn are priced higher.
  • Every plan has a 1 Gbps port, IPv4 addresses (2 to 60 depending on the plan), a /64 of IPv6, and an Out-of-Band VPN option, so you can reach the console when the main network path is down.

Links:

Not sure which one fits? Leave a comment with your workload and I'll tell you honestly, even if the answer is "a $5 VPS is plenty"


Top comments (0)