The Custom ISO Refresh
The installation image you already chose, rebuilt on a current version of Linux and proved to boot under Secure Boot before it reaches you. Nothing else about it changes.
An installation image is a photograph of Linux on the day it was taken. Install from a year-old one and each machine starts a year behind, on an installer older than the hardware you are putting it on.
Send us the recipe from your original build and you get that same image again on a current base. Your applications and your branding come across untouched, and the boot menu still installs a machine while nobody watches.
Our engineers have been building and shipping Linux images since 2003. A new base brings a new bootloader and a new kernel, and that is where an installer breaks if it is going to. We install the refreshed image four ways, Secure Boot included, and confirm it on one of your own machines before it goes near the rest of your fleet.
What's included
- The same image on a current base: your applications and your branding come across untouched, so nobody has to be told anything is different about it
- A written record of what moved underneath it, so a package the distribution renamed or dropped is something we tell you rather than something one of your staff discovers
- Proved before you get it, installed four ways in virtual machines here, including under Secure Boot, which is where a new bootloader catches people out
- Confirmed on one of your own machine models, run by your own person while we watch on a screen share, with the models we did not re-test named in writing rather than left for you to assume
- Your build recipe back, updated to describe this build, so the one after it is the same short job
- A handover with the new checksum, the re-issued USB guide, and a straight answer on when to buy another one. The trigger is installing machines rather than the calendar
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.
- The build recipe from your original image, as one archive. We can't start without it
- The version name of the image it produced, and the base system it runs on today
- Your confirmation that nothing about the image is changing, plus any new SSH public keys
- One machine model from your original test list, and a person who can run the install while we watch
- Where the new image goes: our private download link, or a destination you name
Who it's for
A business that had an installation image built, is about to put Linux on another batch of machines, and wants those machines to start from something current without one other thing about the image changing.
Questions
How fast is delivery?
Standard delivery is within 40 weekday hours (≈ 3 working days). Express delivery — within 24 weekday hours (≈ 2 working days) — costs 25% more. The clock pauses while we are waiting on your recipe, your confirmation that nothing is changing, or a person to be free for the hardware check, so a prerequisite you are still putting together never counts against the deadline.
What do you need from us before you can start?
The build recipe from your original image: the base it came from and its checksum, the answer files, the package list with versions, your branding files, the repositories and the command sequence. That is what makes this a rebuild rather than a fresh one, and it is why it costs what it costs. Our copy of your ISO is deleted thirty days after we deliver it, by design, so the recipe has to come from your side.
What if we cannot find our recipe, or somebody else built our image?
A recipe kept properly is a recipe, whoever wrote it, and we check yours against seven things before building: the base image and its checksum, an answer file for each install profile, a package list with versions, the branding as files rather than as a description, a command sequence that runs as written, the repositories used, and your word that this is what produced the image you are running. If the recipe has gone, or it does not hold up, the honest answer is a new image, which is The Custom Linux ISO. We will tell you that before you pay rather than after.
Can you move us up to the next version of Linux at the same time?
No. A refresh moves you to a newer release of the version you are already on: Debian 12.7 to 12.11, AlmaLinux 9.4 to 9.6. Going up a version proper, like Debian 12 to 13 or Ubuntu 22.04 to 24.04, changes the installer, the desktop, the package names and the boot files at the same time, which puts the original build back on the table. That one is worth doing properly, and it is The Custom Linux ISO.
Can we change what is in the image while you are rebuilding it anyway?
No. A new application has to be sourced and proved to start, a different colour has to be rendered across four screens and reviewed with you, and a third install profile means a third answer file and a fourth boot entry. Each of those is work you paid for the first time, so changing any of them is The Custom Linux ISO rather than this. What the distribution forces on us we do absorb: up to three packages it has renamed or moved between sources since your last build.
How often should we expect to buy one of these?
The trigger is installing machines rather than the calendar. If you are hiring or replacing kit continuously, roughly twice a year tracks the distribution releases. If you buy machines in batches, buy one refresh just before each batch and none in between, and we would rather tell you that than sell you two. Machines already running are a separate matter and a refreshed image does nothing for them; keeping those current is The Linux Patching Plan.
Often booked alongside
- Switch to Linux
The Custom Linux ISO
One installable Linux image your own people put on every machine — your branding on it from the moment it powers on, and a boot-menu entry that installs the lot without anyone answering a question.
A$604 From A$302 on a plan
- Secure Remote Teams
The Developer Remote Workstation Setup
One developer's remote Linux workstation, finished before they log in: the desktop opens in a browser and the toolchain is proved by running it, on a machine you own rather than a laptop that leaves the building.
A$106 From A$53 on a plan
- Secure Remote Teams
The Guacamole Remote Desktop Gateway
Up to ten of your servers and desktops reachable from a browser tab over RDP, VNC or SSH, with nothing installed on the device anyone connects from and no licence to buy per person.
A$324 From A$162 on a plan