Overview

FluxDeploy is a custom Windows OS deployment system built on .NET 10, designed as a modern replacement for Microsoft Deployment Toolkit (MDT). It automates the entire lifecycle of bare-metal Windows deployments - from PXE boot through driver injection and first-boot configuration.

Key Principles#

• UEFI only - FluxDeploy targets modern hardware exclusively. The boot agent validates firmware_type=UEFI at startup and halts immediately if legacy BIOS/CSM is detected.
• HTTPS everywhere - All communication between agents, relays, and the Core server is encrypted with TLS 1.2+. Certificate pinning prevents man-in-the-middle attacks.
• Minimal-touch - Deployments are fully automated when a single recipe is active and no boot password is required. Technician interaction is only needed for multi-recipe selection or password entry.
• SHA-256 verification - Every WIM image is hash-verified before DISM applies it. Mismatches abort the deployment immediately.

Architecture#

FluxDeploy uses a Core/Relay architecture:

• FluxDeploy Core - The central management server. Hosts the web UI, image library, driver repository, and all administrative functions. Core can also serve as a direct deployment server.
• FluxDeploy Relay - Deployed at remote sites, relays cache images and drivers locally. Agents at each site connect to their local relay for faster deployments. Relays sync content from Core automatically.

Technology Stack#

What FluxDeploy Manages#

• Deployment Recipes - Reusable deployment configurations combining a Windows image, drivers, answer file settings, and task sequences
• Windows Images - WIM files with optional customization (debloat, updates, feature enablement)
• Driver Packages - Deployment drivers (offline injection) and WinPE drivers (boot-time loading) from HP, Dell, and Lenovo catalogs
• Boot Images - WinPE ISOs with embedded agents for PXE or USB boot
• Task Sequences - Custom scripts and commands at defined deployment phases

On a phone or tablet#

Below about 990px wide - a phone in any orientation, or a tablet in portrait - the navigation sidebar becomes a drawer. A bar across the top of the page carries the menu button on the left; tap it to slide the navigation in, and tap a link, tap outside the drawer, or press Escape to close it again. The sidebar footer controls (theme, sign out, version, What's New) are inside the drawer, at the bottom, exactly where they are on a desktop.

The rest of the interface reflows to one column. Tables of things you look at individually - relay sites, machines, the reports - become one card per row with each value labelled, so nothing is cut off and nothing is hidden; wide reference tables such as the driver catalogs keep their columns and scroll sideways inside their own box rather than moving the page.

Interface Preferences#

The sidebar footer holds two per-browser display preferences. Both are stored locally in the browser, so they apply to whoever is sitting at that machine rather than to the FluxDeploy account.

• Descriptions (info icon) - Settings pages carry explanatory text under most controls. Turn descriptions off once you know your way around and the pages collapse to just the controls. Each hidden description leaves a small ? next to its field - click it to read that one description without turning everything back on. Errors, validation messages, warnings, and anything reporting current state are never hidden.
• Theme - Light, Dark, or Auto (follows the operating system setting).

Finding the Documentation#

Every settings page and every major feature page carries a ? button in its header, and panels with a matching topic carry a Learn more link. Both open this documentation in a separate window sized to sit beside the app, so you keep your place - and any half-filled form - in the main window. Clicking help again re-uses that same window rather than opening another one, and the docs window follows your theme.

The documentation is served by your own FluxDeploy server. Nothing is fetched from the internet, so it works on an isolated network. If you would rather read it full-screen inside the app, the docs window's Open in app window link sends the main window to the same page, and /help/{topic} addresses stay bookmarkable.