The cheapest VPS worth self-hosting on is the smallest KVM instance with NVMe storage, CPU you know the terms of, and a stated traffic allowance. Rock-bottom prices usually hide oversold CPU, slow disks or traffic caps. Buy on the spec sheet and the provider's record, not the headline number.
Short answer
Pick a KVM VPS with NVMe storage, at least 2 GB RAM for one small app (4 GB for a production app with a database), and a stated traffic allowance. Know whether the vCPU is shared or dedicated. Hetzner, DigitalOcean, Vultr, Contabo and OVHcloud all sell in this range. Prices change by plan and region, so compare them on each vendor's own page on the day you buy.
I am Manoj. I lead infrastructure and deployment work for ERPNext and Frappe programmes at MithTech, a team of Frappe specialists in Bengaluru, running Frappe/ERPNext, n8n, databases and other self-hosted tools for clients who want to own their infrastructure. This is the checklist I use before I click "deploy".
The cheapest VPS on paper is rarely the cheapest to live with: a slow disk or an oversold CPU costs more in lost hours than the few rupees saved.
What specs should a cheap VPS have for self-hosting?
Four specs decide whether a budget VPS is a bargain or a trap: virtualisation type, storage type, CPU terms and IP addressing. Get these right and an entry plan runs open-source apps well.
KVM gives you a real virtual machine with its own kernel, so the RAM you pay for is yours rather than shared out of an oversubscribed container. NVMe storage matters more than most people expect: random I/O on NVMe is far faster than on SATA SSD or spinning disk, and a database-backed app on slow storage feels sluggish however much CPU it has. Finally, read how the CPU is described. Shared vCPUs are fine for light or bursty loads; a database under steady load is worth a "dedicated" plan, which costs more.
Skimmable summary: check KVM, NVMe, the vCPU terms and a public IPv4; those four separate a usable cheap VPS from a frustrating one.
Which VPS providers should you consider?
No provider wins on every axis, so match it to what you care about most: raw cost, tooling, or RAM per rupee. Prices change often, so this table compares fit, not price; confirm prices on each vendor's page.
| Positioning | Suits | |
|---|---|---|
| Hetzner | Low-cost cloud in Europe, the US and Singapore; good API and CLI; large included traffic | Developers who want cheap, clean infrastructure and can live without an India region |
| DigitalOcean | Simple dashboard, good docs, predictable billing, a Bengaluru region | Teams who value simplicity and tutorials over the lowest price |
| Vultr | Wide data-centre footprint, including Indian cities | A node close to Indian or APAC users |
| Contabo | A lot of RAM and storage for the money | RAM-hungry workloads where capacity matters more than peak disk speed |
| OVHcloud | Large European host with an India site | Buyers who want a big incumbent |
Capacity-first hosts such as Contabo give more RAM and disk for the money, sometimes on more heavily shared hardware, so speed can vary by time of day. Hetzner and DigitalOcean give cleaner APIs, better docs and steadier performance. For an India-facing app, a region in India, or at least Singapore, feels noticeably faster than one in Europe or the US. I compare three of these in Hetzner vs DigitalOcean vs AWS, and Hetzner against AWS for ERPNext in AWS vs Hetzner.
Skimmable summary: Hetzner or DigitalOcean for tooling and steady speed, Contabo for raw RAM, Vultr, DigitalOcean or OVHcloud for an India region; check prices on each vendor's page.
How much RAM, CPU, and storage do you actually need?
Size for the real workload plus headroom, because backups, updates and traffic spikes all take resources at the worst moment. One light app is happy on a small instance; a database-heavy tool or several services together need more RAM long before they need more CPU.
The tiers I start from:
Hobby or single small app
One static site, a small CMS, or a single low-traffic service runs comfortably on an entry KVM instance with around 1 vCPU and 2 GB RAM on NVMe. Fine for testing and personal projects.
Serious single production app
For a real production workload with a database — a self-hosted analytics tool, an automation engine, or a small business app — start at roughly 2 vCPU and 4 GB RAM. This is the comfortable floor for most people.
Several stacked services or a heavier app
Running multiple containers, a PaaS layer, and a couple of databases together means 4 vCPU and 8 GB RAM or more. Under-provisioning here causes swap thrashing that gets wrongly blamed on the application.
Add storage and backup headroom
Whatever RAM you pick, give yourself disk room for the OS, your data, and at least one local backup. Block storage that can grow without a reinstall saves real pain later.
The usual mistake is the smallest instance, then an app that crawls once real data lands. Sizing right once is cheaper than moving a live service under pressure.
Skimmable summary: 2 GB RAM for a hobby app, 4 GB as the production floor, 8 GB+ for stacked services — and always leave headroom for backups and updates.
What are the hidden gotchas of cheap VPS hosting?
They sit in the fine print: oversold CPU, throttled "unlimited" bandwidth, no backups, and a region far from your users. Any one of them turns a cheap plan into an expensive one.
Support is the other quiet variable. A slightly dearer host that answers a ticket in an hour can cost less in practice than one that leaves you alone with a network outage at midnight. Uptime history and community reports are worth reading.
Skimmable summary: check traffic caps, CPU oversell, backup pricing, region and egress before you commit.
Once you have a plan in mind, the self-hosting cost comparator turns your monthly server, backup and support bills into a three-year total. Set it against the SaaS subscription you would otherwise pay, and add the hours your team spends on upkeep.
Should you run a PaaS layer like Coolify on top?
For most people, yes. Coolify is an open-source, self-hostable platform that makes a plain server work more like Vercel or Heroku: Git deploys, automatic Let's Encrypt certificates, databases and a catalogue of one-click services, on a server you pay for directly.
Coolify has no licence fee; you pay only for the server. Its first stable v4 release, v4.0.0, came out on 27 April 2026 after a long beta. It manages servers over plain SSH, so you can point it at any provider above, and your data and configuration stay on your machine. I walk through a setup in self-host with Coolify.
The alternative is Nginx, TLS and deploy scripts by hand. That works if you enjoy it; a PaaS layer removes a lot of fiddly, error-prone work for no licence fee.
Skimmable summary: Coolify (stable v4 since 27 April 2026) adds push-to-deploy and automatic TLS to any cheap VPS, with no licence fee and your data on your server.
How does this apply to self-hosting ERPNext?
ERPNext needs more than a static app: it runs MariaDB, Redis, background workers and a Python and Node application server, so RAM and disk speed matter more. A cheap VPS still works. ERPNext is open source under GPL-3.0 with no licence fee, but size it properly.
The same rules apply: KVM, NVMe, and enough RAM that MariaDB and the Redis and worker processes are not fighting for memory. One well-chosen instance handles a modest user count; larger teams need more. If you would rather not run the server at all, that is a fair choice too, and since ERPNext is open source the choice stays yours: run it yourself on a cheap VPS, or hand hosting and upkeep to someone else.
Skimmable summary: ERPNext runs well on a right-sized cheap VPS with NVMe and enough RAM; hand the upkeep to someone else if you would rather not run it.
Should you run the VPS yourself, or have it run for you?
Run it yourself if someone on your team has a few hours every month for updates, security patches and a backup they have actually restored; the checklist above is then all you need. Have it run for you if nobody owns that work, because a cheap VPS stays cheap only while someone looks after it.
Do it yourself if
Someone is at home with Linux, SSH and Docker, will copy backups off the server and test a restore, and a few hours offline while they fix something is acceptable.
Have it run for you if
Nobody wants to be the person who patches the server, what runs on it (an ERP, a store, customer chats) cannot be down for a day, or those hours cost more than a monthly fee.
Under managed hosting we run one named server in your cloud account or ours: nightly backups copied off it, one restored on a schedule, every upgrade tried on a copy first, and the keys stay yours. It is a monthly fee for running it plus the server, quoted in writing after a call. To weigh that quote against doing it yourself, use the self-hosting cost comparator; for ERPNext, who runs it after go-live sets out who does each job on each path.
Frequently asked questions
+What is the cheapest reliable VPS for self-hosting in 2026?
The smallest KVM instance with NVMe storage and a stated traffic allowance, from a host with a good uptime record. Hetzner, DigitalOcean, Vultr, Contabo and OVHcloud all sell in this range. Prices change often and vary by region, so compare current plans on each vendor's own page rather than trusting a figure in an article.
+Is KVM really better than OpenVZ for a cheap VPS?
Yes. KVM gives you a real virtual machine with its own kernel and RAM, while OpenVZ containers share the host kernel and are easier to oversell. For anything that matters, insist on KVM; most budget providers now offer it as standard.
+How much RAM do I need to self-host an open-source app?
One small app runs in about 2 GB RAM; a production service with a database is more comfortable at 4 GB. Several services together, or a heavier app, want 8 GB or more. RAM usually runs out first, so leave headroom.
+Can I run ERPNext on a cheap VPS?
Yes. ERPNext is open source under GPL-3.0 with no licence fee, so you pay for the server and its upkeep. It needs more RAM and faster storage than a simple app because it runs a database and background workers, so choose an NVMe-backed KVM instance with enough memory and size up as users grow.
+Do I need a PaaS like Coolify, or can I deploy manually?
You can deploy by hand with Nginx, TLS and scripts, but a self-hosted PaaS like Coolify removes most of that work with no licence fee. It adds Git deploys, automatic TLS and one-click services on any VPS you already pay for, and your data and configuration stay with you.
+What bandwidth should I look for on a cheap VPS?
A plan that states its included traffic, rather than a vague "unlimited" that often hides throttling or a fair-use cap. Match it to your expected traffic, and check the egress policy: some hosts charge for outbound data, which quietly raises a cheap plan's real cost.
Comments & ratings
No comments yet. Start a new discussion.
Manoj · Published on 20 July 2026
Worked with us? Leave a Google review