One refurbished mini PC of the ₹10,000–15,000 kind described below can host five or six independent servers. That is the whole pitch. In a self-hosting environment, a careless config change to the box running Pi-hole can take down the entire household’s DNS, usually with someone hovering behind asking when the Wi-Fi will come back. Proxmox solves this by isolating services into separate VMs or containers so that experiments stay contained and the family’s services keep humming, untouched, in VMs of their own.
About the prices and versions: Rupee figures for the refurbished mini PCs here are what Indian sellers were asking when this guide was written (whether a figure includes GST varies by seller), and they move quickly — treat them as indicative rather than a quote. The repository steps are for Proxmox VE 9, the current major release when this guide was written; check the documentation linked under Sources before assuming a command or option still matches.
Proxmox VE is free, open-source virtualisation software, and the name alone makes it sound like something you need a certification to touch. It really is enterprise-grade. The intimidating part is mostly marketing. If you’ve installed Ubuntu even once, you can run this, and what follows takes you from a blank machine to two working virtual servers.
what proxmox actually does
It’s an operating system you install straight onto the hardware. Rather than running your apps itself, it slices the machine into isolated virtual computers, each one handed its own portion of CPU, RAM and disk, each running its own OS, each rebootable or deletable without disturbing the rest. You drive all of it from a web page in your browser. After the install, you never plug a monitor into the box again.
There are two flavours of guest. Full VMs emulate an entire computer and will run anything, Windows included. LXC containers borrow the host’s kernel, boot in seconds and want a fraction of the RAM. A Pi-hole container runs fine on 512 MB. My rule, give or take: containers for simple Linux services, VMs for anything that needs its own kernel, Docker, or a weird OS you can’t predict.
hardware: what you actually need in india
Proxmox itself barely sips resources. The real question is how many guests you intend to stack on top. My honest minimums:
| Spec | Minimum | Comfortable |
|---|---|---|
| CPU | 4 threads with VT-x/AMD-V | i5 6th gen or newer, 4 cores |
| RAM | 8 GB | 16 GB (the real bottleneck) |
| Storage | 128 GB SSD | 256–512 GB NVMe or SATA SSD |
| Network | Ethernet to router | Gigabit ethernet |
The smart buy is still the refurbished corporate mini PC. A Lenovo ThinkCentre M710q or a Dell OptiPlex Micro with an i5 and 16 GB lands around ₹10,000–15,000 from refurb sellers, pulls 15–30 W, and sits there silent. An old laptop with 16 GB does the job too, and brings its battery along as a built-in UPS. Skip the Raspberry Pi here. Proxmox VE doesn’t support it (even the official arm64 build added in August 2026 needs UEFI/ACPI server-class hardware), and the RAM ceiling would bite you fast anyway. Whatever you land on, put it on the inverter line. A hard power cut mid-write is the single most common way beginners corrupt a Proxmox disk, and at 25 W the inverter won’t even register the load.
installing proxmox in about 30 minutes
- Download the Proxmox VE ISO (proxmox.com, free, no registration) and flash it to a pen drive with Rufus or Etcher.
- In the machine’s BIOS, enable virtualisation (Intel VT-x or AMD-V; often buried under “CPU Configuration”) and set “Restore on AC Power Loss” to power on. Both matter. The second one is your power-cut insurance, and people forget it constantly.
- Boot from USB, accept defaults, let it take the whole SSD (the installer erases it, so copy off anything you need first), and hand it a static-feeling IP you’ll actually remember, like 192.168.29.10. Use your real router gateway and 8.8.8.8 for DNS for now.
- When it reboots, pull the monitor and keyboard. From any browser on your network, open the address it printed, say https://192.168.29.10:8006, accept the self-signed certificate warning, and log in as root.
One post-install chore trips up nearly everyone. Proxmox ships pointed at the paid enterprise update repository, so the first time you run updates they fail with a subscription nag. Switch to the free community repo from the web UI (Repositories section: disable “enterprise”, add “no-subscription”), or do it from the shell. These steps are for Proxmox VE 9; the one-line bookworm recipes all over the internet are for Proxmox VE 8, which reached end of life in August 2026.
# Proxmox VE 9 (Debian 13 "trixie") keeps repositories in deb822 .sources files.
# 1. Disable the enterprise repo: add the line "Enabled: no" to its entry
nano /etc/apt/sources.list.d/pve-enterprise.sources
# 2. Add the free repo: create (or edit) this file so it contains these five lines
nano /etc/apt/sources.list.d/proxmox.sources
Types: deb
URIs: http://download.proxmox.com/debian/pve
Suites: trixie
Components: pve-no-subscription
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
# 3. Update
apt update && apt full-upgrade -yThe catch is that the nag dialog at login sticks around even on the free version. Click OK and move on. Nothing is actually restricted, no matter how much the popup implies otherwise.
your first container: pi-hole in ten minutes
Containers need a template before anything else. In the web UI, click your storage (“local”), then CT Templates, then Templates, and pull down the newest debian-standard template that Pi-hole’s prerequisites page lists as supported. Hit Create CT at the top right and walk the wizard: hostname “pihole”, a strong root password, the Debian template, 8 GB disk, 1 CPU core, 512 MB RAM, and a static IP on your LAN such as 192.168.29.11/24 with your router as gateway. Start it, open its console from the UI, and install Pi-hole inside exactly as you would on any Debian box. My Pi-hole guide applies from here on unchanged.
Sit with what just happened. A whole “server” came into being in under a minute, on half a gigabyte of RAM. That’s usually the moment Proxmox clicks for people who were skeptical of the whole idea. Two small tips for containers that serve the whole house. Tick “Start at boot” so the service survives a power cut without you babysitting it, and set the Pi-hole container’s start order to 1 under Options so DNS is up before anything else tries to resolve. Done right, your family never even learns the electricity died at 4 am, which is about the highest praise a home lab can earn.
your first full vm: an ubuntu docker host
Upload the current Ubuntu Server LTS ISO (26.04 at the time of writing) to local storage (ISO Images, then Upload), click Create VM, and give it 2 cores, 4 GB RAM and a 32 GB disk. Two settings are worth slowing down for. Set CPU type to host for full performance, and tick the QEMU Guest Agent option (then install qemu-guest-agent inside Ubuntu) so Proxmox can read the VM’s IP and shut it down cleanly instead of yanking the plug. Install Ubuntu in the console as normal, add Docker, and this VM becomes home to everything from Jellyfin to the n8n automation stack. If you’re migrating off a single-OS setup, my weekend home lab plan maps onto this VM almost one-to-one.
backups: the feature that justifies the whole thing
Here’s the feature that, for home use, is the actual reason to bother. Select any VM or container, click Backup, and Proxmox spits out a single file holding the entire machine. Schedule it under Datacenter, then Backup. A sensible schedule is every guest at 3 am daily to a second internal disk. Restoring a small container from the previous night’s backup is typically a matter of minutes, against the full weekend a from-scratch rebuild can cost. So take snapshots before any risky change too. A snapshot is instant and rolling back is one click.
where beginners trip
- Forgetting to enable VT-x in the BIOS, then wondering why VM creation keeps failing. It ships disabled on a lot of refurb machines.
- Over-allocating RAM. Proxmox itself wants 1–2 GB; on a 16 GB box, hand out 12–13 GB to guests at the very most.
- Running guests on DHCP. Give every container and VM a fixed IP and keep a plain text list somewhere. Services that quietly change addresses cause the kind of breakage you’ll waste an evening chasing.
- Storing backups on the same disk as the guests. One dead SSD then takes both with it. A second cheap disk, or an external drive, solves it for almost nothing.
- Exposing the 8006 web UI to the internet. Don’t. Reach it remotely through Tailscale, which also sidesteps Jio and Airtel CGNAT entirely.
FAQ
Is Proxmox really free, or is the subscription required?
The software is fully free and open source, with no feature locks hiding behind the paywall. So what does the subscription actually buy? Access to an extra-tested update repository and official support, which enterprises want and homes genuinely don’t. The free no-subscription repo is what most home labs run; Proxmox itself describes it as intended for testing and non-production use.
Proxmox or just Docker on Ubuntu: which should a beginner pick?
Running three or four services on one machine? Plain Ubuntu with Docker is simpler, and you should probably start there. Proxmox earns its keep when you want real isolation, instant full-machine backups, or the freedom to experiment without breaking production. Plenty of people run both: Proxmox on the metal, Docker inside a VM.
How much electricity will a Proxmox box add to my bill?
A mini PC host with five or six light guests draws 20–35 W, which works out to roughly 15–25 units a month, or about ₹100–180 at typical Indian tariffs. The guests share one physical power budget. That’s precisely why a single Proxmox box beats running several separate machines that each idle away their own watts.
Can I run Windows in a VM for that one office app?
Yes, and it works surprisingly well. Give the VM 2 cores and 4–8 GB RAM, attach the Windows ISO plus the VirtIO drivers ISO during creation, and you end up with a Windows machine reachable over Remote Desktop from any device in the house. You’ll need your own valid Windows licence, of course. No way around that one.
Tonight, before you talk yourself out of it: build the Pi-hole container. Grab whatever 16 GB machine you can find, flash the ISO, and create that one half-gigabyte container while it’s fresh. Everything else here can wait for next weekend.
Update history: the repository steps now cover Proxmox VE 9, the Raspberry Pi, Ubuntu ISO, template and power-cost details are corrected, an installer warning is added, and more primary sources are listed.
Sources
- Proxmox VE documentation — official admin guide for storage, clustering and backup specifics.
- Proxmox VE package repositories — the enterprise and no-subscription repository files for the current release.
- Proxmox VE FAQ — supported releases and end-of-life dates.
- Proxmox VE roadmap — release history, including architecture support.