The Proxmox Audit & Tune-up
We inspect your Proxmox platform against 96 checks, rank what we find by how much trouble it will cause you, and repair the eight worst problems — so you stop guessing what state the machines your business runs on are in.
Somebody else set up your Proxmox. A data centre did it at handover, or an admin who has since left, and it has run ever since — which is not the same thing as being in good shape.
We go through your nodes, your storage, your cluster, your backup arrangements, your network and the headroom you have left, and write down what we find. We rank every problem by what it will cost you, then put the eight worst repairable ones right.
The engineers doing it have been running remote Linux infrastructure since 2003 and work on Proxmox most weeks. Nothing changes until you have read the findings and approved a named list, so we never alter a live platform on our own judgement of what matters.
What's included
- A written account of what state your virtualisation is actually in: nodes, cluster, storage, backup arrangements, resource headroom, network and security posture, each with the measured numbers behind the verdict
- Every problem ranked by what it costs you, so the storage pool losing a disk is never buried among the settings that are only untidy
- The eight worst repairable findings put right, worst first, chosen from a list of seventeen repairs published before you book
- Nothing touched until you say so: the findings reach you first, and a person you name approves a specific list in writing before anything on a live platform changes
- Before and after evidence for every repair, the exact way back from each one, and the affected checks re-run to prove the result instead of asserting it
- A prioritised plan for everything left over, in the order it should be dealt with, each item naming what covers it
- The written record of your environment — nodes, versions, storage, network and every machine's settings — which for an inherited install is often the first one that has ever existed
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.
- Root or sudo SSH access to every node, plus a web interface login that can read the datacenter configuration
- The size of the job: how many nodes, machines and physical disks, and whether you run Ceph
- Which machines are production, and whether your web interface is reachable from the internet
- The person who approves fixes, and a maintenance window if you can offer one
- Read access to your Proxmox Backup Server, if you run one and want it checked
Who it's for
A business running Proxmox it inherited from a data centre or a previous admin, that wants to know what state it is in and the worst of it fixed.
Questions
How fast is delivery?
Standard delivery is within 46 weekday hours (≈ 3 working days). Express delivery — within 28 weekday hours (≈ 2 working days) — costs 25% more. The clock pauses while we wait for your approval of the fix list and for the maintenance window you pick, so taking your time over either never counts against the deadline.
How much fixing is included?
Eight repairs, and you can count them yourself before you book. They come from a published list of seventeen: bringing a node up to date within its current version, reclaiming a root disk that is filling, putting a scrub schedule on a storage pool that has never had one, fixing a network bond running with no link monitoring, setting boot order and agent flags across your machines, and so on. A repair that applies to one node counts once for that node, and a machine-settings repair covers up to five machines you name. We write everything else up in priority order for you to act on or book separately.
Will you change anything on our live platform without asking?
No. The whole inspection is read-only, and you get the findings before anything is touched. We then propose a specific list — what we would do, what it affects, whether it needs a reboot, and how it would be undone — and a person you nominate approves it in writing. Approving none of it is a perfectly good outcome, and you still get the full report and the priority plan.
Do you fix the security problems you find?
No, and the reason is worth knowing. We check eleven things: whether the admin interface is exposed, whether anyone has a second factor, who holds administrator rights, certificate expiry, firewall state and the rest. Every finding goes in the report with what to do about it. Closing them properly means certificates, MFA enrolment, named-account separation and firewall changes, which need the lock-out protection that The Proxmox Web UI Hardening is built around. Making those changes halfway through an audit is how an administrator ends up locked out of their own hypervisor.
Do you check our backups?
We check what exists on the day we look: which jobs run, which of your machines are covered and which are not, when each job last succeeded, and whether retention is set. Where you give us read access to a Proxmox Backup Server we also report its free space and its last cleanup and integrity results. What we cannot tell you is that a backup will restore, because only a restore proves that. Bringing one of your machines back from its backup in front of you and timing it is The Proxmox Backup Server Setup. And nobody here watches your jobs afterwards, so treat the backup section as a photograph rather than a promise.
How big an environment does this cover?
One standalone node or a cluster of up to three, carrying up to 30 machines, with up to 24 physical disks between them, on Proxmox VE 7 or later. Ceph is not inspected: how a Ceph cluster is doing depends on disk count, pool layout and network capacity, and that is a job in its own right. If your environment is bigger than that, or Ceph is the part you are worried about, talk to us before booking.
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