A custom VPS is a virtual private server where you choose the resources - CPU, RAM, storage - and get root access to configure the operating system and software exactly how you want. It sits between shared hosting (cheap, limited, no control) and a dedicated server (expensive, total control), and the thing to understand before buying one is that the control you are paying for comes bundled with responsibility you cannot hand back.
Custom VPS sounds like the grown-up choice, and sometimes it is. But full control means full responsibility, and that trade is the whole decision.
Table of contents
- What a VPS actually is
- The control you gain
- The responsibility you inherit
- When a VPS is the right call, and when it is not
- Where RunxBuild fits
- FAQ
What a VPS actually is
A physical server is partitioned into several virtual machines, each with dedicated slices of CPU, memory, and disk, isolated from the others. Your VPS behaves like its own server: you get root access, choose the OS, and install whatever you like. Custom usually means you pick the resource sizing rather than taking a fixed package.
Unlike shared hosting, your neighbours cannot consume your allocation - the resources are yours. Unlike a dedicated server, you are sharing the physical hardware, which is what keeps it affordable. For a lot of workloads it is the sweet spot of control versus cost, provided you actually want the control.
The control you gain
Root access is the appeal. You can install any runtime, any database, any system package; tune the web server and kernel parameters; run background workers and cron jobs; and host multiple sites or services on one box however you like. Nothing is off-limits because there is no control panel deciding what you are allowed to do.
For workloads that need a specific software stack, an unusual configuration, or several moving parts on one machine, this flexibility is genuinely valuable. It is the reason people choose a VPS over shared hosting: the shared environment said no to something, and the VPS says yes to everything.
The responsibility you inherit
Here is the part the sales page is quiet about. With root access, you are the system administrator. You patch the OS and the software for security vulnerabilities. You configure and maintain the firewall. You set up backups and test that they restore. You monitor for disk filling, memory leaking, and the server going down at an inconvenient hour. You handle the TLS certificates, the reverse proxy, and the log rotation.
On an unmanaged custom VPS, all of that is yours. A VPS left unpatched is a VPS that gets compromised. The hourly cost of the server is often the smallest part of the total cost; the time and the risk are the rest, and they do not appear on the invoice.
When a VPS is the right call, and when it is not
A custom VPS makes sense when you genuinely need root-level control - an unusual stack, specific kernel tuning, several services co-located, or a learning exercise where running the server is the point. If you have the sysadmin skills or want to build them, it is a powerful, cost-effective tool.
It is the wrong call when what you actually want is to run an app and have it stay up, and the server administration is pure overhead you would rather not own. Many people buy a VPS for the control and then spend their time doing operations instead of building the thing they wanted to build. If that is you, a managed platform gets you the running app without the server to babysit.
Where RunxBuild fits
RunxBuild is the managed alternative to a custom VPS for the common case. Instead of provisioning a server, patching it, and wiring up TLS, backups, and a reverse proxy, you deploy a service from a GitHub repo and the platform runs it - with a live route, automatic TLS on custom domains, runtime logs, metrics, and autoscaling between a floor and ceiling plan you choose.
You still pick the resources, the way you would size a custom VPS - the plans run from a Free tier through Basic at $6 and up - but you are choosing a plan, not inheriting a server to administer. If you want root access for its own sake, a VPS is the right tool. If you want the app running without becoming its sysadmin, this is the trade in the other direction.
How this fits the rest of the stack
The cost of a project is the sum of its line items, not the headline number, and the RunxBuild hosting calculator is the right place to add them up: the service, the database, the storage, the bandwidth, each a separate figure. Model it before committing, not after the first invoice. The RunxBuild dashboard is where the running project shows its real usage in one place.
Useful related references:
FAQ
What does custom VPS mean?
A virtual private server where you choose the resource sizing - CPU, RAM, storage - and get root access to configure the operating system and software yourself. It sits between shared hosting and a dedicated server, offering dedicated resources and full control while still sharing physical hardware to keep costs down.
What is the difference between a VPS and shared hosting?
On shared hosting many sites share one environment and your performance depends on your neighbours, with no root access. A VPS gives you a dedicated slice of resources that neighbours cannot consume, plus root access to install and configure anything, in exchange for more responsibility and cost.
Do I have to manage a VPS myself?
On an unmanaged custom VPS, yes - you patch the OS and software, configure the firewall, set up and test backups, handle TLS and the reverse proxy, and monitor uptime. Managed VPS or managed platform options take that operational work on for you, which is the main reason to choose them.
Is a custom VPS worth it?
It is worth it when you genuinely need root-level control - an unusual stack, specific tuning, or co-located services - and have or want the sysadmin skills. It is poor value when you only want an app to run reliably and the server administration becomes pure overhead you would rather not own.
What is the managed alternative to a custom VPS?
A managed platform where you deploy your app from a repository and it runs with automatic TLS, logs, metrics, and autoscaling, while you choose a resource plan rather than administering a server. You give up root access for its own sake in exchange for not having to patch, back up, and monitor a machine.