A VPS (virtual private server) is a virtual machine running on a physical server in a data center. It behaves like your own computer on the internet: it has its own operating system, its own IP address, guaranteed CPU, memory and storage, and you have full administrator (root) access to install whatever you want.
How a VPS works
A powerful physical server — many CPU cores, lots of RAM, fast SSDs — runs a hypervisor. The hypervisor divides the hardware into several isolated virtual machines. Each one:
- runs its own kernel and operating system (Ubuntu, Debian, AlmaLinux, Windows Server…);
- gets a defined share of CPU cores, RAM and disk;
- has its own network interface and public IP address;
- can be rebooted, reinstalled or reconfigured without affecting the others.
With KVM — the virtualization built into the Linux kernel, and what VPS.DO uses — each VPS is a full virtual machine. You can load kernel modules, run Docker, set up VPNs, change kernels and install Windows. Older container-based technologies like OpenVZ share one kernel between all customers and are far more restricted. See KVM vs OpenVZ vs LXC.
An analogy
- Shared hosting is a room in a shared house: cheap, but you share the kitchen and can’t renovate.
- A VPS is an apartment: your own space and keys, walls between you and neighbours, but the building’s infrastructure is shared.
- A dedicated server is a whole house: everything is yours, at a higher price.
What can you run on a VPS?
Practically anything a Linux or Windows server can run:
- Websites and online stores — WordPress, WooCommerce, Laravel, Next.js.
- Web apps and APIs in Node.js, Python, PHP, Go, Java or .NET.
- Databases: MySQL, PostgreSQL, MongoDB, Redis.
- Docker containers and self-hosted apps: Nextcloud, Vaultwarden, Uptime Kuma, n8n.
- A personal VPN server.
- Game servers for Minecraft, Valheim and others.
- Trading platforms such as MT4/MT5 on a Windows VPS, running 24/7 near the broker.
- Bots, scrapers, cron jobs, CI runners and development environments.
VPS vs other hosting types
| Shared hosting | VPS | Dedicated server | Public cloud VM | |
|---|---|---|---|---|
| Resources | Shared, not guaranteed | Guaranteed slice | Whole machine | Guaranteed slice |
| Root access | No | Yes | Yes | Yes |
| Install any software | No | Yes | Yes | Yes |
| Price | Lowest | Low–medium | High | Variable (usage-based) |
| Billing | Fixed | Fixed monthly | Fixed monthly | Per hour/second + traffic |
| You manage the OS | No | Yes (unmanaged) | Yes | Yes |
More detail: VPS vs shared hosting, VPS vs dedicated server and VPS vs serverless vs PaaS.
VPS specs explained
- vCPU cores — virtual CPU cores. More cores help with parallel work: many PHP workers, builds, databases under load.
- RAM — often the most important number. Web stacks, databases and Java apps are memory-hungry. See how much RAM a VPS needs.
- Storage — SSD space for the OS, applications and data.
- Bandwidth / traffic — how much data you can transfer per month, and the port speed. See VPS bandwidth explained.
- IP addresses — at least one dedicated IPv4 address.
- Location — the data center city. Pick one close to your users for low latency; see choosing a VPS location.
Managed vs unmanaged
Most VPS plans — including ours — are unmanaged (self-managed): the provider keeps the hardware, network and virtualization running; you manage the operating system and software. That gives you full control at a low price, but you’re responsible for updates, security and backups. A managed VPS adds administration by the provider at a higher cost. See managed vs unmanaged VPS.
If you’re comfortable with the command line — or willing to learn — unmanaged is the better value. Our blog has step-by-step guides for nearly everything.
Who should use a VPS?
A VPS is the right step when:
- your site has outgrown shared hosting (slow, resource limits, “too many processes”);
- you need software that shared hosting doesn’t allow (Node.js, Docker, custom PHP extensions);
- you want a dedicated IP, full control over security, or root access;
- you run something 24/7 that a home computer can’t do reliably.
Getting started
- Pick a location and plan (start small — you can upgrade later).
- Choose an operating system; Ubuntu LTS and Debian are the most beginner-friendly.
- Log in over SSH — see connecting to your VPS.
- Do the basic setup: updates, a sudo user, SSH keys, a firewall — our first 10 minutes on a new VPS guide walks through it.
- Install your stack.
VPS.DO offers KVM VPS in USA, Hong Kong and Japan data centers, with full root access, instant setup and a 7-day money-back guarantee — a low-risk way to try your first server.