VPS vs Cloud Hosting: What the Bill Looks Like
VPS vs cloud hosting compared on the only line that matters: the invoice. Egress, add-ons, flat pricing, and when the cloud is genuinely worth it.
VPS vs cloud hosting is not really a technology argument, because both give you a virtual machine on somebody else's hardware. It is a billing argument. A VPS is a flat number you can put in a spreadsheet for the year. A cloud instance is a rate, and the rate is the smallest part of what arrives at the end of the month. If you have ever been surprised by a hosting invoice, this is the post that explains where the surprise came from.
The lines on a cloud bill that a VPS does not have#
Egress. Sending data out is metered by the gigabyte on the major clouds, separately from the instance, and it is the line that most often doubles a small bill. Serve images, ship backups off-site, or have one popular week, and the traffic you thought was free turns out to be the product.
Storage that is priced in operations. Cloud block storage is commonly billed on capacity plus provisioned throughput, so the fast disk is an upgrade rather than the default. On a VPS the disk is part of the plan and its speed is a hardware fact, not a slider.
The pieces around the instance. A load balancer, a managed database, snapshots, monitoring beyond the free tier, and a support plan that answers on a weekend are separate charges. None of them are unreasonable individually. Together they are why the estimate and the invoice rarely match.
We wrote up exactly how we build our own prices, so it is only fair to say the quiet part about theirs: metered billing is not dishonest, it is just optimized for workloads that scale up and down, and most small infrastructure does neither.
What a flat bill looks like#
Here is the shape of it on our Performance line, priced live from the same data the product page reads:
| Plan | vCores | RAM | NVMe | Transfer included | Monthly |
|---|---|---|---|---|---|
| P10 | 1 | 2 GB | 25 GB | 4 TB | $8.00/mo |
| P40 | 2 | 8 GB | 100 GB | 16 TB | $32.00/mo |
| P70 | 6 | 24 GB | 300 GB | 48 TB | $96.00/mo |
The transfer column is the one to sit with. Those allowances are included, not metered, and the bandwidth article explains how usage is counted and what happens in the rare case you exceed it. The cores are guaranteed rather than burstable, which only means something because we cap how many servers a node will ever hold. And renewals are at the price you signed up at, which should not be a feature but in this industry it is.
When the cloud is genuinely the right call#
We sell VPS plans, so treat this section as the one we had the most reason to leave out.
- Traffic that swings by an order of magnitude. If you are idle on Tuesday and ten times bigger on Friday, per-hour billing and autoscaling are worth real money.
- Managed services you do not want to operate. A managed database with automatic failover is a genuine engineering saving if nobody on your side wants to be a database administrator.
- Multi-region requirements. Regulatory data residency or global low latency needs footprints we do not have.
- Everything defined in code. If your infrastructure is provisioned by a pipeline and torn down nightly, an API-first platform is the correct tool.
What none of those describe is the most common workload on the internet: a site, a database, and a couple of background jobs that run at roughly the same size all year. If that workload is still on shared hosting, the cheaper first move is the smaller one, and we walked through it in shared hosting vs VPS.
The middle path most people actually want#
Run the steady part on a VPS and rent the elastic part by the hour when you truly need it. One machine can hold the application, its database, a queue worker, and a staging copy, especially with Docker Compose keeping them tidy. Push backups somewhere else on purpose, because a copy that lives on the same server is not a backup; our backup and RAID article draws that line clearly.
Start smaller than you think and move up when a graph tells you to. Upgrades prorate daily and stay on the same line, and if the workload turns out to need pinned cores rather than guaranteed shares, the VDS line is the next step; the knowledge base comparison walks that decision properly.
FAQ#
Is a VPS cheaper than cloud hosting?
For a steady workload, usually yes, and the gap widens as soon as you serve real traffic, because egress is included here and metered there. For bursty workloads the cloud can absolutely win.
What is the actual difference between a VPS and a cloud instance?
Technically very little; both are virtual machines. Commercially the difference is flat versus metered, and long-lived versus disposable.
Do I get charged extra for bandwidth?
Every plan includes a transfer allowance measured in terabytes, shown in the table above and on the plan pages. Overage is the exception rather than the business model.
Can I move to a bigger plan without rebuilding?
Yes. Upgrades happen in the MyNobull portal, prorate daily, and do not require a reinstall, so sizing conservatively at the start costs you nothing later.
