What people run on a VPS: scenarios and sizing
Find the workload closest to yours, then verify its configuration in a 5-hour trial period before you pay
This is not a wall of client logos — it is a breakdown of eight typical workloads: what the load looks like, where the bottleneck sits and which configuration clears it. The lightest case is a WordPress site: 4 vCPU, 4 GB RAM, 50 GB NVMe — the Standard 1 plan at €5.49/mo. The heaviest one covered here is several projects on a single machine: 20 vCPU, 32 GB, 300 GB NVMe — Power 4 at €36.99/mo. Every configuration comes from our own price list, and you can run any of them against your real load: VPS and cloud servers are handed over in trial mode for 5 hours before payment.
Workload → configuration → plan → price
A starting point for eight typical loads. Configurations and prices come from our price list.
| Workload | Configuration | Plan | Price, €/mo | |
|---|---|---|---|---|
| WordPress site or blog, a few hundred visits a day | 4 vCPU · 4 GB · 50 GB NVMe | Standard 1 | €5.49 | Order now |
| Online store with 2,000–5,000 products | 6 vCPU · 8 GB · 80 GB NVMe | Standard 3 | €8.99 | Order now |
| Backend API with its database on the same box | 8 vCPU · 8 GB · 100 GB NVMe | Standard 4 | €10.99 | Order now |
| Dev box: Docker, CI runner, staging | 8 vCPU · 12 GB · 120 GB NVMe | Standard 5 | €13.99 | Order now |
| Minecraft server for 20–40 players | 10 vCPU · 16 GB · 160 GB NVMe | Power 1 | €17.99 | Order now |
| Self-hosted PostgreSQL or analytics for a team | 12 vCPU · 16 GB · 200 GB NVMe | Power 2 | €19.99 | Order now |
| Scraping and automation with several browser workers | 16 vCPU · 24 GB · 240 GB NVMe | Power 3 | €27.99 | Order now |
| Several projects or microservices on one server | 20 vCPU · 32 GB · 300 GB NVMe | Power 4 | €36.99 | Order now |
These are typical configurations for a workload, not case studies of named clients: real resource use depends on your code, traffic and settings. Prices are from the current price list, billed monthly; paying yearly brings the monthly figure down by 18 %. Not sure which one fits — describe the task to support and we will help you size it.
Three families of workloads
Each has its own load profile — and its own page with the details.
Sites, stores, APIs
PHP-FPM, a database and static files on one machine. The bottleneck is memory for the database and disk latency, not core count: 4–8 GB of RAM on NVMe covers most projects.
Development, Docker, CI
A handful of containers, a build runner and staging side by side. Disk and memory run out first here: budget from 120 GB of NVMe for image layers and build caches.
Games and heavy compute
Single-threaded and stateful loads where core frequency and memory headroom matter more than core count. These land on Power plans with 16 GB and up.
How to size a configuration for your own task
The same order we used to build the scenarios above.
Find the bottleneck
Decide what your task actually depends on: CPU frequency, the amount of RAM, or disk speed. The plan is chosen by that one parameter, not by a vague sense of project size.
Add headroom on one parameter
There is usually a single bottleneck. Take headroom there and keep the rest minimal — resources can be raised later, and paying for everything up front makes no sense.
Verify under a real load
VPS and cloud servers are handed over in trial mode: 5 hours to check before payment. Run your own workload, not a synthetic benchmark.
Scale on evidence
Hit a limit — move to a higher plan. A dedicated server follows a different rule: payment comes first, and we help you pick the configuration beforehand.
Why that particular configuration
Six scenarios from the table, explained.
The bottleneck is not the CPU but memory for PHP-FPM and MySQL, plus disk latency on small random reads. 4 vCPU, 4 GB RAM and 50 GB NVMe (Standard 1, €5.49/mo) carry a site with a few hundred visits a day; as traffic grows, RAM is what asks for more first. Stack and setup details are in the WordPress VPS breakdown.
A catalogue lives or dies by the database: indexes have to fit in memory, otherwise every filter query hits the disk. 6 vCPU, 8 GB and 80 GB NVMe (Standard 3, €8.99/mo) is a working starting point. Heavier catalogues move the database to its own machine — see the Magento VPS breakdown.
The application and the database compete for the same cores, so take roughly twice the vCPU you think you need: 8 vCPU, 8 GB and 100 GB NVMe (Standard 4, €10.99/mo). Do not economise on disk — logs and the write-ahead log consume it faster than your code does. Details in the backend VPS breakdown.
Disk runs out before the CPU does: image layers and build caches grow quietly. 8 vCPU, 12 GB and 120 GB NVMe (Standard 5, €13.99/mo) hold a dozen containers plus a runner alongside. See the Docker VPS and GitLab VPS breakdowns.
A vanilla server is single-threaded, so core frequency and memory for the world and plugins matter more than core count. 10 vCPU, 16 GB and 160 GB NVMe (Power 1, €17.99/mo) cover 20–40 players with a modpack. Versions and tuning are in the Minecraft VPS breakdown.
A database server is sized by working set: the hot part of the data should fit in RAM, and the rest should sit on NVMe. 12 vCPU, 16 GB and 200 GB NVMe (Power 2, €19.99/mo) suit a team dashboard or a reporting replica. See the database VPS breakdown.
What these scenarios do not promise
A configuration from the table is a starting point, not a guarantee of the same result: every project has its own code, traffic and settings. We do not give a formal SLA on a single server — if a project needs high availability, we build a distributed fault-tolerant cluster across several data centres.
Automatic backups are not part of a plan: you take a backup yourself in the control panel in a couple of clicks. DDoS protection is a separate paid option matched to a specific service. You choose the image and install the OS yourself, with the KVM console as a safety net; turnkey setup is server administration from €79/mo.
Discuss your workloadFrequently asked questions
Did not find your answer?
Write to us through the form on the contacts page.
€5.49/mo — the Standard 1 plan: 4 vCPU, 4 GB RAM, 50 GB NVMe. That carries a site with a few hundred visits a day; as traffic grows, RAM is the first thing to add.
For 20–40 players, Power 1 at €17.99/mo: 10 vCPU, 16 GB RAM, 160 GB NVMe. A vanilla server is single-threaded, so memory headroom matters more than core count.
Standard 3 at €8.99/mo — 6 vCPU, 8 GB RAM, 80 GB NVMe — handles a catalogue of 2,000–5,000 products, provided the database indexes fit in memory.
No. These are typical configurations for a workload, not case studies of named clients: there are deliberately no company names, quotes or revenue figures here.
Yes, for VPS and cloud: the server is handed over in trial mode for 5 hours before payment. A dedicated server is prepaid, but support helps you size it first.
No, automatic backups are not part of the plan. You take a backup yourself in the control panel in a couple of clicks — there is nothing to configure.
We do not give a formal SLA on a single server. If a project needs high availability, we build a distributed fault-tolerant cluster across several data centres.
Yes. Start smaller and raise vCPU, RAM and disk as the real load shows up — moving between plans costs less than paying for headroom you never use.