Installs

Timeline

Node Images

Operating system images that bootimus hosts and boots nodes with. Add an image for a provider, then download it so the kernel and initrd are cached locally. Clusters pick a node image to determine their OS.

Clusters

Kubernetes clusters that bootimus boots nodes into. Each cluster picks a node image for its OS; use Configure to edit or upload its join configs.

Cluster Nodes

Nodes assigned to a cluster. Add a node by its MAC address. Reinstall wipes the node and reprovisions it on next PXE boot; Remove from cluster detaches the node.

Public Files

Files available to all clients. For image-specific files, manage them from the Images tab.

User Management

Manage admin panel user accounts and permissions.

Two-Factor Authentication

Protect your own account with a time-based one-time code from an authenticator app such as Aegis, Google Authenticator or 1Password. Applies to local accounts only; LDAP and OIDC users get their second factor from their identity provider.

Scan the code, or enter this secret manually:

Code from the app

Enable Cancel

API Tokens

Long-lived tokens for scripts and integrations. Send one as Authorization: Bearer btk_…. Read tokens can only call GET endpoints available to read-only users; admin tokens can do everything except manage tokens.

Audit Log

Every change made through the admin API: who did it, what was called and how the server answered. Reads are not recorded.

Boot Tools

Download a tool to make it available, then enable it to show in the boot menu.

Distro Profiles

Distro profiles define how ISOs are detected and booted. Built-in profiles are updated from the central repository. Custom profiles take priority.

Auto-Install Files

Install operating systems without manual prompts. Windows uses autounattend.xml; Ubuntu uses cloud-init; Red Hat and its family use kickstart; Debian uses preseed; openSUSE uses AutoYaST or Agama; Fedora CoreOS and Flatcar use Ignition; Proxmox VE uses an answer file. Attach a file to an image for a default config, or override it per client for machine-specific setups.

Bootloader Management

Manage iPXE bootloader sets served to PXE clients. Create custom sets with your own bootloader files.

Boot Menu

Configure the PXE boot menu seen by clients — title, timeout, and default fallback action. Console resolution may not be supported by all iPXE firmware builds.

Preview as Client

Render the exact iPXE script a client would receive, without logging a boot or consuming its next-boot action. Leave the MAC as unknown to see the menu an unregistered client gets.

Webhook

POST a JSON payload to a URL when PXE events happen. Fire-and-forget, 10s timeout, no retries.

Backup

Download a .tar.gz of the bootimus data directory: database, bootloader configuration, custom bootloader sets, and settings. ISOs and downloaded tool binaries are excluded (they're reproducible).

Upload a backup produced by Download Backup. It is staged in the data directory and applied the next time Bootimus starts; the previous SQLite database is kept as bootimus.db.pre-restore. PostgreSQL restores need psql on the server.

Housekeeping

Prune old records once a day so the database does not grow without limit. Set a period to 0 to keep records forever.

Data directory usage

USB Boot Images

Download bootable USB images for machines that don't support PXE network booting. Write to a USB stick and boot from it to access the bootimus menu.

Disk Images

Capture a client's disk into an image with Clonezilla, then deploy that image to one client or a whole client group on their next PXE boot. Images are stored under disk-images/ in the data directory and served to clients over the built-in NFS server.

Capture and Deploy Jobs

A job stays pending until the client PXE boots, runs while Clonezilla works, and is completed or failed when the client reports back. Pending and running jobs can be cancelled.

PXE Debug

Every DHCP packet the built-in proxyDHCP responder has seen, with the decision Bootimus took: which bootfile it offered, or why it stayed silent. Use this when a client fails to PXE boot before you reach for tcpdump.

API Reference

Generated from the server's OpenAPI document at /api/openapi.json. All endpoints require authentication except where marked NO AUTH. Responses are JSON of the form {success, data, error}. Placeholders are shown as {name}.

Boot Attempt History

Record of all PXE boot attempts by clients.