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
How it works
- 01
Book and send access
Book online with your ABN or NZBN. We tell you exactly what access and material we need; the clock starts once we have it.
- 02
We do the work
An experienced employee who specialises in this task works through it, and asks before anything outside the scope.
- 03
Delivered with evidence
You get everything listed on this page, with a written account of what was done.
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
Who it's for
A business building Linux VMs on Proxmox it already runs, that wants each one to arrive finished and written down rather than carrying whatever the person who built it remembered that day.
Questions
How fast is delivery?
Standard delivery is within 8 weekday hours per VM. Express delivery — within 5 weekday hours — costs 25% more. The clock pauses while we wait on access, on your keys, or on a template that is still being built, so a prerequisite you are putting together never counts against the deadline.
Do we need cloud-init templates already?
Yes, and it is the one thing we cannot start without. A template is what makes a VM cost this little instead of costing an operating system install, so if you have none for the OS you want, we pause before taking any money and point you at The Cloud-Init Template Library. Build that once and every machine after it starts from a tested image.
What counts as one VM?
One guest, one network card, one disk, one entry in your register. A second card, a second disk or a graphics card passed through are all real things we do, but they are not this fixed price, so raise them and we will size it properly.
Do you install our application on it?
No. The machine is handed over empty on purpose, ready for whatever you put on it. A web server is The Web Server Install, a database is The Database Install and Hardening, and anything with no product of its own is The Server Admin Day.
We are moving machines off VMware or Hyper-V. Does each one need this too?
No. A migrated guest is not a new build, it does not consume one of these, and you are never charged for both on the same machine. This builds new machines from a template, so it cannot be pointed at one you already have — for an existing guest, a security baseline is The Linux Server Hardening.
How much hardening is in here?
Twelve things, all named up front: root and password logins shut, a machine that drops everything but the ports you chose, logs that survive a reboot and cannot fill the disk, and the guest agent answering. A full benchmark pass across sixty-odd settings is The Linux Server Hardening, ban-on-repeat-failure is The Brute Force Guardian, and supervised monthly patching afterwards is The Linux Patching Plan.
Often booked alongside
- DevOps & Servers
The Brute Force Guardian
Repeated failed logins get the attacker's IP banned at your firewall automatically — a standalone fail2ban setup, with your own addresses whitelisted first so you're never locked out.
A$135 From A$67.50 on a plan
- DevOps & Servers
The CI Runner & Pipeline Setup
Build machines wired into the git platform you already run, with up to three pipelines handed over running green on your own code.
A$354 From A$177 on a plan
- Proxmox Administration
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.
A$249 From A$124.50 on a plan