Budget VPS shopping usually starts with the sticker price, and that is where most buyers stop thinking. A $3.50 plan with 1 GB of RAM and a $7 plan with 4 GB are not competing on the same terms once you divide cost by memory. Doing that division takes two minutes and changes the order of almost every host comparison you will run this month.
Price per GB of RAM is a single number that makes wildly different plans comparable. It is not the only number that matters, but it is the fastest filter for cutting a 40-host shortlist down to six. Below is how the arithmetic works, where it misleads, and how to read it next to CPU, disk and transfer.
The basic arithmetic, worked through
Take the monthly price in dollars and divide by the RAM figure in gigabytes. A $2.99 plan with 512 MB of RAM works out to $5.98 per GB. A $4.50 plan with 1 GB is $4.50 per GB. A $9 plan with 2 GB is $4.50 as well, so the cheaper sticker is actually the worse value per gigabyte.
Run that on real Linux and the pattern repeats often enough to be useful. Entry plans price memory at $2 to $7 per GB because hosts know small buyers compare the headline number. Everything from 2 GB to 8 GB usually settles between $3 and $5 per GB, and the best value zone on most of the market sits at 2 GB to 4 GB.
Why the small plans lose on this metric
Every virtual machine carries fixed costs a host cannot spread thinner: an IPv4 address, a slice of disk, snapshot space, panel overhead and support hours. On a 512 MB plan those costs eat most of the revenue, so the provider charges more per gigabyte to stay profitable. That is a structural fact, not a rip-off.
The practical consequence is that stacking two $2.99 micro-plans to get 1 GB rarely beats one $4.50 plan. You pay two IP addresses, two sets of disk overhead and double the management work. Only buy micro-plans when you specifically need separate machines for isolation, not when you are trying to reach a memory figure.
Where price per GB hides a CPU trap
Memory is the easiest spec to pad, and some hosts do exactly that. A 4 GB plan at $8 per GB? No — a 4 GB plan at $6 a month looks strong until you see it ships with a single shared vCPU. The per-GB number is excellent, but you cannot push 4 GB of memory through one contended core.
Check the vCPU count and the generation of the CPU before you accept a low per-GB figure. Current-generation cores at a 3:1 or 2:1 memory-to-core ratio are a sane balance for web workloads. Plans that go beyond 4:1 usually mean the host expects you to leave most of that memory idle.
NVMe, SATA and the disk factor
Disk type moves value far more than most buyers realise. Two hosts both quoting $4 per GB can differ by 5x in storage speed, so a database on the slower one needs more memory headroom to compensate. When you compare, pair the per-GB figure with the storage type and the disk size in the same table row.
A useful secondary metric is price per GB of RAM per GB of storage. Take $6.00 a month, 2 GB RAM, 50 GB NVMe: that is $3.00 per GB RAM and 25 GB disk per GB of RAM. Plans falling under 15 GB of disk per GB of RAM tend to run out of room before they run out of memory, which forces an early upgrade you did not budget for.
Building a normalised comparison table
Sort your shortlist into five columns: price, RAM, vCPU, disk, transfer. Add a sixth column for price per GB RAM and a seventh for monthly cost at 12-month billing versus monthly billing. The annual figure matters because most budget hosts discount 20 to 40 percent for prepayment, and that discount does not fall evenly across plans.
Our comparison table lists plans with RAM, vCPU and disk side by side for exactly this reason. Once the columns are aligned, hosts that looked cheap at first glance frequently land in the bottom half, and the mid-tier 2 GB NVMe plans that seemed expensive turn out to be the best dollars-per-gigabyte buy on the page.
Annual billing skews the number
Per-GB figures computed on monthly pricing can mislead you into a host that only looks competitive for one billing cycle. A plan at $6 monthly and $48 annually is $4.00 per GB per month at 2 GB, but a $5 monthly plan with no annual discount stays at $5.00. Prepayment rewards you only if you are confident the host will still exist in ten months.
A reasonable compromise for budget buyers is to compute price per GB on the annual rate, then add a risk premium of 10 to 15 percent for unknown providers. That keeps the metric honest without pushing you toward hosts with the longest lock-in and the thinnest track record.
When to ignore the metric entirely
Memory-heavy work loads flip the logic. A Postgres instance, a Java service using a 3 GB heap or a Docker host running six containers cares about absolute memory availability and non-swappable performance, not the per-GB discount. In those cases pick the plan that fits with 30 percent headroom and stop optimising.
For light workloads, price per GB is a sharp filter. For production databases and multi-tenant hosts, it is a tiebreaker at most. Treat the number as the start of the conversation about a plan, not the end of it, and you will avoid both overpaying for tiny plans and under-specifying the machine that actually runs your site.
Compare prices per gigabyte across current offers in our VPS plan breakdown, then check the vCPU and disk columns before you commit. A few minutes with a spreadsheet beats a year of regret on a plan that was cheap per gigabyte and short on everything else.
