Programming · Hosting · infrastructure
What is a VPS?
Once you've built something — a website, an API, a bot, or a containerised app — it needs somewhere to run that you control. For most developers, the answer is a VPS. This guide explains what a VPS is, how it works, how it compares to other hosting, and when it's the right choice.
The short definition
A VPS — virtual private server — is your own isolated portion of a physical server, with dedicated CPU, memory and storage, and full administrator (root) access. One physical machine is split into several virtual servers, each behaving like an independent computer with its own operating system. You get the control of a dedicated server at a fraction of the cost, because you share the underlying hardware without sharing your slice of it.
How it works: virtualization
A VPS is created through virtualization. Software called a hypervisor runs on the physical server and divides it into multiple isolated virtual machines, each allocated a guaranteed share of the hardware. Your VPS can't be slowed down by another customer hogging resources (unlike basic shared hosting), and you can install whatever operating system and software you like, because you have root access. It's the same virtual-machine idea that underpins cloud computing.

VPS vs the alternatives
- Shared hosting — many sites share one server and its resources, with no root access. Cheapest and simplest, but limited and easily affected by neighbours. Fine for a basic site, not for running your own stack.
- VPS — a guaranteed slice with root access and isolation. The sweet spot of control versus cost for most developer projects.
- Dedicated server — a whole physical machine to yourself. Maximum power and isolation, at a much higher price; overkill until you genuinely need it.
- Cloud servers — VPS-like instances you can spin up, scale and pay for by the hour, often with extra managed services. More elastic, sometimes pricier for steady workloads.
What you use a VPS for
A VPS is the general-purpose home for things you build: hosting websites and web apps, running an API or backend, deploying Docker containers (or even a small Kubernetes node), running bots, cron jobs, a Git server, or a personal VPN. Anything that needs to be online 24/7 and that you want full control over is a good fit.
Managed vs unmanaged
This is the choice that trips people up. An unmanaged VPS gives you a bare server — you handle the operating system, updates, security and backups yourself. It's cheaper and more flexible, but you are the system administrator. A managed VPS costs more but the provider handles maintenance, patching and support, which is worth it if you'd rather not run a server. Pick based on how much sysadmin work you want to own.
The honest trade-offs
A VPS gives real control, but with responsibility. On an unmanaged box, security is on you: unpatched software and weak SSH settings are how servers get compromised. Resources are guaranteed but finite — you size the plan to your workload and scale up when needed. And there's a learning curve to the command line and Linux administration. For most developers, though, that control is exactly the point, and the skills transfer everywhere.
Frequently asked questions
What is a VPS in simple terms?
A VPS is your own private slice of a physical server. One real machine is divided by software into several isolated virtual servers, and you rent one — with guaranteed CPU, memory and storage, your own operating system, and full administrator access — so it behaves like a dedicated computer at a much lower cost.
What is the difference between a VPS and shared hosting?
Shared hosting puts many websites on one server with pooled resources and no root access, so you're limited and can be affected by other users. A VPS gives you a guaranteed, isolated share of resources plus full root access, so you can install your own software and run your own stack without interference.
What is the difference between a VPS and a dedicated server?
A VPS is a virtual slice of a shared physical machine; a dedicated server is an entire physical machine reserved for you. A dedicated server offers more raw power and isolation but costs much more. A VPS gives most of the control at a fraction of the price, which is enough for the large majority of projects.
Do I need to be a sysadmin to use a VPS?
For an unmanaged VPS, you handle the OS, updates and security yourself, so basic Linux and command-line skills help. If you'd rather not, a managed VPS hands maintenance and support to the provider for a higher price. Either way, the core skills are very learnable and widely useful.
A VPS to run your projects
A VPS or cloud server gives you full root control to host sites, APIs, containers or a personal VPN. Infomaniak — a Swiss, privacy-respecting provider — offers VPS and cloud servers to deploy what you build.
See Infomaniak Cloud →Affiliate link — it supports these free guides.
Browse more clear explainers in our guides index.