Linux
Prepared unattended paths with storage selection and network configuration.
- Ubuntu Server 24.04 + 26.04
- Ubuntu Desktop 26.04
- Debian
- AlmaLinux 8, 9 + 10
- Rocky Linux
Rebuild a server for an ISO.
LogicBoot gives operators one controlled boot path for unattended installs, hypervisors, live environments and recovery tools across physical infrastructure.
- Networking
- IPv4 + IPv6
- Workflows
- Install + recover
The repeatable paths operators use most.
LogicBoot adds guided, infrastructure-aware deployment to the common rebuilds, while keeping interactive installers available when a machine needs individual attention.
Windows
WinPE-based deployment with generated answer files and a controlled media source.
- Windows 10 Pro
- Windows 11 Pro
- Server 2022 Standard
- Server 2022 Datacenter
- Server 2025 Standard
- Server 2025 Datacenter
Infrastructure
Hypervisor and appliance installation from the same authenticated boot path.
- Proxmox VE
- Proxmox Backup Server
- Proxmox Mail Gateway
- VMware ESXi 8.0 U3e
More than the usual server images.
Choose a prepared installer, a live operating system or the right recovery utility without rebuilding boot media for each job.
Platform availability varies by site, firmware and architecture.
A
AlmaLinux
Server
D
Debian
Server
F
Fedora
Server
R
Rocky Linux
Server
U
Ubuntu Server
Server
A
Arch Linux
Desktop & live
K
Kali Linux
Desktop & live
L
Linux Mint
Desktop & live
W
Windows 11 Pro
Windows
W
Windows Server 2025 Standard
Windows
Proxmox VE
Infrastructure
VMware ESXi
Infrastructure
C
Clonezilla
Recovery & tools
G
GParted
Recovery & tools
M
Memtest86+
Recovery & tools
S
SystemRescue
Recovery & tools
A
Alpine Linux
Server
C
CentOS Stream
Server
C
CentOS Stream CoreOS
Server
D
Devuan
Server
F
Fedora CoreOS
Server
F
Flatcar Container Linux
Server
F
FreeBSD
Server
F
FreeDOS
Server
24 shown 99 boot targets in the current catalogue
Save the install choices you would otherwise enter by hand.
A deployment profile is a reusable install plan. It combines the target operating system with its network and storage choices, then gives LogicBoot what it needs to prepare the installer.
Choose the target
Start with the operating system, hypervisor or appliance being installed.
Set the network
Use DHCP or include the static addresses needed by the finished machine.
Set the storage
Choose the supported disk layout, such as LVM, RAID 1 or a ZFS mirror.
Use it again
Apply the same plan to the next suitable machine without preparing new boot media.
Example profileProxmox host
- install
- Proxmox VE
- route
- Automatic
- addressing
- Static IPv4
- disks
- Two-disk ZFS mirror
One profile gives the installer a consistent target, route, network and disk layout.
Automation where it helps. Control where it matters.
The common Linux rebuilds can run unattended, while normal installers, live environments and recovery utilities remain available behind the same controlled entry point.
Automated installs
Ubuntu, Debian, AlmaLinux and Rocky Linux can use prepared unattended routes with network and supported storage choices already supplied. Windows Server and infrastructure targets can use their own prepared paths.
Interactive media
When a machine needs individual attention, load the normal installer or live environment instead of forcing it through an automated route.
Recovery tools
Boot maintenance and diagnostic utilities without first writing an image to removable media or changing the installed system.
Put the network in place before the installer asks.
The deployment profile can carry the addressing model the machine should use, reducing the amount of configuration left for the console.
DHCP
Start quickly on networks that already provide the required lease and route.
Static IPv4
Prepare the address, prefix, gateway and resolver used by the installed system.
IPv6
Carry IPv6 configuration where the selected deployment route supports it.
Dual stack
Prepare IPv4 and IPv6 together for machines that need both from first boot.
Choose the disk policy before installation starts.
Storage support depends on the target installer, but the intent can still be part of the deployment profile rather than an operator decision made halfway through the rebuild.
Direct partitions
A simple layout for straightforward operating-system installs.
LVM
Flexible volume management where the selected Linux installer supports it.
RAID 1
A mirrored layout for supported installers and matching disks.
ZFS mirror
Prepared two-disk ZFS installation for supported infrastructure targets.
deployment routeresolved
- request
- authenticated
- mirror
- closest available
- media
- selected target
One boot address, routed to the nearest available mirror.
A server does not need location-specific boot configuration. LogicBoot receives the request, selects the closest enabled mirror and returns the requested installer or recovery image.
One entry point
Use the same network boot address across every enabled deployment location.
No mirror selection
The dispatcher chooses the closest available route instead of presenting another menu.
Regional media delivery
The selected installer or recovery environment loads from the resolved mirror.
A controlled route from power-on to deployment.
The boot menu is only the front end. LogicBoot handles the session, location, network and installation choices needed to turn it into an operational deployment system.
Authenticated entry
The dispatcher checks the access policy before issuing a time-limited boot session, keeping each deployment request controlled from the start.
Site-aware routing
LogicBoot automatically selects the closest available deployment site and directs the machine to its local endpoint and media.
Network configuration
Use DHCP for a quick start or prepare static IPv4, IPv6 and dual-stack settings before the selected installer begins.
Storage profiles
Choose direct partitions, LVM, RAID 1 or ZFS where the selected installer supports them, giving repeat rebuilds a consistent layout.
What early access actually means.
LogicBoot is being shown while the automated routes and regional deployment layer continue to expand. These are the useful boundaries to know before requesting access.
Is every catalogue entry automated?
No. The catalogue combines prepared unattended routes with normal installers, live environments and recovery tools. The available path is shown for the selected target.
Does it work with BIOS and UEFI?
LogicBoot can serve machines using either legacy BIOS or UEFI network boot. Individual media can still depend on firmware and architecture.
Does an operator choose the deployment site?
No. LogicBoot resolves the session to the closest available enabled site before the target media is loaded.
Can a machine use static networking?
Yes. A deployment profile can use DHCP or prepared static IPv4, IPv6 and dual-stack settings where the installer supports them.
Is LogicBoot generally available?
Not yet. The service is in early access while deployment routes, media and automated installers are expanded and tested.
Bring a better rebuild path to your infrastructure.
Tell us about your hardware, locations and deployment workload. We’ll explain where LogicBoot fits and what access currently includes.