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.
Standing up a server should take two minutes. It takes forty, because somebody is sitting through another operating-system install and then setting the timezone, the keys and the agent again from memory.
We build four templates for the Linux versions you standardise on, each carrying the same defaults: your SSH keys, your timezone and locale, the agent Proxmox needs to see inside a machine, and a root disk that grows to whatever size you give it. Cloning one gets you a running server in about a minute.
We then prove every one of them, cloning each, booting it and checking it against eight things before deleting the test machine. One template we clone twice, so you can watch the two copies come up with identities of their own. Our engineers have been building Linux fleets since 2003.
What's included
- Four templates for the Linux versions you actually run, all carrying the same defaults, so a new server becomes a clone and a boot instead of an install and an afternoon
- Your SSH keys, your timezone and your locale already inside every one, so a fresh machine is yours from its first boot rather than after twenty minutes of setup
- A root filesystem that grows to whatever disk size you ask for at clone time, so a 200 GB machine has 200 GB of usable space without anybody resizing a partition
- Every clone with an identity of its own, proved by cloning one template twice so you see two machines come up different. A copied VM hands the same machine ID and SSH host keys to every copy, which is what breaks DHCP leases and makes host-key warnings meaningless
- Proxmox able to see inside every machine you clone, so its address shows in the interface and a shutdown request is obeyed instead of pulling the power
- All four cloned, booted and checked against eight things before handover, with the results written down and the test machines destroyed
- A one-page index of the library, the exact build steps archived so your own team can rebuild any template without us, and a plain note on how they age and how to refresh them
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 the Proxmox node we build on, with a route out to the official Linux image mirrors
- Your four operating systems from our list, and a size for each
- The SSH public keys, login name, timezone and locale every new machine should carry
- A storage ID, a network bridge and four free VM IDs for the templates, and whether test clones get their address by DHCP
Who it's for
A business provisioning Proxmox VMs often enough that hand-installing each one has become the bottleneck, or that has started cloning a favourite VM and hitting duplicate-identity problems.
Questions
How fast is delivery?
Standard delivery is within 28 weekday hours (≈ 2 working days). Express delivery — within 17 weekday hours (≈ 2 working days) — costs 25% more. The clock pauses while we wait on access or on the details we need up front. Nothing in this build needs a maintenance window or a call with your team, so it rarely stops once it starts.
How many templates, and which operating systems?
Four, and you pick them from Debian 12, Debian 13, Ubuntu 22.04 LTS, Ubuntu 24.04 LTS, Rocky Linux 9 and AlmaLinux 9. Four covers both package families with room for two releases of each, which is what most fleets standardise on. Windows is a different tool chain, Alpine has no equivalent cloud image, and LXC container templates are a different artifact that comes with The Per-LXC Setup. Tell us before booking if one of those is what you need.
Does this build our actual virtual machines?
No, and the two are meant to be bought together. This builds the templates; The Per-VM Setup provisions machines from them at A$74 each. That price works because provisioning from a tested template is a clone and a boot rather than an operating-system install, which is exactly what this library gives you.
Can you preinstall our application stack or a monitoring agent?
No. An image with your web server, database or agent inside it is a build rather than a template, and a monitoring agent baked into a fleet of clones is what nobody notices has stopped reporting eight months later. Those go onto a real machine after it exists: The Web Server Install, The Database Install & Hardening, and The Wazuh Server & Client Install.
What happens as the templates get older?
They fall behind, and we would rather tell you the number than let you find out. A machine cloned six months from now starts six months behind and applies those updates on its first patch run. Your handover carries the refresh procedure for each template so your own team can rebuild one, and we can do it for you as a repeat booking. The Website Care Plan does not cover this: that one looks after websites, not servers.
Are the machines hardened?
These images ship with no passwords set and SSH keys as the only way in, and we check and record that rather than assuming it. A full lockdown belongs on a running server, where there are firewall rules, exposed services and real accounts to work with, and that is The Linux Server Hardening.
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
- DevOps & Servers
The Server Admin Day
A senior system administrator works a full day on your server backlog, from the patch level nobody has checked to the backup nobody has restore-tested. Book one day or a run of dates, and each day ends with a written account of every hour.
A$360 From A$180 on a plan