Small VPS bills in 2026 are not dominated by the CPU line. Inventory a $22/month stack — instance, snapshots, a second IPv4, block storage, a backup volume — and compute is $8 to $10 of it. The rest is storage and features you enabled in the first ten minutes of setup and never audited again.
That distribution is why a 30-50% cut is realistic without a worse provider or degraded performance. There are seven levers on a VPS bill and they are not equal: two deliver more than the other five combined. This ranks them by dollars saved per hour of work on a $22 baseline.
The baseline: what a typical $22 stack is composed of
A concrete example: 2 vCPU / 4 GB at $14, snapshot storage $2, block storage $3, a second IPv4 $2, an upsized backup volume $1 — $22. Two lines are capacity you chose, three are defaults. The audit question is which lines below compute still describe your workload.
Get the invoice into a spreadsheet first; the ranking only means something if you know which line each saving lands on. Compare current plan pricing on our provider comparison table to see how the same 2 vCPU / 4 GB shape prices elsewhere.
Lever 1: right-size the instance against measured memory, not the upgrade screen
This is the largest single lever, worth $4 to $7 a month on a typical stack. Most over-provisioned instances are over-provisioned for peak memory that occurs for ninety minutes a week — a nightly import, a backup compression, a build. The rest of the time the instance idles at 55% of its RAM and you pay for the peak.
Measure it properly. Collect MemAvailable and pgmajfault every minute for two weeks, drop the top 1% of samples, and size to the p99 of the remainder plus 20%. On the example stack, p99 memory sits at 2.4 GB, so a 3 GB plan is defensible and a 4 GB plan is not. Save the peak for the job that needs it, not the instance that hosts it.
# two-week memory profile, 1-minute resolution
while true; do
awk '/MemAvailable/{a=$2} /pgmajfault/{print systime(), a, $2}' /proc/meminfo /proc/vmstat
sleep 60
done >> mem-profile.tsv
# p99 of available memory (KB), ignoring the top 1%
sort -k2 -n mem-profile.tsv | awk '{v[NR]=$2} END{print v[int(NR*0.99)]}'Lever 2: move snapshots to object storage and cap retention
Provider snapshot storage is priced at a convenience premium — commonly $0.05 to $0.10 per GB-month, against $0.005 to $0.015 for object storage at a dedicated S3-compatible provider. A 400 GB weekly snapshot set on the second pricing costs $80 a month; the same data pushed as encrypted tarballs to object storage costs under $5. This lever is worth $15 to $40 on stacks that keep long histories.
The trade-off is restore time, which is real and should be measured before you switch. The table below compares snapshot storage cost and restore effort for a 400 GB working set.
| Method | Monthly cost (400 GB) | Retention kept | Restore time |
|---|---|---|---|
| Provider snapshots, 8 weekly | $160-$320 | 8 weeks | 3-6 min |
| Provider snapshots, 2 weekly | $40-$80 | 2 weeks | 3-6 min |
| Object storage, 30 daily | $5-$12 | 30 days | 12-25 min |
| Object storage, 3 daily | $2-$4 | 3 days | 12-25 min |
Lever 3: kill the second IPv4 and the managed DNS add-on
Extra IPv4 addresses cost $1-$3 each and most stacks have one serving a leftover project. Audit reverse DNS, firewall rules, and records; if nothing resolves to it, release it. Managed DNS at $3-$5 is the same story — a secondary resolver on the same instance covers it.
Lever 4: consolidate underused instances onto one
Three $6 instances at 12% CPU each are a $18 bill running the work of one $10 instance. The consolidation lever is worth $6 to $12, and it is the one people resist because separation feels like safety. In practice two small services on one 2 GB instance with hard container memory limits are more reliable than two 1 GB instances that each swap under load.
Consolidate low-traffic services first: cron runners, webhook receivers, status endpoints, staging copies. Keep separate anything with blast radius — the database, the public edge, customer data. The target is not one instance for everything, just no instance that exists to run a job firing twice a day.
Lever 5: switch billing term only after the first three levers
Annual prepay saves 15-30%, which on the $22 baseline is $3 to $6 a month. It ranks fifth because it multiplies whatever plan size you currently have, including the wrong one. Cutting a 4 GB instance to 3 GB and then prepaying the 3 GB saves more than prepaying the 4 GB, and it is the order most people get backwards.
Lever 6: negotiate the renewal
Retention offers at renewal are routine: a 10-20% discount for a one-year commitment, or a free tier upgrade, is commonly granted to a customer who opens a ticket thirty days out and states the competing quote. Worth $2-$4 a month here, and it only works before the invoice auto-charges.
Lever 7: audit egress and overage
Overage is last because it is often zero, but when it is not, it is the most volatile line on the bill. Pull the last three invoices and look for a transfer or API-request line above $3. If it is there, the fix is architectural — serve large assets from a CDN with a cheaper egress rate, or cache more aggressively at the edge — and it usually pays for itself in one month.
The ranking, in dollars saved per month
On the $22 baseline, the levers stack like this: right-sizing $4-$7, snapshot storage $15-$40, dead IPs and DNS $2-$6, consolidation $6-$12, annual prepay $3-$6, renewal negotiation $2-$4, and egress remediation $0-$20 when it applies. Most stacks get to a 30-50% cut from levers one, two, and three alone.
Run them in that order and re-measure after each. A right-sized instance changes the prepay saving; dropping snapshot storage changes what restore costs later. The goal is not the smallest bill — it is to stop paying for capacity you do not use, then spend the savings where money buys reliability.
Start with the invoice, not the pricing page. Pull three months of line items, map each to a lever, and work top down. The price and terms comparison shows what the same instance shapes cost elsewhere once renewal pricing and overage rates are included.
