Why "best" is the wrong question
Search for the best VPS for self-hosting and you will find a dozen lists that all name different winners. That is not because the writers disagree about hardware; it is because self-hosting is not one workload. Someone running a single note-taking app has almost nothing in common with someone hosting a photo library, a password vault, a media server and a database on the same machine. A plan that is perfect for one is either wasteful or hopeless for the other. The useful question is not "which is best" but "which criteria decide," and this page hands you those criteria.
The recommended baseline in the panel above — two cores, four gigabytes and sixty gigabytes of fast disk — is a sensible middle for a small collection of apps, not a universal answer. Treat it as a starting shape and adjust with the checklist below. The value of learning the criteria is that you stop trusting other people's lists and start reading plans the way an experienced self-hoster does.
The five criteria that actually separate plans
Marketing pages compete on the numbers that are easy to print. The things that determine whether a self-hosting plan is pleasant or painful are often in the fine print, or absent entirely. These five are where good and bad plans diverge.
| Criterion | What a good plan does | The cheap-trap version |
|---|---|---|
| Memory headroom | Enough RAM for the combined stack plus spare | Just enough for today, swapping within weeks |
| Disk that grows | NVMe with room for logs, images and data | A tiny disk that fills and blocks deploys |
| Honest bandwidth | Clear allowance that survives real use | Low cap with throttling or overage bills |
| Real CPU share | Cores that hold up under concurrent load | Oversold cores that stall when busy |
| Upgrade path | Resize in place with a reboot | Growth means rebuild and migrate by hand |
Match the plan to how you self-host
Self-hosting grows by accretion. You start with one app, it works, and six months later there are five, plus a database and a reverse proxy tying them together. That pattern should shape the purchase: size for the stack you will plausibly have soon, not only the one app you are installing this weekend. Memory is where this bites first, because each new service takes its slice before your data is even touched.
The other structural choice is one box or several. A single server is simpler to manage and cheaper, and it is the right call for a handful of related apps you can afford to restart together. But it is also a single point of failure — one bad update or full disk takes everything down at once. When the stack matters, or when one app is clearly the heavyweight, splitting the load across two focused plans is often the more resilient and easier-to-reason-about choice.
A short checklist for judging a self-hosting plan
- Sum the RAM of every app you will run at once, then add headroom for the host.
- Choose disk that has room for months of logs, images and data growth.
- Read the bandwidth allowance and what happens when it is exceeded.
- Prefer providers that let you resize in place instead of forcing a migration.
- Decide up front whether one box or two focused servers fits your risk tolerance.
Ready to judge a plan?
Take these five criteria to a provider's line-up and see which plan actually fits your stack.