A VPS is a whole machine that belongs to you alone: your own operating system, your own root access, your own memory that nobody else can take. The only hard question when you buy one is how big to make it. Guess high and you pay every month for capacity that sits idle. Guess low and the machine starts killing your own processes at the worst possible moment. Here is how to work it out instead of guessing.
Memory is the number that actually decides it
Of the three numbers on a plan — memory, disk, cores — memory is the one that will hurt you first. When a Linux server runs out of it, it does not slow down politely. It picks a process and kills it, and the process it picks is usually the biggest one, which is usually your database.
A small site on WordPress or a similar CMS, with a database on the same machine, is comfortable in 2 GB. A shop with a few thousand products, a search index and a cache wants 4 GB. If you are running several sites on one machine, add roughly a gigabyte per site rather than hoping they will share.
The rule that saves the most trouble: whatever the machine uses when it is busy, buy the next size up. Not because you need the headroom every day, but because you need it on the day traffic triples and you have no time to resize.
Cores matter less than you think, until they suddenly matter
Two cores handle far more than most people expect. A web server spends most of its life waiting — for the disk, for the database, for the visitor's browser — and waiting does not consume a core.
What does consume cores is work that has no waiting in it: resizing images, encoding video, building a site on every deploy, running a background job queue. If any of that describes you, count those jobs and give each one a core. If none of it does, two cores is a reasonable place to start.
Disk: measure what you have, then double it
Disk is the easiest number to estimate because you can simply look. Add up your files, your database, and the space your backups take, then double the result. The doubling is not padding: a database needs temporary room to rebuild an index, a system update downloads before it installs, and a log file nobody is watching can fill a partition in a week.
A disk that reaches one hundred per cent is not a slow server, it is a stopped one. Databases refuse to write, sessions break, and the fix usually needs the very disk space you do not have.
You can change your mind later
None of these decisions are permanent. A VPS can be resized, and moving up a plan takes a reboot, not a migration. That is the practical difference between a VPS and a physical server, and it is a good reason not to agonise over the first choice.
What we would not recommend is buying the largest plan on day one to be safe. You will learn more about what your machine actually needs in its first month of real traffic than in any amount of planning beforehand.
Where the machine lives
Our virtual servers run in EU data centres, on modern hardware with NVMe storage. For visitors in Georgia and the region that means the connection is fast, and it also means your data sits under EU rules rather than somewhere with none.
Every server comes with full root access, a console you can open from your account in this portal even when the network is broken, and the ability to reinstall the operating system yourself without asking anyone.