Also known as: VPS
A virtual private server (VPS) is a slice of a physical server that behaves like your own machine, complete with root access.1
Overview
A VPS sits between shared web hosting and a whole dedicated server: more control than the former, far cheaper than the latter. It is created by virtualization — a hypervisor divides one physical host into several isolated virtual machines, each with its own operating system, kernel, and root account.
The isolation is logical rather than physical: neighbors share the same silicon, so a very busy tenant can in principle contend for CPU or disk (the “noisy neighbor” effect), though providers cap and balance resources to limit it. Providers like DigitalOcean, Linode, and Hetzner rent these by the month, and can resize or snapshot them far faster than any physical box.
When to choose it
The VPS is the middle rung of the hosting ladder, and the choice is usually against its neighbors:
| Option | Control | Cost | Performance |
|---|---|---|---|
| Shared hosting | Low (no root) | Lowest | Shared, variable |
| VPS | Root, own OS | Moderate | Good, mostly isolated |
| Dedicated / bare metal | Full machine | Highest | Uncontended |
Reach for a VPS when shared hosting stops being enough: you need root access, custom services, or a specific software stack. The trade-off is responsibility — you manage the operating system, security updates, and backups yourself.
Where it fits
A VPS is the default first “real server” for most projects — enough control to run anything, cheap enough to leave on 24/7. For GopherTrunk this is a fine place to host the web console and store and serve decoded data, though like any virtual or remote server it still cannot capture RF, which needs a radio front end near the antenna.
Sources
-
Virtual private server — Wikipedia, on VPS hosting and the hypervisor model. ↩