What Is a VPS? A Plain-English Guide for Developers
What a VPS actually is, how virtualisation divides a physical server, what you get and what you're responsible for, and how a VPS compares with shared and managed hosting.
On this page
“Get a VPS” is common advice for developers who’ve outgrown free platforms or shared hosting. But what exactly are you getting, and what are you signing up to manage? This guide explains VPS hosting in plain terms and helps you decide whether it’s right for your project.
A VPS in one sentence
A Virtual Private Server is a slice of a powerful physical server that behaves like your own separate computer: its own operating system, its own reserved resources, its own IP address and full administrator (root) access.
How it works
A data centre runs large physical servers — many CPU cores, lots of RAM, fast storage. Software called a hypervisor divides each one into several virtual machines. Each virtual machine gets:
- a set number of virtual CPUs (vCPUs),
- a fixed amount of RAM,
- its own disk space,
- one or more IP addresses,
- and runs its own operating system kernel.
To you, it looks and feels like a dedicated machine. You connect over SSH, install whatever you want and configure it however you like. Other VPSes on the same host can’t see your files or processes.
The virtualisation technology matters. KVM — used by Kerit Cloud’s VPS plans — is full hardware virtualisation: each VPS runs its own kernel with dedicated resources, so you can run Docker, custom kernels modules, VPNs and anything else a real server can. Older container-based approaches share the host’s kernel and restrict what you can do. See KVM vs containers.
What you get
- Root access. Install any software, open any port, run any process.
- Reserved resources. The RAM and disk are yours; CPU is allocated as vCPUs.
- A dedicated IP address. Your own public IPv4 (and often IPv6), useful for hosting websites, game servers and services with their own domains.
- Your choice of OS. Commonly Ubuntu, Debian, AlmaLinux or Rocky Linux — or your own ISO.
- Always on. No sleeping, no idle timeouts.
What you’re responsible for
This is the part to take seriously. With a VPS, you are the system administrator:
- Security updates for the OS and every package you install.
- Firewall configuration and SSH hardening — see securing a fresh Ubuntu VPS.
- Process supervision — making sure your apps restart after crashes and reboots, with systemd, PM2 or Docker.
- Backups of your data and configuration (though many providers, including Kerit Cloud, include automated snapshots).
- Monitoring — noticing when disk fills up or memory runs out.
None of this is difficult, but it’s ongoing. If you’d rather not do it, managed hosting handles it for you.
VPS vs other hosting types
| Shared hosting | Managed app/bot hosting | VPS | Dedicated server | |
|---|---|---|---|---|
| Root access | No | No | Yes | Yes |
| Your own IP | Usually shared | Varies | Yes | Yes |
| Resources | Shared, limited | Allocated per plan | Reserved slice | Entire machine |
| Maintenance | Provider | Provider | You | You |
| Flexibility | Low (usually PHP sites) | Medium (specific workloads) | High | Highest |
| Cost | Lowest | Low | Low–moderate | High |
Shared web hosting runs many websites on one server with a control panel like cPanel. It’s great for PHP websites and useless for bots or game servers — see shared web hosting vs bot hosting.
Managed hosting — like Kerit Cloud’s Discord bot, Lavalink or database plans — runs one kind of workload for you with a panel, automatic restarts and no server administration.
A dedicated server gives you the whole physical machine — maximum performance and isolation at a much higher price. See KVM VPS vs dedicated server.
What people run on a VPS
- Several bots and services together — Discord and Telegram bots, APIs and a database on one machine.
- Websites and web apps behind Nginx with free TLS certificates.
- Game servers and game server panels like Pterodactyl.
- Self-hosted Lavalink or other audio nodes.
- VPNs such as WireGuard.
- Development and staging environments.
- Docker-based stacks of any kind.
Understanding VPS specs
- vCPU — a virtual CPU core. Performance depends heavily on the underlying processor; a vCPU on a modern high-clock CPU like the AMD Ryzen 7 5700X (up to 4.6 GHz boost) handles single-threaded work very well. See Ryzen 7 5700X VPS: who it’s for.
- RAM — how much memory your processes can use. The OS itself takes a few hundred megabytes.
- Storage — NVMe is dramatically faster than SATA SSD or hard drives. See NVMe vs SATA SSD vs HDD.
- Bandwidth — monthly data transfer allowance, and the port speed.
- Location — affects latency to your users. See why Miami?.
Kerit Cloud’s VPS plans
Kerit Cloud offers KVM VPS hosting on AMD Ryzen 7 5700X processors in a tier-3 data centre in Miami, Florida:
| Plan | vCPU | RAM | NVMe (PCIe 4.0) | Bandwidth | Price |
|---|---|---|---|---|---|
| Nano | 1 | 2 GB DDR4 | 25 GB | 1 TB | $4.99/mo |
| Basic | 1 | 4 GB DDR4 | 50 GB | 2 TB | $7.99/mo |
| Plus | 2 | 8 GB DDR4 | 80 GB | 3 TB | $11.99/mo |
| Pro | 4 | 16 GB DDR4 | 120 GB | 5 TB | $19.99/mo |
Every plan includes a dedicated IPv4 address and a /64 IPv6 subnet, daily automated off-site backups with one-click restore, Cloudflare Magic Transit DDoS protection with OVH TCP Shield (17+ Tbps), a control panel with a web VNC console and ISO mounting, and a 99.99% uptime target. See the VPS plans.
Is a VPS right for you?
Choose a VPS if you want to run several different things together, need root access or custom software, want your own IP, or enjoy learning how servers work.
Choose managed hosting if you’re running one kind of workload — a bot, a Lavalink node, a database — and would rather not manage an operating system. Managed bot hosting vs a VPS goes deeper.
Summary
A VPS is a virtual machine on a shared physical server that behaves like your own computer: reserved resources, a dedicated IP, your choice of OS and full root access. That flexibility comes with responsibility for updates, security, supervision and backups. It’s ideal for running several services together or anything that needs root, while managed hosting suits single workloads you’d rather not administer.