IF ImageForge Request pilot

USB-first Windows imaging for real IT benches

ImageForge

Turn one clean Windows machine into a repeatable deployment workflow your technicians can run without PXE, cloud lock-in, or hand-built installs.

Built for schools, IT shops, repair benches, and MSPs Early pilot access open

If imaging still means installing Windows by hand, copying files from a random share, or babysitting a one-off cloning tool, ImageForge gives your team a cleaner system: one Forge server, one boot USB, one repeatable process.

1 image library Golden Windows images, driver packs, profiles, and activity in one place
No cloud login Designed for LAN-first and air-gapped imaging environments

How it works

From clean install to repeatable deployment.

ImageForge keeps the workflow simple enough for a bench technician and structured enough for an IT manager to trust.

01

Prepare one good machine

Start with a clean Windows install, your apps, your policies, and the setup you want every similar PC to receive.

02

Capture it to the Forge

Boot from the ImageForge USB and save the machine as a reusable golden image in your central library.

03

Reimage the next PC

Choose the image, confirm the wipe, let ImageForge apply the image, inject matching drivers, and reboot.

Why it matters

Stop rebuilding the same Windows machine again and again.

ImageForge is for teams that need repeatable deployments but do not want to spend weeks turning imaging into its own infrastructure project.

Less repetitive bench work

Replace manual installs, driver hunts, and setup checklists with a repeatable capture and deploy process.

Cleaner handoff to technicians

Technicians boot the USB, authenticate, pick the right image, and follow a constrained workflow instead of improvising.

One place for image truth

Keep images, categories, drivers, deployment profiles, and activity history on the Forge instead of scattered across folders.

What you get

A command center for your Windows image library.

The Forge gives your team a central place to manage golden images, technician access, driver packs, deployment profiles, storage, and audit history.

IMAGEFORGE::CONSOLE licensed
18images
2.4 TBlibrary
12/15seats
recent activity

Deploy front-office-win11 to Dell Latitude 7420

Capture lab-golden-22h2 from HP ProDesk

Service win11-base v7 with cumulative updates

Driver matchLatitude 74*

TLS pinverified

Golden image library

Keep deployable Windows images organized by name, category, operating system, technician, size, and history.

Hardware-aware drivers

Attach driver packs to machine models so deployments can adapt to the laptops and desktops on your bench.

Deployment profiles

Apply naming rules, organization settings, first-boot scripts, and other finish-work that normally happens by hand.

Audit and inventory

See who captured or deployed what, which machine was touched, which image was used, and whether the job succeeded.

Why teams switch

The control you need, without the heavyweight imaging stack.

PXE

No PXE on day one

Start with USB boot media and prove the workflow before adding network boot complexity.

LAN

Works where cloud tools do not

Run on local networks, imaging VLANs, repair benches, and environments where internet access is limited.

WIM

Windows-native imaging

Build around WIM images and WinPE workflows your IT team can reason about and troubleshoot.

LOG

Know what happened

Capture and deploy events flow into a history you can review, export, and use for accountability.

Security

Built for networks where images are sensitive.

Golden images can contain software, configuration, and access decisions. ImageForge treats the image server like infrastructure that needs authentication, encryption, and traceability.

Offline activation

Activate a Forge with a signed license key that verifies locally, even on an isolated imaging network.

Admin and technician access

Admins manage the console. Technicians use access codes so image actions are tied to the person doing the work.

Server verification

Boot media can pin the Forge certificate fingerprint so technicians know they are talking to the right server.

Destructive action guardrails

Deploy requires WinPE, an explicit wipe confirmation, and image verification before the operating system is applied.

Pricing

Simple licensing for teams that image PCs.

Start with a bench pilot, then grow by Forge server and technician seats as ImageForge becomes part of your deployment workflow.

Pilot

Bench pilot

Request quote

For proving ImageForge with your own machines, images, drivers, and technicians.

  • 1 Forge server
  • Up to 3 technician seats
  • USB capture and deploy workflow
  • Email onboarding support
Start pilot
MSP

Service provider

Custom

For providers that prepare, refresh, or recover Windows machines across client environments.

  • Multiple Forge licenses
  • Customer-specific seat counts
  • Deployment reporting export
  • Roadmap input for scale features
Talk rollout

Seat planning

Each active technician access code consumes one licensed seat.

12 seats

Downloads

Grab the software. Your license is the key.

Downloads are open — an ImageForge server won't capture or deploy anything until it's activated with a license key, and boot media is inert without an activated Forge and a technician access code. Install first, activate when you're ready.

Forge Server

ImageForge Server Installer

Installs the Forge as a Windows service, walks through server name and license, and configures the firewall and file sharing for direct capture.

Windows 10/11 or Server 2019+ · 64-bit

Download installer

Server setup guide

Boot Media

ImageForge Boot ISO

The technician boot environment. Write it to any USB stick with Rufus (GPT, UEFI) and boot the machines you want to capture or deploy.

UEFI machines · ~550 MB

Download boot ISO

Boot media guide

Pilot access

Prove it with the machines sitting on your bench.

The best ImageForge demo is not a slide deck. It is your source PC, your target PC, your storage, and a real reimage job.

What the pilot includes

  • A licensed Forge server for your test environment
  • Guided USB or ISO boot media setup
  • A technician workflow for capture, deploy, and diagnostics
  • A validation checklist for images, drivers, and audit history
  • Storage guidance for local disk or NAS-backed image libraries

What you bring

  • A Windows machine or VM to run the Forge
  • One source PC with the Windows setup you want to reuse
  • One wipe-safe target PC for deployment testing
  • Any special NIC or storage drivers your hardware needs
  • A short test window where destructive deploy is expected

Early access status

Built carefully. Tested honestly.

ImageForge is entering early pilot while physical hardware testing is completed. The public promise is simple: prove the workflow on real machines before making broad compatibility claims.

Done

VirtualBox Windows 10 capture, deploy, and boot validation

Done

WinPE driver injection path exercised with model matching

Now

Physical USB testing on real laptops, desktops, NICs, and storage controllers

Next

Publish supported hardware notes, screenshots, demo video, and buyer-facing install guide

FAQ

Questions before you try it.

Does ImageForge require PXE?

No. ImageForge starts with USB or ISO boot media, which is easier to pilot and does not require DHCP, TFTP, or network-boot changes.

Can activation work offline?

Yes. License keys are signed by the vendor and verified locally by the Forge, so activation works on air-gapped imaging networks.

Can one image handle multiple hardware models?

Yes, that is the purpose of driver packs. The client detects the target model and injects matching drivers during deploy.

Is ImageForge a replacement for large enterprise tools?

ImageForge is aimed at teams that want a lighter, bench-friendly deployment system. It can complement larger tooling, but it is designed to be useful without a full enterprise imaging rollout.

Evaluation resources

Bring the right people into the pilot.

Get started

See if ImageForge fits your bench.

Tell us what you reimage, how often you do it, and what hardware mix you support. We will shape a pilot around your actual workflow.