The Per-VM Setup
A new Linux VM on your own Proxmox, handed over finished: your keys in, root and password logins shut, and only the ports you named answering — each of those proved by trying it from a machine you choose rather than by reading a config file.
Creating a virtual machine takes about a minute. Finding out what nobody set on it takes about a year, and it arrives as the password login left open on a box you thought was locked, or the disk that never grew past its template size.
We hand you a machine that is finished. It comes up on the address you asked for, at a size that follows from the job you told us it has, taking your keys and refusing everything else. We write it into a register you keep, so it still makes sense to whoever inherits it.
Our engineers have been building Linux servers since 2003, and they build these in batches. You get the output of every check we ran, so you know the password login is shut instead of taking our word for it.
What's included
A machine live on the address you asked for, at a size that follows from what you tell us it has to do, so nobody guesses and nobody bills you for a benchmarking exercise
Your keys in, with root and password logins shut, proved by us trying both from a machine you choose and handing you what came back
Only the ports you named answering, on a machine that drops the rest, so adding a VM does not quietly add an opening
Up to date the day it is born, with automatic updates left off on purpose and the reason in writing, because an auto-updater that takes a live service down at 4am is nobody's idea of a favour
Reporting into the monitoring you already run, confirmed by finding it in your own console. Where you run none, we install none and the handover says so
A snapshot of exactly what we handed over, with the one line that puts it back
One entry in a register you keep: what this machine is, what it answers on, what it was built from, and what is not on it
Before you order
Have these ready so we can start the moment you order. The delivery clock only runs while we have them.
A cloud-init template on your Proxmox for the operating system you want. If you have none, The Cloud-Init Template Library builds them
Root or sudo SSH access to the Proxmox node, and the storage and network bridge the machine will use
For each machine: its hostname, its timezone, what it is for, and a DHCP or fixed address
Your SSH public keys, the addresses allowed to reach SSH, and up to five other ports to open
A machine on your network we can test the connection from
If you already run monitoring: the server's address and its enrolment key
How it works
Book it — pay the fixed price and tell us the target environment. No scoping call first.
We deliver — an experienced specialist runs our standard workflow for this exact task. You can watch progress and message them in the portal.
Hand-off — you get the deliverables, the documentation, a rollback snapshot, and a walkthrough if you want one.
Who does it
A salaried Support Resort specialist with more than ten years in the field, working from a runbook we've been refining since 2003 — supervised by senior management, never a marketplace contractor. You'll see who is assigned and can message them about this task directly in your portal.
FAQ
Ask about this task
Our assistant knows the scope document and runbook behind this service. Ask what's covered, what isn't, or whether it's the right task for your situation.
Answers come from our published scope documents. Prefer a person? Switch to the "Email us" tab — a senior manager replies personally, usually the same weekday.
Related services
The Cloud-Init Template Library
Four tested starting points for your virtual machines, so a new server is a two-minute clone rather than another operating-system install, and every clone comes up with an identity of its own.
The Per-LXC Setup
A new Linux container on your own Proxmox, handed over finished and unprivileged by default: your keys in, root and password logins shut, only the ports you named answering — and the isolation you actually got written down instead of assumed.
The Proxmox Cluster
Three Proxmox servers joined into one cluster with working high availability, proved by deliberately killing a node in a window you choose, so you watch the platform recover before you trust anything to it.
The Linux Server Hardening
One production Linux server closed off at the operating-system level to the break-in routes attackers rely on — with before-and-after evidence of every change we make.