Wetin Be VPS? Simple Explanation of How E Work

Wetin be VPS?

A VPS (virtual private server) na part of one real computer wey dey for data centre, dem rent am give you as if na your own complete machine. Software for that computer divide am into several independent servers, and you get one of dem: your own memory, your own disk, your own IP address, and root login wey let you install anything wey you want. E dey run all the time, and e dey answer for public address for internet.

Break the three words apart, and the product explain itself. Server na computer wey stay on and answer requests through network. Virtual mean say software create am. Your server na partition for one bigger physical machine. Private mean say na only you get that partition. Your files and programs wey dey run no dey visible to person wey rent the slice beside your own.

If you never get root access for anything before, na this last part matter pass. VPS na the first kind hosting wey make you be administrator of the machine. Nobody set anything up for you, and nothing stop you too.

Wetín hypervisor dey slice, and wetín e dey share

The program wey dey do the dividing na hypervisor. E dey run for physical machine, wey dem dey call host. E dey give each customer one set of pretend hardware: processor, memory block, disk, and network card. Dem install operating system for that pretend hardware, and e boot as if na real computer e own. That guest system na your VPS. KVM (kernel-based virtual machine) na the usual hypervisor for Linux hosts, while Xen, VMware ESXi and Microsoft Hyper-V dey do the same work.

Dem divide memory and disk by space. Dem divide processor by time. Na this difference dey explain most of the things wey later fit surprise people. The memory wey dem assign to you na memory wey no other guest fit take. Your disk na file or logical volume for the host storage, and e remain your own until you delete am. Your virtual cores na queues wey dey wait for the host real cores, and hypervisor dey decide thousands of times every second which guest go run next.

One command go tell you the kind virtualisation wey you buy.

systemd-detect-virt
uname -r

systemd-detect-virt dey print kvm for normal VPS. This mean say full hypervisor boot kernel wey belong to you alone. E dey print lxc, openvz or container for container virtualisation. For this setup, your server na fenced-off area inside the host own operating system, and every other customer for the machine dey share the kernel. E dey print none for bare metal. This difference get real effects because shared kernel na kernel wey you no fit change. You no fit load module. So in-kernel feature like the WireGuard VPN module go fail with Operation not supported, and uname -r go report version wey you no choose and wey you no fit upgrade.

Virtual for this place mean say na software create the server, instead of one physical machine wey dem reserve only for you.

Because software make up the server, e go dey ready about one minute after you pay for am. Nobody need rack hardware for you. Dem build am from template image, so rebuild fit put clean Ubuntu back within a few minutes. Mistake wey fit spoil physical installation fit cost you only one afternoon at most. Most provider panels fit also take snapshot of the disk before you try risky change, resize the plan with reboot, and move your guest to different hardware when the host underneath need maintenance.

The price come from the same thing: many customers dey pay for one physical machine at the same time. Na why VPS cost as e cost when you compare am with renting complete server.

The cost dey close to the benefit. Other customers dey share the hardware underneath, so busy neighbour fit affect you too. The section about limits below get the command wey fit measure am.

Wetin private mean for here?

Private mean isolation, and e good make we explain exactly how much. You get your own kernel, your own root filesystem, your own user accounts, your own process list, your own firewall rules, and your own IP address. Another customer for the same host no fit list your processes or read your files, because their guest no get route enter your memory or your virtual disk. Na two separate operating systems be dem wey just dey share one power supply.

Shared hosting dey work the other way. You get one directory for a machine wey dey serve hundreds of other websites, one control panel, and any software wey the provider choose to install. No apt install dey there, because installing one package go change the whole machine, and the whole machine no be your own to change. Shared hosting against VPS go through the trade-off in detail. For one line: shared hosting rent account give you, while VPS rent computer give you.

VPS spec sheet wey line-by-line

Dem dey sell every VPS with short list of numbers. Na mid-range plan like the kind providers dey advertise wey we go use as example below. These figures na the normal published values as of August 2026, no be quote.

[
  {
    "plan": "Example mid-range VPS",
    "vcpu_cores": 4,
    "ram_gb": 16,
    "nvme_gb": 160,
    "bandwidth_tb": 8,
    "ipv4_addresses": 1
  }
]

That one line na the whole product. Read am from left to right.

4 vCPU. vCPU (virtual central processing unit) na one thread for host processor wey hypervisor dey schedule for you. Unless plan talk say dedicated, na share of that thread you get, no be reservation. Inside the server, nproc dey print 4, while lscpu dey show model name wey fit be the real host CPU or generic QEMU model, depending on how dem configure the host.

16 GB of RAM. Memory na fixed reservation, and e also get fixed maximum. free -h dey report value wey small pass wetin you buy, near 15Gi for 16 GB plan, because kernel and some reserved memory regions dey subtract before Linux count wetin usable. When memory finish, you no fit borrow from host.

160 GB of NVMe. NVMe (non-volatile memory express) na the way drive dey connect inside host, and e dey much faster than SATA SSD wey older plans use. Your share go show as virtual disk, normally /dev/vda for KVM. df -h / dey show value wey small pass 160 GB, and free space figure dey lower again because ext4 dey reserve 5 percent of filesystem for root by default. Wetin SSD for SSD VPS actually mean and how to verify the disk wey dem sell you explain am more.

8 TB of transfer. Na data wey move every month, and dem usually count outbound traffic only. E na volume, while port speed na separate number, often 1 Gbit/s. If you pass the allowance, provider fit charge you or throttle traffic, so read that line before you host video. sudo apt install vnstat dey give you your own count with vnstat -m, starting from the day you install am.

1 IPv4 address. The address na your own for as long as you rent the server. You fit point domain to am, accept traffic for any port, and normally set reverse DNS record for provider panel, wey mail servers dey check. Very cheap plans sometimes put many customers behind one shared address. Dem dey call this NAT VPS, and then ip -4 addr show dey report private address like 10.0.0.5 while inbound ports dey limited.

Four commands go confirm wetin dem give you.

nproc
free -h
df -h /
ip -4 addr show

If any of dem no match the spec sheet pass the rounding wey we describe above, e make sense to open support ticket before you build anything for the machine.

Wetìn root access mean for real life

Root na the administrator account for Linux, and e user ID na 0. Run id -u and you go see 0 when you be root. Root fit install packages for the whole system, open ports below 1024 (kernel reserve dem for privileged processes, na why ordinary user no fit start web server for port 80), load kernel modules, replace kernel, read and edit any file for disk, and destroy the system with one careless command. Nobody go undo that for you.

The practical difference short. For shared hosting, you go open support ticket to ask for software. For VPS, you go type this.

sudo apt update
sudo apt install -y nginx
systemctl status nginx

systemctl status nginx suppose print active (running) within one or two seconds, and the server IP address for browser suppose show default nginx page. If status print failed, run journalctl -u nginx -n 50 and read the last lines, because service record why e refuse start. The common reasons na typo for config file, or another program wey already dey listen on port 80.

Root na also your complete security boundary, and e dey come as password wey provider generate. The first session for new server no be time to install applications. Create ordinary user, move your login go SSH key, and put firewall in front of the ports. The first ten minutes for new VPS na that checklist in order, SSH key basics explain the login itself, ufw firewall basics explain the ports, and least privilege users explain wetin your services suppose run as afterwards. Server wey get password login and no firewall go collect thousands of guessing attempts every day, and you fit monitor dem as dem dey arrive with journalctl -u ssh -f.

VPS get wetin be the limits?

The processor na shared, and you fit measure the sharing. Steal time na the portion of time wey your virtual CPU ready to run but e get nothing, because hypervisor give the physical core to another guest.

vmstat 1 5

The last column, st, na steal time. One or two percent for short bursts normal for any shared host. If e dey remain for double digits while your own processes dey idle, e mean say host don get too many workloads, and no tuning inside your server go fix am, because the waiting dey happen outside your server. How to benchmark VPS properly show how to prove am before you report am to provider. KVM and Xen guests dey report steal. For container virtualisation, e dey remain zero and e no tell you anything.

The memory fixed, and the limit dey come suddenly. When allocation fail, kernel OOM (out of memory) killer choose one process and end am with SIGKILL.

sudo dmesg -T | grep -i "out of memory"

One line fit explain outage wey otherwise go look like mystery:

Out of memory: Killed process 2412 (mysqld) total-vm:2183104kB, anon-rss:1897224kB, file-rss:0kB

The application's own log normally no talk anything, because SIGKILL no give process chance to write anything. The reason dey only inside kernel log. Plenty VPS images ship without swap file, and this make the limit harder still, so adding small swap file na common first change.

The disk fast and e shared. The host's NVMe quick, and your own portion dey compete with every other guest for input and output operations. Benchmark wey you run during quiet hour no be promise say the same machine go perform like that during peak time.

The hardware no be your own to touch. You no fit plug anything into am. No USB device, no capture card, and no graphics card unless the plan intentionally pass one through, and that one na separate and more expensive product: VPS wey get GPU.

Na exactly one copy dey. VPS na single machine. If host get fault, your server go dey down until host return, and nothing go fail over unless you build the failover yourself. Backups na your responsibility, so restic backups from VPS suppose dey setup list. Provider snapshot convenient, but e no be backup, because e dey on the same infrastructure as the thing wey e dey protect.

Support dey stop for hypervisor. For unmanaged plan, provider dey keep hardware, network, and virtualisation layer healthy. Everything from operating system upward na your work, including security updates. Managed and unmanaged hosting explain where that line dey, and unattended upgrades for Ubuntu na the smallest useful thing to switch on.

How VPS dey compare with the things wey people dey confuse am with

A virtual machine na the general idea, and VPS na one commercial form of am: virtual machine wey you rent every month, with operating system, public address and network already attached. A VPC (virtual private cloud) na private network inside bigger cloud, and servers dey live inside am, so e dey answer different question entirely. VPS against VM against VPC separate the three terms properly.

A dedicated server na the complete physical machine, without hypervisor or neighbours. E cost several times more every month, and na the correct option when steal time or disk contention be your real bottleneck. VPS against dedicated server list the points wey you need consider.

A VPN (virtual private network) share two letters with VPS and nothing else. VPN na encrypted tunnel between machines. VPS na machine, and one popular use for am na to run your own VPN, na from there the confusion start. VPS against VPN settle the two words.

Hardware wey you own, or hypervisor like Proxmox for machine wey dey your house, give you more resources for the money and residential connection wey many services dey treat with suspicion. Proxmox against VPS weigh power, noise and uptime against monthly fee.

Wetín people dey run for VPS?

The honest answer be anything wey fit run for Linux. Common choices na website with its database, private VPN, game server, status monitor, mail server, media library, or coding agent wey continue to work while your laptop dey closed. Everything wey you run dey listen on one port, so wetín port be for Linux na the next concept wey worth learning, and wetín you fit do with VPS get the longer list plus the resource cost of each one.

FAQ

VPS na the same thing as virtual machine?

VPS na virtual machine wey company rent give you, with operating system, public IP address, and monthly price attached. The underlying technology na the same. The words get different meaning: "virtual machine" describe any guest wey dey run for hypervisor, including one wey dey your own laptop, while "VPS" describe the product wey you buy. VPC na another different thing, private network inside cloud provider instead of server.

I need to know Linux before I fit use VPS?

You need small knowledge, and you fit learn the rest as you dey use am. The starting set na connecting with ssh, moving around with cd and ls, editing file with nano, installing software with apt, and reading logs with journalctl. Unmanaged VPS assume say na you go handle updates and firewall by yourself. If that one pass wetin you want, managed plan or control panel go handle part of am for higher monthly price.

Why my VPS dey show RAM wey small pass wetin the plan promise?

Linux dey report usable memory, while the plan dey advertise assigned memory. The kernel image and some reserved memory regions dey subtract before dem calculate the total for free -h, so 16 GB plan normally go report about 15Gi. Difference of few hundred megabytes dey expected. Difference of several gigabytes no dey normal, and you fit open support ticket for that one.

Wetin be steal time, and I suppose worry about am?

Steal time na the percentage of time wey your virtual CPU ready to run but need wait, because hypervisor give the physical core to another guest. The st column of vmstat 1 dey show am. One or two percent for short bursts normal for shared hardware. Sustained double-digit figure while your own load low mean say physical host get more workload than e fit handle, and the fix na different host or different plan, because nothing inside your server control the host scheduler.

I fit run more than one service for one VPS?

Yes. Na the reason root dey available: the machine na general-purpose, and services fit coexist as long as dem fit inside memory and each one dey listen on e own port. Memory usually na the first limit wey you go meet, and disk speed na the second. Mail na the awkward exception, because delivery depend on the reputation of your IP address, and fresh address from hosting provider often start with large mail systems distrusting am.