OpenFactory promises prompt-to-ISO golden images. One alpha review is not evidence.

OpenFactory, a new service from developer Erik Ziegenbald, says it will turn a prompt, a Git repo or a reusable recipe into bootable Linux images, multi-node labs and fleet deployments, boot and test them in VMs, apply CIS controls, deploy web apps and record visual app tests ^[1][2]. ZDNet's reviewer ran the prompt path and came away with a working Debian-based KDE Plasma ISO he could rebuild, retest and re-download ^[4], which matters because the golden image is usually a platform team's hand-assembled artifact rather than something a service emits on request.

What was actually demonstrated is narrower than the pitch. The reviewer described a creative desktop: KDE Plasma styled to look like macOS, writing, audio, video and publishing tools, Ollama with the Alpaca GUI, and the Calamares installer ^[6]. He clicked New Chat, typed that description, clicked Validate Recipe, waited, clicked Start Build, waited longer, and downloaded an ISO inside a ZIP ^[7]. Both build paths, the AI prompt and the selection menu, produced a bootable result ^[5]. That is the whole of the verified surface. The CIS controls, Git repo ingest, multi-node labs, fleet deployment, web app deploys and visual test recording named in the site copy are unexercised in this account ^[17]. For anyone whose interest is compliance baselines, the one capability that would justify replacing a platform-team process is the one nobody has shown working.

The alpha is a real alpha. ZDNet calls the service "currently in the early alpha stage" in its summary and "pre-alpha software" in the body, so the source is not consistent about maturity ^[10][11][12]. The reviewer's experience was bumpy and involved a lengthy back-and-forth with the developer to resolve bugs as they appeared ^[9]. A second attempt failed at download with {"detail":"Failed to create download package"}, traced to a credential problem ^[8]. Note who fixed it: the developer, not the evaluator ^[20]. In a hosted build pipeline that is the normal cost of the model, but it is a cost worth pricing before anything downstream depends on it.

The interesting part is not the ISO. It is the recipe. ZDNet frames the use case as a reproducible definition shared across an organisation so every member of an IT team deploys the same distribution with the same feature set ^[16], and the reviewer could return to a build, add or remove features and rebuild ^[4]. That is the same claim Kickstart, image builders and Dockerfiles make, and it lives or dies on whether inputs are pinned. The service also lets you run 1356 distributions and variants online ^[13] and build for a PinePhone ^[14], and requires an account to keep your builds and downloadable ISOs ^[15].

Four things to test if you evaluate it. Whether a recipe saved today rebuilds to the same content in six months, since reuse is the advertised value ^[2][16]. Whether the CIS step emits a machine-readable report an auditor will accept, rather than a claim in a chat log ^[2]. Whether a Git repo as input means declarative config under your review process or an opaque scrape. And how much of the build depends on the vendor's control plane, given that the one hard failure here needed the vendor to clear it ^[8][20].

One reviewer, initially skeptical of services that overpromise ^[19], expects this one to be big ^[18]. That is a forecast from a single hands-on session, not a track record.