Price per gigabyte of RAM and price per vCPU are the two ratios that make plans comparable. In 2026, a reasonable budget Small plan lands near $3–$5 per GB of RAM and $4–$8 per vCPU. A plan 40% below those bands is not a bargain; it is either oversubscribed, running older hardware, or priced as an introductory rate. Before you pay, divide the renewal price — not the first-month price — by the RAM and see where it lands.
The other check is what is missing from the base price: backups, a second IPv4, snapshot storage, and any control panel licence. These add $2–$8 per month in total, which can be 60% of a $5 plan. Add them before comparing providers, or you will be comparing a complete offer against an incomplete one.
The Decision Order That Avoids Rework
- Compute the four numbers. If you cannot, measure a week of current traffic first.
- Pick RAM from the bottom-up stack table; this removes most plans from consideration immediately.
- Pick disk for month twelve, with 20% free space.
- Check transfer against measured egress, not the advertised cap.
- Only then look at CPU, and choose by single-core score rather than core count.
- Add the true cost of backups, IPs and panels before comparing.
Following that order typically moves a buyer from a 4 GB plan at $20 to a 2 GB plan at $7 that performs identically for the workload, or from a $3 plan that thrashes to a $7 plan that does not. Both directions are savings; only one of them is visible on the pricing page.
Choosing a VPS plan at a fixed budget is mostly an elimination exercise. Most buyers start from the price and work outward, which is how people end up paying for 4 GB of RAM they never touch while running out of disk in month five. Start from the workload, convert it into four numbers, then find the cheapest plan that clears all four. The order matters because the numbers fail in a predictable sequence.
Step 1: Convert Your Workload Into Four Numbers
Before looking at any plan, write down these four figures for your project. If you do not know one, the estimate below is close enough to start.
| Number | How to estimate it | What it sizes |
|---|---|---|
| Peak concurrent requests | Monthly visits × 3 peak factor ÷ 2,592,000 × average page views | PHP workers, vCPU |
| Resident memory per request | Measure one PHP-FPM worker RSS under load, typically 40–90 MB for WordPress | RAM ceiling |
| Data growth per month | Uploads + database growth + logs, measured over a week and multiplied | Disk |
| Monthly egress | Page size × views, plus downloads and API traffic | Transfer quota |
A worked example: 30,000 monthly visits, 1.8 pages per visit, average page weight 1.4 MB. That is 54,000 pageviews and about 76 GB of raw egress — call it 90 GB with assets cached imperfectly. A plan advertising 1 TB of transfer clears this by a factor of ten, so transfer is not the constraint and you should stop optimising for it. Peak concurrency is roughly 54,000 × 3 ÷ 2,592,000 × 1.8 ≈ 0.11 requests per second sustained, with bursts to perhaps 5–8 simultaneous during a crawl. RAM, not CPU or bandwidth, is the binding constraint at this scale.
Step 2: Budget the RAM From the Bottom Up
The most reliable sizing method is to add up what the stack actually needs at rest, then add workers. At idle, a LEMP stack on Debian looks like this:
| Component | Idle RSS | Notes |
|---|---|---|
| OS + sshd + systemd | 120–180 MB | Ubuntu higher than Debian minimal |
| MariaDB / MySQL | 150–400 MB | Depends on innodb_buffer_pool_size |
| Nginx (master + workers) | 15–30 MB | Scales with worker count, not traffic |
| PHP-FPM master + 3 children | 150–280 MB | 40–90 MB per worker |
| Redis (optional) | 10–40 MB | More with object cache enabled |
| Headroom for page cache | 150–300 MB | Do not fill RAM to 100% |
That totals roughly 600–900 MB for a small WordPress site, which is why 1 GB plans work and 512 MB plans do not. The number that changes with traffic is the PHP-FPM child count, and it is capped by RAM, not by CPU. A useful rule for 1 GB: three children, four at the absolute most. For 2 GB: six to eight. Anything more and the OOM killer will do the capping for you, less politely.
Step 3: Size Disk With a Year of Headroom
Disk is the resource budget buyers most often misjudge, because people size for day one rather than month twelve. Plan for the following footprint:
- Base OS: 2–3 GB Debian, 6–8 GB Ubuntu server.
- Stack packages: 1–2 GB for nginx, PHP, MariaDB and certbot.
- Application: 300 MB–1 GB for a typical WordPress install with plugins.
- Uploads and database: your measured monthly growth × 12, plus 30%.
- Logs and backups: 2–4 GB if capped properly, unlimited if not.
- Free space to keep: 15–20% of total, so MySQL does not stall on a full filesystem.
A site growing 1.5 GB per month needs about 30 GB of usable space to reach its first anniversary comfortably. That points to a 40 GB plan, not the 20 GB plan that looks adequate on signup day. Upgrading storage later is almost always more expensive than buying it upfront, and on many providers it requires a migration.
Step 4: Choose the Plan Shape, Not the Plan Size
Once you have the four numbers, match them against real plan shapes. The table below reflects the budget market in 2026 and is the same set of options summarised in our budget VPS comparison table.
| Shape | Typical specs | Fits | Fails at |
|---|---|---|---|
| Micro | 1 vCPU, 512 MB–1 GB, 10–20 GB | Proxy, VPN, bot, static site | Anything with a database |
| Small | 2 vCPU, 2 GB, 40 GB NVMe | Cached CMS, small API | Uncached dynamic traffic above ~50k views |
| Standard | 4 vCPU, 4–8 GB, 80–160 GB | WooCommerce, Docker host, staging + prod | Search clusters, video transcoding |
| Large | 8+ vCPU, 16 GB+ | Multiple services, real databases | Nothing at typical small-site scale |
Step 5: Sanity-Check the Price Against the Shape
Price per gigabyte of RAM and price per vCPU are the two ratios that make plans comparable. In 2026, a reasonable budget Small plan lands near $3–$5 per GB of RAM and $4–$8 per vCPU. A plan 40% below those bands is not a bargain; it is either oversubscribed, running older hardware, or priced as an introductory rate. Before you pay, divide the renewal price — not the first-month price — by the RAM and see where it lands.
The other check is what is missing from the base price: backups, a second IPv4, snapshot storage, and any control panel licence. These add $2–$8 per month in total, which can be 60% of a $5 plan. Add them before comparing providers, or you will be comparing a complete offer against an incomplete one.
The Decision Order That Avoids Rework
- Compute the four numbers. If you cannot, measure a week of current traffic first.
- Pick RAM from the bottom-up stack table; this removes most plans from consideration immediately.
- Pick disk for month twelve, with 20% free space.
- Check transfer against measured egress, not the advertised cap.
- Only then look at CPU, and choose by single-core score rather than core count.
- Add the true cost of backups, IPs and panels before comparing.
Following that order typically moves a buyer from a 4 GB plan at $20 to a 2 GB plan at $7 that performs identically for the workload, or from a $3 plan that thrashes to a $7 plan that does not. Both directions are savings; only one of them is visible on the pricing page.
